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 ·

qunitjs.com

https://qunitjs.com/

100 98 100 100 19AXE –CWV

Data from Aug 23, 2026, 7:32 AM UTC 14h old

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

The measuring machine was faster than usual.

Lighthouse benchmark index was 3104 against a baseline of 2456.8 (26.3%). 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.

GitHub Pages Hosted by GitHub Pages

Scores

100
Performance
no change
98
Accessibility
no change
100
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 903 ms 902 ms ↑ +1 ms (+0.1%) 902 ms 904 ms
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 0 ms 0 ms → no change 0 ms 0 ms
FCP First Contentful Paint 771 ms 819 ms ↓ -48 ms (-5.9%) significant 771 ms 819 ms
Speed Index 771 ms 819 ms ↓ -48 ms (-5.9%) significant 771 ms 819 ms
TTFB Time to First Byte 603 ms 602 ms ↑ +1 ms (+0.2%) 602 ms 604 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 903 ms 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 50 ms
time to first byte 3 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 2.03 s — 0 2.04 s 1.73 s
2026-06-20 2.45 s — 0 2.45 s 1.90 s
2026-06-13 2.60 s — 0 2.56 s 2.02 s
2026-06-06 2.54 s — 0 2.55 s 1.83 s
2026-05-30 2.49 s — 0 2.48 s 1.75 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 91.5 kB 91.9 kB ↓ -387 B (-0.4%) 91.5 kB 91.9 kB
Requests 10 10 → no change 10 10
Third-party Weight 73.6 kB 73.8 kB ↓ -232 B (-0.3%) 73.6 kB 73.8 kB
Third-party CPU 8 ms 11 ms ↓ -2 ms (-21.5%) significant 8 ms 11 ms
Unused JS 35.0 kB 35.0 kB → no change 35.0 kB 35.0 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

script 73.3 kB · 2 req
stylesheet 8.2 kB · 2 req
image 4.4 kB · 2 req
document 4.4 kB · 2 req
other 1.2 kB · 1 req
third party 73.6 kB · 2 req

Third parties 1 entities

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

jQuery CDN 73.6 kB · 8 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 280 ms 386 ms ↓ -106 ms (-27.4%) significant 280 ms 386 ms
Long Tasks 0 1 ↓ -1 (-100%) 0 1
DOM Elements 200 200 → no change 200 200
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 19 19 → no change 19 19
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 1 1 → no change 1 1

Main thread work

other 110 ms
style layout 84 ms
script evaluation 39 ms
script parse compile 22 ms
parse HTML 14 ms
paint composite render 12 ms

Axe violations axe-core 4.13.0, full rule set

19 violating nodes across 4 rules, 426 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 14 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 of 25 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.

  • 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

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, 7:32 AM UTC 100 903 ms 0 0 ms 91.5 kB 3/3 ±0 3,104 23.6s
Aug 22, 2026, 7:31 AM UTC 100 902 ms 0 0 ms 91.9 kB 3/3 ±5 2,434 27.7s
Aug 21, 2026, 6:51 AM UTC 100 904 ms 0 0 ms 91.5 kB 3/3 ±0 2,480 22.9s

Embed this score

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