surge.sh

Data from Aug 23, 2026, 9:26 AM UTC 12h old

Web Hosts #12 · 3 measurements · since Aug 21, 2026

The measuring machine was slower than usual.

Lighthouse benchmark index was 2333.5 against a baseline of 3223.8 (-27.6%). CPU-bound metrics — TBT, TTI, main thread work — are affected by this and may have moved without the site changing at all.

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.56 s needs-improvement

INP 109 ms good

CLS 0.010 good

Scores

Performance

↓ -2 (-2.3%)

Accessibility

no change

Best Practices

no change

SEO

no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.25 s.

407 ms
813 ms
1.22 s
1.63 s
2.03 s
2.44 s
2.85 s
3.25 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	4.23 s	4.00 s	↑ +222 ms (+5.5%) significant	4.00 s	4.23 s
CLS Cumulative Layout Shift	0.044	0.013	↑ +0.031 (+238.5%) significant	0.005	0.044
TBT Total Blocking Time	0 ms	0 ms	→ no change	0 ms	0 ms
FCP First Contentful Paint	1.57 s	1.53 s	↑ +37 ms (+2.4%)	1.53 s	1.57 s
Speed Index	1.57 s	1.53 s	↑ +37 ms (+2.4%)	1.53 s	1.57 s
TTFB Time to First Byte	623 ms	622 ms	↑ +1 ms (+0.2%)	620 ms	623 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

4.23 s

4.00 s

↑ +222 ms (+5.5%) significant

4.00 s

4.23 s

CLS Cumulative Layout Shift

0.044

0.013

↑ +0.031 (+238.5%) significant

0.005

0.044

TBT Total Blocking Time

0 ms

→ no change

0 ms

FCP First Contentful Paint

1.57 s

1.53 s

↑ +37 ms (+2.4%)

1.53 s

1.57 s

Speed Index

1.57 s

1.53 s

↑ +37 ms (+2.4%)

1.53 s

1.57 s

TTFB Time to First Byte

623 ms

622 ms

↑ +1 ms (+0.2%)

620 ms

623 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 4.23 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 206 ms

time to first byte 22 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.56 s	needs-improvement	73.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	109 ms	good	89.7% good
CLS CWV	0.010	good	93.8% good
FCP	2.48 s	needs-improvement	57.2% good
TTFB	1.40 s	needs-improvement	46.8% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.56 s

needs-improvement

73.4% good

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

109 ms

good

89.7% good

CLS CWV

0.010

good

93.8% good

FCP

2.48 s

needs-improvement

57.2% good

TTFB

1.40 s

needs-improvement

46.8% good

Lab vs field

Lab LCP 4.23 s · field p75 2.56 s · real users are 0.61× 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.52 s	103 ms	0.010	2.45 s	1.41 s
2026-08-08	2.50 s	105 ms	0.010	2.42 s	1.39 s
2026-08-01	2.49 s	104 ms	0.010	2.42 s	1.42 s
2026-07-25	2.50 s	103 ms	0.010	2.42 s	1.44 s
2026-07-18	2.52 s	105 ms	0.010	2.43 s	1.43 s
2026-07-11	2.58 s	103 ms	0.010	2.48 s	1.45 s
2026-07-04	2.54 s	98 ms	0.010	2.44 s	1.42 s
2026-06-27	2.47 s	99 ms	0.010	2.37 s	1.37 s
2026-06-20	2.47 s	97 ms	0	2.39 s	1.40 s
2026-06-13	2.24 s	96 ms	0	2.15 s	1.25 s
2026-06-06	2.25 s	96 ms	0	2.15 s	1.25 s
2026-05-30	2.27 s	96 ms	0	2.18 s	1.27 s

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.52 s

103 ms

0.010

2.45 s

1.41 s

2026-08-08

2.50 s

105 ms

0.010

2.42 s

1.39 s

2026-08-01

2.49 s

104 ms

0.010

2.42 s

1.42 s

2026-07-25

