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 ·

preview.tabler.io

https://preview.tabler.io/

64 92 100 100 CWV 150AXE

Data from Aug 21, 2026, 6:49 AM UTC — 12h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 12h

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.

Vercel Hosted by Vercel

Core Web Vitals field data, url-level

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

LCP 1.34 s good
INP 165 ms good
CLS 0.040 good

Scores

64
Performance
no change
92
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 6.00 s 6.00 s 6.00 s
CLS Cumulative Layout Shift 0.045 0.045 0.045
TBT Total Blocking Time 365 ms 365 ms 365 ms
FCP First Contentful Paint 2.57 s 2.57 s 2.57 s
Speed Index 4.00 s 4.00 s 4.00 s
TTFB Time to First Byte 494 ms 494 ms 494 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.

element render delay 409 ms
time to first byte 77 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.34 s good 88.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 165 ms good 78.4% good
CLS CWV 0.040 good 97.1% good
FCP 1.21 s good 83.2% good
TTFB 430 ms good 88% good

Lab vs field

Lab LCP 6.00 s · field p75 1.34 s · real users are 0.22× 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.30 s 157 ms 0.040 1.17 s 422 ms
2026-08-08 1.40 s 163 ms 0.030 1.34 s 450 ms
2026-08-01 1.37 s 163 ms 0.010 1.33 s 488 ms
2026-07-25 1.45 s 169 ms 0 1.37 s 488 ms
2026-07-18 1.37 s 183 ms 0 1.33 s 426 ms
2026-07-11 1.31 s 170 ms 0.010 1.24 s 381 ms
2026-07-04 1.38 s 184 ms 0.040 1.28 s 375 ms
2026-06-27 1.46 s 206 ms 0.050 1.34 s 404 ms
2026-06-20 1.50 s 206 ms 0.050 1.38 s 435 ms
2026-06-13 1.55 s 212 ms 0.050 1.38 s 436 ms
2026-06-06 1.37 s 193 ms 0.020 1.23 s 394 ms
2026-05-30 1.33 s 186 ms 0.010 1.22 s 367 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.40 MB 1.40 MB 1.40 MB
Requests 130 130 130
Third-party Weight 467.2 kB 467.2 kB 467.2 kB
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 140.3 kB 140.3 kB 140.3 kB
Unused CSS 64.6 kB 64.6 kB 64.6 kB

By resource type

font 465.1 kB · 2 req
script 405.4 kB · 14 req
image 360.0 kB · 95 req
stylesheet 100.6 kB · 10 req
document 62.1 kB · 1 req
other 4.3 kB · 4 req
third party 467.2 kB · 3 req

Third parties 1 entities

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

rsms.me 467.2 kB · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 4.42 s 4.42 s 4.42 s
Long Tasks 8 8 8
DOM Elements 3,304 3,304 3,304
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 150 150 150
A11y Failures 5 5 5
A11y Failing Nodes 17 17 17

Main thread work

other 1.37 s
script evaluation 1.10 s
style layout 1.05 s
paint composite render 692 ms
script parse compile 126 ms
parse HTML 91 ms

Axe violations axe-core 4.13.0, full rule set

150 violating nodes across 10 rules, 3053 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 133 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 7 nodes
  • serious link-name — Links must have discernible text 3 nodes
  • minor empty-table-header — Table header text should not be empty 1 node
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node
  • moderate page-has-heading-one — Page should contain a level-one heading 1 node
  • serious scrollable-region-focusable — Scrollable region must have keyboard access 1 node

Accessibility failures 5 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. 6 nodes
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 5 nodes
  • link-name — Links do not have a discernible name 3 nodes
  • td-has-header — `<td>` elements in a large `<table>` do not have table headers. 2 nodes
  • 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 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, 6:49 AM UTC 64 6.00 s 0.045 365 ms 1.40 MB 3/3 ±8 2,492 54.1s

Embed this score

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