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 ·

qwik.dev

https://qwik.dev/

93 96 58 92 6AXE CWV

Data from Aug 23, 2026, 6:38 AM UTC 15h old

Site Generators #16 · 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.

Qwik Built with Qwik
Cloudflare Hosted by Cloudflare

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-25 → 2026-08-21). This is what Google measures you on.

LCP 1.71 s good
INP 48 ms good
CLS 0 good

Scores

93
Performance
↑ +3 (+3.3%)
96
Accessibility
no change
58
Best Practices
no change
92
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.06 s 2.42 s ↓ -360 ms (-14.9%) 1.87 s 2.42 s
CLS Cumulative Layout Shift 0 0 → no change 0 0
TBT Total Blocking Time 220 ms 291 ms ↓ -71 ms (-24.4%) 113 ms 291 ms
FCP First Contentful Paint 2.01 s 2.13 s ↓ -119 ms (-5.6%) 1.87 s 2.13 s
Speed Index 2.01 s 2.13 s ↓ -119 ms (-5.6%) 1.87 s 2.13 s
TTFB Time to First Byte 454 ms 457 ms ↓ -3 ms (-0.7%) 454 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 2.06 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 91 ms
time to first byte 24 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-25 → 2026-08-21). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.71 s good 91.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 48 ms good 99.3% good
CLS CWV 0 good 94.7% good
FCP 1.62 s good 80.5% good
TTFB 1.14 s needs-improvement 56.9% good

Lab vs field

Lab LCP 2.06 s · field p75 1.71 s · real users are 0.83× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.84 s 49 ms 0 1.68 s 1.16 s
2026-08-08 1.82 s 58 ms 0 1.66 s 1.15 s
2026-08-01 1.75 s 61 ms 0 1.66 s 1.19 s
2026-07-25 1.54 s 62 ms 0 1.55 s 1.16 s
2026-07-18 1.65 s 57 ms 0 1.58 s 1.21 s
2026-07-11 1.54 s 51 ms 0 1.56 s 1.11 s
2026-07-04 1.47 s 57 ms 0 1.52 s 1.08 s
2026-06-27 1.59 s 59 ms 0 1.58 s 1.07 s
2026-06-20 1.47 s 61 ms 0 1.46 s 1.07 s
2026-06-13 1.52 s 61 ms 0 1.53 s 1.09 s
2026-06-06 1.45 s 61 ms 0 1.45 s 1.06 s
2026-05-30 1.44 s 62 ms 0 1.44 s 1.09 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.34 MB 2.34 MB ↑ +309 B 2.34 MB 2.34 MB
Requests 468 463 ↑ +5 (+1.1%) 463 468
Third-party Weight 11.5 kB 11.5 kB → no change 11.5 kB 11.5 kB
Third-party CPU 6 ms 4 ms ↑ +2 ms (+55.6%) 4 ms 6 ms
Unused JS 65.3 kB 65.3 kB → no change 65.3 kB 65.3 kB
Unused CSS 0 B 0 B → no change 0 B 0 B

By resource type

image 1.07 MB · 11 req
script 821 kB · 205 req
other 375 kB · 246 req
document 45.6 kB · 2 req
font 25.2 kB · 3 req
third party 359 kB · 12 req

Third parties 1 entities

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

Cloudflare 11.5 kB · 6 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.47 s 2.57 s ↓ -92 ms (-3.6%) 2.47 s 2.64 s
Long Tasks 5 4 ↑ +1 (+25%) 4 5
DOM Elements 740 740 → no change 740 740
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 6 → no change 6 6
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 3 3 → no change 3 3

Main thread work

other 1.33 s
script evaluation 851 ms
style layout 97 ms
script parse compile 75 ms
parse HTML 60 ms
paint composite render 52 ms
garbage collection 6 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 1100 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 5 nodes
  • moderate page-has-heading-one — Page should contain a level-one heading 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 3 nodes

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 23, 2026, 6:38 AM UTC 93 2.06 s 0 220 ms 2.34 MB 3/3 ±16 2,475 42.3s
Aug 22, 2026, 6:38 AM UTC 90 2.42 s 0 291 ms 2.34 MB 3/3 ±17 2,340 41.5s
Aug 21, 2026, 5:31 AM UTC 97 1.87 s 0 113 ms 2.34 MB 3/3 ±2 2,376 39.7s

Embed this score

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