speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

pico-blades.buildawesome.one

https://pico-blades.buildawesome.one/

90PERF 73A11Y 100BEST 82SEO ✗AXE –CWV

Ranks Overall #1,567 Build Awesome Starters #162

Data from Oct 14, 2026, 11:16 AM UTC old Measured once a week · 7 runs since Sep 1, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

Netlify Hosted by Netlify

Lighthouse Scores LAB Simulated

90
Performance
↑ +2 (+2.3%)
73
Accessibility
no change
100
Best Practices
no change
82
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 1.86 s good ↓ -48 ms (-2.5%) 1.83 s – 2.67 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.173 needs work ↓ -0.039 (-18.4%) significant 0.173 – 0.212
TBT Total Blocking Time 125 ms good ↑ +17 ms (+15.7%) 41 ms – 248 ms
FCP First Contentful Paint 1.71 s good ↑ +27 ms (+1.6%) 1.66 s – 2.37 s
Speed Index 1.71 s good ↑ +27 ms (+1.6%) 1.66 s – 2.46 s
TTFB Time to First Byte 635 ms good ↑ +15 ms (+2.4%) 605 ms – 1.14 s

LCP Subparts LAB Unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.

element render delay 72 ms
time to first byte 36 ms

Page weight

Metric Value Change / range Trend
Page Weight 359 kB ↓ -1.0 kB (-0.3%) 351 kB – 360 kB
Requests 23 → no change 22 – 32
Third-party Weight 354 kB ↓ -694 B (-0.2%) 346 kB – 355 kB
Third-party CPU 89 ms ↑ +4 ms (+5.1%) 52 ms – 125 ms
Unused JS 143 kB ↑ +1.0 kB (+0.7%) 141 kB – 145 kB
Unused CSS 11.7 kB → no change 11.7 kB – 11.7 kB

By resource type

Type Transfer Share Size Requests
script 90.9% 311 kB 3
stylesheet 4.6% 15.6 kB 2
image 3.1% 10.5 kB 9
document 1.3% 4.4 kB 3
other 0.2% 514 B 4
Total 359 kB 23

Third parties 7 entities

Entity Transfer Size Main thread Simulated
Google Tag Manager script 307 kB 87 ms
blades.dev 16.9 kB 0 ms
JSDelivr CDN 15.6 kB 0 ms
shields.io 9.5 kB 0 ms
zgo.at 4.3 kB 2 ms
All 7 354 kB 89 ms

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Page health

Metric Value Change / range Trend
Main Thread Work 839 ms ↓ -13 ms (-1.6%) 666 ms – 1.10 s
Long Tasks 4 ↑ +1 (+33.3%) 2 – 5
DOM Elements 119 → no change 119 – 144
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 14 → no change 14 – 19
A11y Failures 5 → no change 5 – 5
A11y Failing Nodes 10 → no change 10 – 15

Main thread work

Task Time Share Duration Simulated
script evaluation 42% 349 ms
other 28% 233 ms
style layout 13% 113 ms
script parse compile 10% 88 ms
paint composite render 5% 43 ms
parse HTML 2% 14 ms
Total 839 ms

Axe violations axe-core 4.13.0, full rule set

14 violating nodes across 8 rules, 252 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes
    Offending elements
    1. pre:nth-child(8) > .language-sh
      <code class="language-sh">cd multisite/ # OR og-images/, OR tailwind/ npm install # dependencies npm start # development npm run stage # serve production version locally # ready to deploy! 🚀 </code>
    2. pre:nth-child(10) > .language-sh
      <code class="language-sh">SITE=bootstrap npm start </code>
    3. pre:nth-child(20) > .language-sh
      <code class="language-sh">cd og-images/ npm i npx shotpipe-init # free key, no signup — writes it to .env npm start </code>
  • critical image-alt — Images must have alternative text 3 nodes
    Offending elements
    1. p:nth-child(2) > img
      <img src="https://img.shields.io/github/v/release/buildawesome-one/examples?label=&amp;color=darkslategray&amp;style=for-the-badge">
    2. a[title="github.com"] > i > img
      <img src="https://www.google.com/s2/favicons?domain=github.com&amp;sz=64">
    3. a[title="shotpipe.io"] > i > img
      <img src="https://www.google.com/s2/favicons?domain=shotpipe.io&amp;sz=64">
  • serious object-alt — <object> elements must have alternative text 2 nodes
    Offending elements
    1. p:nth-child(2) > object
      <object data="https://img.shields.io/github/stars/buildawesome-one/examples?label=GitHub&amp;labelColor=silver&amp;color=gainsboro&amp;style=for-the-badge"></object>
    2. .dark-auto
      <object data="https://build.blades.ninja/gh.svg" class="dark-auto"></object>
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 2 nodes
    Offending elements
    1. pre:nth-child(8)
      <pre><code class="language-sh">cd multisite/ # OR og-images/, OR tailwind/ npm install # dependencies npm start # development npm run stage # serve production version locally # ready to deploy! 🚀 </…
    2. pre:nth-child(20)
      <pre><code class="language-sh">cd og-images/ npm i npx shotpipe-init # free key, no signup — writes it to .env npm start </code></pre>
  • minor empty-table-header — Table header text should not be empty 1 node
    Offending element
    1. th:nth-child(2)
      <th></th>
  • moderate heading-order — Heading levels should only increase by one 1 node
    Offending element
    1. #enable-it
      <h6 id="enable-it" tabindex="-1">Enable it: <a class="header-anchor" href="#enable-it" aria-hidden="true">#</a></h6>
  • serious link-name — Links must have discernible text 1 node
    Offending element
    1. p:nth-child(2) > a
      <a href="https://pico-blades.buildawesome.one/"><img src="https://img.shields.io/badge/Demo_➜-blue?style=for-the-badge" hidden=""></a>
  • moderate region — All page content should be contained by landmarks 1 node
    Offending element
    1. article
      <article>Generated by <mark>Multisite Starter</mark> from <code>./pico-blades/</code></article>

Accessibility failures 5 of 20 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 nodes
  • image-alt — Image elements do not have `[alt]` attributes 3 nodes
  • object-alt — `<object>` elements do not have alternate text 2 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-name — Links do not have a discernible name 1 node

SEO failures 2 of 8 audits

  • meta-description — Document does not have a meta description
  • image-alt — Image elements do not have `[alt]` attributes 3 items

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 14, 2026, 11:16 AM UTC 90 1.86 s 0.173 125 ms 359 kB 3/3 ±8 2,392 -4% 31.1s Wayback
Oct 7, 2026, 9:52 AM UTC 88 1.90 s 0.212 108 ms 360 kB 3/3 ±6 2,346 -6% 27.7s Wayback
Sep 30, 2026, 8:03 AM UTC 86 1.92 s 0.173 248 ms 356 kB 3/3 ±13 2,493 0% 32s Wayback
Sep 23, 2026, 5:31 AM UTC 89 1.96 s 0.173 152 ms 354 kB 3/3 ±5 2,338 -6% 31.7s Wayback
Sep 16, 2026, 3:30 AM UTC 88 1.89 s 0.173 184 ms 354 kB 3/3 ±13 2,509 +1% 25.8s Wayback
Sep 8, 2026, 11:51 PM UTC 90 1.83 s 0.186 41 ms 351 kB 3/3 ±5 4,406 +77% 24s Wayback
Sep 1, 2026, 10:41 PM UTC 84 2.67 s 0.173 148 ms 360 kB 3/3 ±7 2,318 -7% 56.4s Wayback

Embed this score

Use this web component to show pico-blades.buildawesome.one's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://pico-blades.buildawesome.one/"></speedlify2-score>