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 ·

openbulkurl.com

https://openbulkurl.com/

60 86 77 100 ✗CWV 27AXE

Data from Aug 21, 2026, 5:34 AM UTC — 13h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 13h

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.

Astro 5.13.3 Built with Astro 5.13.3
Netlify Hosted by Netlify

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.72 s good
INP 243 ms needs-improvement
CLS 0.070 good

Scores

60
Performance
no change
86
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.78 s — — 3.78 s 3.78 s
CLS Cumulative Layout Shift 0.390 — — 0.390 0.390
TBT Total Blocking Time 390 ms — — 390 ms 390 ms
FCP First Contentful Paint 1.02 s — — 1.02 s 1.02 s
Speed Index 3.29 s — — 3.29 s 3.29 s
TTFB Time to First Byte 654 ms — — 654 ms 654 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 120 ms
time to first byte 43 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.72 s good 86% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 243 ms needs-improvement 61.8% good
CLS CWV 0.070 good 88.9% good
FCP 1.28 s good 89.8% good
TTFB 497 ms good 88.4% good

Lab vs field

Lab LCP 3.78 s · field p75 1.72 s · real users are 0.45× 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.70 s 240 ms 0.070 1.26 s 490 ms
2026-08-08 1.73 s 252 ms 0.070 1.25 s 468 ms
2026-08-01 1.72 s 270 ms 0.070 1.25 s 474 ms
2026-07-25 1.66 s 281 ms 0.070 1.20 s 479 ms
2026-07-18 1.58 s 291 ms 0.060 1.20 s 496 ms
2026-07-11 1.48 s 270 ms 0.040 1.18 s 537 ms
2026-07-04 1.45 s 249 ms 0.040 1.14 s 598 ms
2026-06-27 1.49 s 240 ms 0.040 1.16 s 665 ms
2026-06-20 1.74 s 234 ms 0.040 1.35 s 716 ms
2026-06-13 — — — — —
2026-06-06 — — 0.070 1.79 s —
2026-05-30 2.63 s — 0.090 1.88 s 848 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.24 MB — — 2.24 MB 2.24 MB
Requests 107 — — 107 107
Third-party Weight 1.93 MB — — 1.93 MB 1.93 MB
Third-party CPU 242 ms — — 242 ms 242 ms
Unused JS 283.9 kB — — 283.9 kB 283.9 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

font 1.21 MB · 16 req
script 863.0 kB · 46 req
document 111.2 kB · 10 req
stylesheet 34.6 kB · 8 req
other 15.7 kB · 23 req
image 2.3 kB · 4 req
third party 2.05 MB · 71 req

Third parties 6 entities

1.93 MB transferred, 242 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Google Fonts 1.23 MB · 0 ms CPU
Google Tag Manager 301.8 kB · 66 ms CPU
Google/Doubleclick Ads 257.5 kB · 150 ms CPU
Google FundingChoices 98.6 kB · 13 ms CPU
adtrafficquality.google 21.3 kB · 5 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.06 s — — 3.06 s 3.06 s
Long Tasks 9 — — 9 9
DOM Elements 810 — — 810 810
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 27 — — 27 27
A11y Failures 5 — — 5 5
A11y Failing Nodes 15 — — 15 15

Main thread work

script evaluation 1.72 s
other 583 ms
style layout 418 ms
script parse compile 128 ms
paint composite render 96 ms
garbage collection 85 ms
parse HTML 36 ms

Axe violations axe-core 4.13.0, full rule set

27 violating nodes across 4 rules, 1493 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 18 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 7 nodes
  • serious aria-input-field-name — ARIA input fields must have an accessible name 1 node
  • critical select-name — Select element must have an accessible name 1 node

Accessibility failures 5 of 31 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. 7 nodes
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 5 nodes
  • aria-input-field-name — ARIA input fields do not have accessible names 1 node
  • aria-prohibited-attr — Elements use prohibited ARIA attributes 1 node
  • select-name — Select elements do not have associated label elements. 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 21, 2026, 5:34 AM UTC 60 3.78 s 0.390 390 ms 2.24 MB 3/3 ±7 3,376 52s

Embed this score

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