speedlify2

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

Measurement runs · Embed a score ·

lume.land

https://lume.land/

89 90 92 100 52AXE –CWV

Data from Aug 23, 2026, 4:35 AM UTC 17h old

Site Generators #13 · 3 measurements · since Aug 21, 2026

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.

Lu Built with Lume
Netlify Hosted by Netlify

Scores

89
Performance
↑ +1 (+1.1%)
90
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 376 ms
  2. 751 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.31 s 3.41 s ↓ -2102 ms (-61.6%) 1.31 s 3.41 s
CLS Cumulative Layout Shift 0.224 0.001 ↑ +0.223 (+22300%) significant 0.001 0.224
TBT Total Blocking Time 15 ms 55 ms ↓ -40 ms (-72.7%) 7 ms 55 ms
FCP First Contentful Paint 1.14 s 2.60 s ↓ -1461 ms (-56.2%) 1.14 s 2.60 s
Speed Index 1.53 s 2.60 s ↓ -1072 ms (-41.2%) 1.47 s 2.60 s
TTFB Time to First Byte 634 ms 604 ms ↑ +30 ms (+5%) 604 ms 634 ms

What LCP is made of observed, unthrottled

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

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 1.31 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 148 ms
time to first byte 36 ms

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 — — — — —
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.04 MB 1.03 MB ↑ +5.3 kB (+0.5%) 1.03 MB 1.04 MB
Requests 87 87 → no change 87 87
Third-party Weight 0 B 0 B → no change 0 B 0 B
Third-party CPU 0 ms 0 ms → no change 0 ms 0 ms
Unused JS 31.5 kB 31.5 kB ↑ +58 B (+0.2%) 31.5 kB 31.5 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

image 669 kB · 72 req
font 284 kB · 4 req
script 42.3 kB · 2 req
document 26.7 kB · 1 req
stylesheet 13.3 kB · 3 req
other 1.6 kB · 3 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.23 s 1.09 s ↑ +138 ms (+12.6%) 1.09 s 1.23 s
Long Tasks 4 3 ↑ +1 (+33.3%) 3 4
DOM Elements 1,099 1,100 ↓ -1 (-0.1%) 1,099 1,101
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 52 52 → no change 52 52
A11y Failures 4 4 → no change 4 4
A11y Failing Nodes 25 25 → no change 25 25

Main thread work

other 470 ms
style layout 434 ms
script evaluation 153 ms
paint composite render 146 ms
parse HTML 27 ms
script parse compile 2 ms

Axe violations axe-core 4.13.0, full rule set

52 violating nodes across 5 rules, 1992 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.

  • moderate region — All page content should be contained by landmarks 23 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 22 nodes
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 4 nodes
  • critical aria-required-children — Certain ARIA roles must contain particular children 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 4 of 30 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 21 nodes
  • aria-required-children — Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children. 2 nodes
  • landmark-one-main — Document does not have a main landmark. 1 node
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 1 node

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 6 console errors

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 23, 2026, 4:35 AM UTC 89 1.31 s 0.224 15 ms 1.04 MB 3/3 ±10 2,458 36.6s
Aug 22, 2026, 3:40 AM UTC 88 3.41 s 0.001 55 ms 1.03 MB 3/3 ±18 2,448 37.1s
Aug 21, 2026, 3:11 AM UTC 99 1.67 s 0.012 7 ms 1.04 MB 3/3 ±16 2,349 32.8s

Embed this score

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

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://lume.land/"></speedlify2-score>