2.50 s

103 ms

0.010

2.42 s

1.44 s

2026-07-18

2.52 s

105 ms

0.010

2.43 s

1.43 s

2026-07-11

2.58 s

103 ms

0.010

2.48 s

1.45 s

2026-07-04

2.54 s

98 ms

0.010

2.44 s

1.42 s

2026-06-27

2.47 s

99 ms

0.010

2.37 s

1.37 s

2026-06-20

2.47 s

97 ms

2.39 s

1.40 s

2026-06-13

2.24 s

96 ms

2.15 s

1.25 s

2026-06-06

2.25 s

96 ms

2.15 s

1.25 s

2026-05-30

2.27 s

96 ms

2.18 s

1.27 s

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	1.78 MB	1.78 MB	↓ -2.7 kB (-0.2%)	1.78 MB	1.78 MB
Requests	50	50	→ no change	50	50
Third-party Weight	215 kB	215 kB	↑ +5 B	215 kB	215 kB
Third-party CPU	14 ms	15 ms	↓ -1 ms (-4.1%)	14 ms	15 ms
Unused JS	0 B	0 B	→ no change	0 B	0 B
Unused CSS	0 B	0 B	→ no change	0 B	0 B

Metric

Current

Change

Best

Worst

Trend

Page Weight

1.78 MB

↓ -2.7 kB (-0.2%)

1.78 MB

Requests

→ no change

Third-party Weight

215 kB

↑ +5 B

215 kB

Third-party CPU

14 ms

15 ms

↓ -1 ms (-4.1%)

14 ms

15 ms

Unused JS

0 B

→ no change

0 B

Unused CSS

0 B

→ no change

0 B

By resource type

script 973 kB · 9 req

image 401 kB · 19 req

font 213 kB · 6 req

stylesheet 70.8 kB · 4 req

document 66.6 kB · 2 req

other 57.6 kB · 10 req

third party 1.29 MB · 24 req

Third parties 2 entities

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

Adobe TypeKit 185 kB · 3 ms CPU

Google CDN 29.8 kB · 12 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	993 ms	833 ms	↑ +161 ms (+19.3%) significant	790 ms	993 ms
Long Tasks	1	1	→ no change	1	1
DOM Elements	528	531	↓ -3 (-0.6%)	527	531
A11y Failures	6	6	→ no change	6	6
A11y Failing Nodes	85	84	↑ +1 (+1.2%)	82	85

Main thread work

other 381 ms

style layout 317 ms

script evaluation 140 ms

paint composite render 100 ms

parse HTML 30 ms

script parse compile 27 ms

Axe violations axe-core , full rule set

The axe run failed: Navigation timeout of 120000 ms exceeded

Accessibility failures 6 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. 72 nodes
image-alt — Image elements do not have `[alt]` attributes 7 nodes
link-in-text-block — Links rely on color to be distinguishable. 3 nodes
aria-prohibited-attr — Elements use prohibited ARIA attributes 1 node
frame-title — `<frame>` or `<iframe>` elements do not have a title 1 node
html-has-lang — `<html>` element does not have a `[lang]` attribute 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1

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	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 9:26 AM UTC	85	4.23 s	0.044	1.78 MB	3/3	±13	2,334	152s
Aug 22, 2026, 9:25 AM UTC	87	4.00 s	0.013	1.78 MB	3/3	±15	3,185	154.1s
Aug 21, 2026, 8:40 AM UTC	87	4.01 s	0.005	1.78 MB	3/3	±34	3,263	147.8s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 9:26 AM UTC

4.23 s

0.044

0 ms

1.78 MB

3/3

±13

2,334

152s

Aug 22, 2026, 9:25 AM UTC

4.00 s

0.013

0 ms

1.78 MB

3/3

±15

3,185

154.1s

Aug 21, 2026, 8:40 AM UTC

4.01 s

0.005

0 ms

1.78 MB

3/3

±34

3,263

147.8s

Embed this score

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