railway.com

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

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

Hosted by Railway

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 2.04 s good

INP 598 ms poor

CLS 0.030 good

Scores

Performance

↑ +8 (+23.5%)

Accessibility

no change

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.

375 ms
750 ms
1.13 s
1.50 s
1.88 s
2.25 s
2.63 s
3.00 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	5.42 s	7.55 s	↓ -2134 ms (-28.2%)	5.42 s	7.55 s
CLS Cumulative Layout Shift	0.040	0.040	→ no change	0.040	0.040
TBT Total Blocking Time	3.05 s	2.00 s	↑ +1052 ms (+52.5%)	2.00 s	3.05 s
FCP First Contentful Paint	3.37 s	5.48 s	↓ -2113 ms (-38.5%)	3.37 s	5.48 s
Speed Index	4.04 s	5.48 s	↓ -1440 ms (-26.3%)	3.83 s	5.48 s
TTFB Time to First Byte	620 ms	653 ms	↓ -33 ms (-5.1%)	620 ms	653 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

5.42 s

7.55 s

↓ -2134 ms (-28.2%)

5.42 s

7.55 s

CLS Cumulative Layout Shift

0.040

→ no change

0.040

TBT Total Blocking Time

3.05 s

2.00 s

↑ +1052 ms (+52.5%)

2.00 s

3.05 s

FCP First Contentful Paint

3.37 s

5.48 s

↓ -2113 ms (-38.5%)

3.37 s

5.48 s

Speed Index

4.04 s

5.48 s

↓ -1440 ms (-26.3%)

3.83 s

5.48 s

TTFB Time to First Byte

620 ms

653 ms

↓ -33 ms (-5.1%)

620 ms

653 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 5.42 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 164 ms

resource load duration 22 ms

resource load delay 15 ms

time to first byte 10 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	2.04 s	good	82.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	598 ms	poor	37.9% good
CLS CWV	0.030	good	83.5% good
FCP	1.72 s	good	76.8% good
TTFB	596 ms	good	82.7% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.04 s

good

82.2% good

INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run

598 ms

poor

37.9% good

CLS CWV

0.030

good

83.5% good

FCP

1.72 s

good

76.8% good

TTFB

596 ms

good

82.7% good

Lab vs field

Lab LCP 5.42 s · field p75 2.04 s · real users are 0.38× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	CLS	FCP	TTFB
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

Week ending

LCP

INP

CLS

FCP

TTFB

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
Page Weight	3.58 MB	3.95 MB	↓ -356.8 kB (-9.3%)	3.58 MB	3.95 MB
Requests	284	285	↓ -1 (-0.4%)	284	285
Third-party Weight	423 kB	423 kB	↑ +120 B	423 kB	426 kB
Third-party CPU	411 ms	146 ms	↑ +265 ms (+181.9%)	146 ms	411 ms
Unused JS	1.02 MB	991 kB	↑ +25.7 kB (+2.7%)	991 kB	1.02 MB
Unused CSS	51.9 kB	51.9 kB	↑ +38 B (+0.1%)	51.9 kB	51.9 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

3.58 MB

3.95 MB

↓ -356.8 kB (-9.3%)

3.58 MB

3.95 MB

Requests

284

285

↓ -1 (-0.4%)

284

285

Third-party Weight

423 kB

↑ +120 B

423 kB

426 kB

Third-party CPU

411 ms

146 ms

↑ +265 ms (+181.9%)

146 ms

411 ms

Unused JS

1.02 MB

991 kB

↑ +25.7 kB (+2.7%)

991 kB

1.02 MB

Unused CSS

51.9 kB

↑ +38 B (+0.1%)

51.9 kB

By resource type

script 2.34 MB · 203 req

image 923 kB · 52 req

font 185 kB · 6 req

stylesheet 60.5 kB · 7 req

document 60.1 kB · 1 req

other 9.1 kB · 13 req

third party 423 kB · 23 req

Third parties 7 entities

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

Google Fonts 188 kB · 0 ms CPU

Google Tag Manager 154 kB · 151 ms CPU

Osano CMP 74.7 kB · 257 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
Main Thread Work	9.89 s	8.34 s	↑ +1547 ms (+18.5%)	8.34 s	9.93 s
Long Tasks	20	20	→ no change	20	20
DOM Elements	8,384	8,384	→ no change	8,384	8,384
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	65	65	→ no change	65	65
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	4	4	→ no change	4	4

Main thread work

script evaluation 5.36 s

other 2.48 s

style layout 1.09 s

garbage collection 411 ms

script parse compile 241 ms

paint composite render 238 ms

parse HTML 79 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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 7:32 AM UTC	42	5.42 s	0.040	3.05 s	3.58 MB	3/3	±19	2,466	77.3s
Aug 22, 2026, 6:38 AM UTC	34	7.55 s	0.040	2.00 s	3.95 MB	3/3	±14	2,316	66.2s
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

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 7:32 AM UTC

5.42 s

0.040

3.05 s

3.58 MB

3/3

±19

2,466

77.3s

Aug 22, 2026, 6:38 AM UTC

7.55 s

0.040

2.00 s

3.95 MB

3/3

±14

2,316

66.2s

Aug 21, 2026, 5:33 AM UTC

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 speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://railway.com/"></speedlify2-score>