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 ·

istanbul.js.org

https://istanbul.js.org/

94 84 96 100 12AXE –CWV

Data from Aug 23, 2026, 3:01 AM UTC 18h old

Test Runners #6 · 3 measurements · since Aug 21, 2026

The measuring machine was faster than usual.

Lighthouse benchmark index was 3545.5 against a baseline of 2495 (42.1%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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.

Ph Built with Phenomic 0.16.2
GitHub Pages Hosted by GitHub Pages

Scores

94
Performance
↑ +20 (+27%)
84
Accessibility
no change
96
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. 375 ms
  2. 750 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 2.87 s 5.02 s ↓ -2146 ms (-42.8%) significant 2.87 s 5.02 s
CLS Cumulative Layout Shift 0 0.042 ↓ -0.042 (-100%) significant 0 0.052
TBT Total Blocking Time 69 ms 304 ms ↓ -235 ms (-77.3%) 69 ms 304 ms
FCP First Contentful Paint 1.60 s 1.64 s ↓ -41 ms (-2.5%) 1.60 s 1.69 s
Speed Index 1.60 s 1.64 s ↓ -41 ms (-2.5%) 1.60 s 3.41 s
TTFB Time to First Byte 623 ms 615 ms ↑ +8 ms (+1.3%) 615 ms 759 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 2.87 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 99 ms
time to first byte 24 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 571 kB 570 kB ↑ +451 B (+0.1%) 570 kB 576 kB
Requests 11 11 → no change 11 12
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 68.7 kB 68.7 kB ↓ -2 B 66.4 kB 68.7 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

script 329 kB · 4 req
image 230 kB · 3 req
document 9.1 kB · 2 req
stylesheet 1.6 kB · 1 req
third party 6.2 kB · 4 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 472 ms 737 ms ↓ -264 ms (-35.9%) 472 ms 737 ms
Long Tasks 3 2 ↑ +1 (+50%) 1 3
DOM Elements 68 68 → no change 68 68
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 12 12 → no change 12 12
A11y Failures 3 3 → no change 3 3
A11y Failing Nodes 10 10 → no change 10 10

Main thread work

other 150 ms
script evaluation 142 ms
style layout 104 ms
script parse compile 59 ms
parse HTML 11 ms
paint composite render 6 ms

Axe violations axe-core 4.13.0, full rule set

12 violating nodes across 4 rules, 166 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 8 nodes
  • moderate landmark-one-main — Document should have one main landmark 2 nodes
  • serious frame-title — Frames must have an accessible name 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 3 of 15 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. 8 nodes
  • frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node
  • landmark-one-main — Document does not have a main landmark. 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 2 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, 3:01 AM UTC 94 2.87 s 0 69 ms 571 kB 3/3 ±22 3,546 26.1s
Aug 22, 2026, 2:52 AM UTC 74 5.02 s 0.042 304 ms 570 kB 3/3 ±4 2,501 27s
Aug 21, 2026, 1:15 AM UTC 79 4.95 s 0.052 94 ms 576 kB 3/3 ±19 2,490 26.3s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show istanbul.js.org'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://istanbul.js.org/"></speedlify2-score>