speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

mobile11ty.pages.dev

https://mobile11ty.pages.dev/

92 100 100 100 –CWV 20AXE

Data from Aug 21, 2026, 4:45 AM UTC — 14h old.

Build Awesome Starters · 1 measurement · since Aug 21, 2026 · last attempt 14h

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Cloudflare Hosted by Cloudflare

Scores

92
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.04 s — — 3.04 s 3.04 s
CLS Cumulative Layout Shift 0.081 — — 0.081 0.081
TBT Total Blocking Time 43 ms — — 43 ms 43 ms
FCP First Contentful Paint 1.68 s — — 1.68 s 1.68 s
Speed Index 1.68 s — — 1.68 s 1.68 s
TTFB Time to First Byte 469 ms — — 469 ms 469 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

resource load delay 184 ms
time to first byte 31 ms
element render delay 31 ms
resource load duration 19 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 217.8 kB — — 217.8 kB 217.8 kB
Requests 47 — — 47 47
Third-party Weight 117.7 kB — — 117.7 kB 117.7 kB
Third-party CPU 36 ms — — 36 ms 36 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 101.3 kB · 2 req
script 97.8 kB · 32 req
other 9.6 kB · 10 req
stylesheet 7.1 kB · 2 req
document 2.0 kB · 1 req
third party 117.7 kB · 44 req

Third parties 2 entities

117.7 kB transferred, 36 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

JSDelivr CDN 113.9 kB · 36 ms CPU
web.app 3.9 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 739 ms — — 739 ms 739 ms
Long Tasks 2 — — 2 2
DOM Elements 343 — — 343 343
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 20 — — 20 20
A11y Failures 0 — — 0 0
A11y Failing Nodes 0 — — 0 0

Main thread work

script evaluation 325 ms
other 288 ms
style layout 86 ms
parse HTML 17 ms
paint composite render 14 ms
garbage collection 5 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

20 violating nodes across 4 rules, 557 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • serious role-img-alt — [role="img"] and [role="image"] elements must have alternative text 17 nodes
  • moderate landmark-banner-is-top-level — Banner landmark should not be contained in another landmark 1 node
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 21, 2026, 4:45 AM UTC 92 3.04 s 0.081 43 ms 217.8 kB 3/3 ±3 2,469 22.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show mobile11ty.pages.dev's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site! 

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://mobile11ty.pages.dev/"></speedlify-score>