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 ·

railway.com

https://railway.com/

41 93 73 100 ✗CWV 65AXE

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

Web Hosts · 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.

Railway Hosted by Railway

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 2.04 s good
INP 594 ms poor
CLS 0.030 good

Scores

41
Performance
no change
93
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.18 s — — 6.18 s 6.18 s
CLS Cumulative Layout Shift 0.040 — — 0.040 0.040
TBT Total Blocking Time 2.99 s — — 2.99 s 2.99 s
FCP First Contentful Paint 3.37 s — — 3.37 s 3.37 s
Speed Index 3.83 s — — 3.83 s 3.83 s
TTFB Time to First Byte 633 ms — — 633 ms 633 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 160 ms
time to first byte 18 ms
resource load duration 18 ms
resource load delay 16 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 2.04 s good 82.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 594 ms poor 38.1% good
CLS CWV 0.030 good 83.4% good
FCP 1.72 s good 76.7% good
TTFB 600 ms good 82.6% good

Lab vs field

Lab LCP 6.18 s · field p75 2.04 s · real users are 0.33× 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 2.04 s 586 ms 0.030 1.72 s 601 ms
2026-08-08 2.06 s 589 ms 0.030 1.74 s 609 ms
2026-08-01 2.12 s 589 ms 0.030 1.77 s 627 ms
2026-07-25 2.15 s 578 ms 0.030 1.80 s 642 ms
2026-07-18 2.18 s 560 ms 0.030 1.82 s 656 ms
2026-07-11 2.21 s 547 ms 0.030 1.84 s 673 ms
2026-07-04 2.22 s 530 ms 0.030 1.85 s 690 ms
2026-06-27 2.25 s 529 ms 0.040 1.88 s 716 ms
2026-06-20 2.29 s 535 ms 0.040 1.90 s 733 ms
2026-06-13 2.30 s 540 ms 0.040 1.86 s 713 ms
2026-06-06 2.28 s 556 ms 0.040 1.84 s 701 ms
2026-05-30 2.29 s 594 ms 0.040 1.86 s 671 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 3.58 MB — — 3.58 MB 3.58 MB
Requests 284 — — 284 284
Third-party Weight 426.0 kB — — 426.0 kB 426.0 kB
Third-party CPU 363 ms — — 363 ms 363 ms
Unused JS 1.01 MB — — 1.01 MB 1.01 MB
Unused CSS 51.9 kB — — 51.9 kB 51.9 kB

By resource type

script 2.34 MB · 203 req
image 923.4 kB · 52 req
font 184.8 kB · 6 req
stylesheet 60.4 kB · 7 req
document 60.1 kB · 1 req
other 9.4 kB · 13 req
third party 426.0 kB · 23 req

Third parties 7 entities

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

Google Fonts 187.8 kB · 0 ms CPU
Google Tag Manager 154.3 kB · 104 ms CPU
Osano CMP 77.8 kB · 256 ms CPU
Fathom Analytics 3.2 kB · 2 ms CPU
Google/Doubleclick Ads 2.7 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 9.93 s — — 9.93 s 9.93 s
Long Tasks 20 — — 20 20
DOM Elements 8,384 — — 8,384 8,384
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 65 — — 65 65
A11y Failures 2 — — 2 2
A11y Failing Nodes 4 — — 4 4

Main thread work

script evaluation 5.30 s
other 2.43 s
style layout 1.23 s
garbage collection 383 ms
paint composite render 260 ms
script parse compile 253 ms
parse HTML 78 ms

Axe violations axe-core 4.13.0, full rule set

65 violating nodes across 2 rules, 9121 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 62 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes

Accessibility failures 2 of 20 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
  • 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 4 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 21, 2026, 5:33 AM UTC 41 6.18 s 0.040 2.99 s 3.58 MB 3/3 ±3 2,349 67.8s

Embed this score

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