render.com

https://render.com/

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

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

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.17 s good

INP 307 ms needs-improvement

CLS 0.010 good

Scores

Performance

↓ -2 (-8.7%)

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 4.11 s.

514 ms
1.03 s
1.54 s
2.06 s
2.57 s
3.08 s
3.60 s
4.11 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	8.21 s	7.80 s	↑ +408 ms (+5.2%)	7.64 s	8.21 s
CLS Cumulative Layout Shift	0.831	0.832	↓ -0.001 (-0.1%)	0.831	0.832
TBT Total Blocking Time	2.06 s	2.11 s	↓ -58 ms (-2.7%)	2.03 s	2.11 s
FCP First Contentful Paint	2.05 s	1.57 s	↑ +479 ms (+30.5%) significant	1.56 s	2.05 s
Speed Index	3.00 s	3.00 s	↑ +3 ms (+0.1%)	3.00 s	3.93 s
TTFB Time to First Byte	651 ms	673 ms	↓ -22 ms (-3.3%)	651 ms	673 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

8.21 s

7.80 s

↑ +408 ms (+5.2%)

7.64 s

8.21 s

CLS Cumulative Layout Shift

0.831

0.832

↓ -0.001 (-0.1%)

0.831

0.832

TBT Total Blocking Time

2.06 s

2.11 s

↓ -58 ms (-2.7%)

2.03 s

2.11 s

FCP First Contentful Paint

2.05 s

1.57 s

↑ +479 ms (+30.5%) significant

1.56 s

2.05 s

Speed Index

3.00 s

↑ +3 ms (+0.1%)

3.00 s

3.93 s

TTFB Time to First Byte

651 ms

673 ms

↓ -22 ms (-3.3%)

651 ms

673 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 8.21 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 211 ms

time to first byte 86 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.17 s	good	80.6% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	307 ms	needs-improvement	56.2% good
CLS CWV	0.010	good	83.4% good
FCP	1.84 s	needs-improvement	74% good
TTFB	1.09 s	needs-improvement	59.8% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.17 s

good

80.6% good

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

307 ms

needs-improvement

56.2% good

CLS CWV

0.010

good

83.4% good

FCP

1.84 s

needs-improvement

74% good

TTFB

1.09 s

needs-improvement

59.8% good

Lab vs field

Lab LCP 8.21 s · field p75 2.17 s · real users are 0.26× 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.17 s	307 ms	0.010	1.85 s	1.08 s
2026-08-08	2.19 s	309 ms	0.010	1.86 s	1.09 s
2026-08-01	2.21 s	303 ms	0.010	1.87 s	1.09 s
2026-07-25	2.22 s	297 ms	0.020	1.87 s	1.09 s
2026-07-18	2.23 s	297 ms	0.020	1.87 s	1.09 s
2026-07-11	2.23 s	294 ms	0.030	1.87 s	1.08 s
2026-07-04	2.20 s	296 ms	0.030	1.85 s	1.07 s
2026-06-27	2.19 s	299 ms	0.030	1.84 s	1.06 s
2026-06-20	2.18 s	304 ms	0.020	1.83 s	1.05 s
2026-06-13	2.17 s	307 ms	0.010	1.83 s	1.03 s
2026-06-06	2.18 s	312 ms	0.010	1.84 s	1.04 s
2026-05-30	2.18 s	309 ms	0.010	1.84 s	1.04 s

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.17 s

307 ms

0.010

1.85 s

1.08 s

2026-08-08

2.19 s

309 ms

0.010

1.86 s

1.09 s

2026-08-01

2.21 s

303 ms

0.010

1.87 s

1.09 s

2026-07-25

2.22 s

297 ms

0.020

1.87 s

1.09 s

2026-07-18

2.23 s

297 ms

0.020

1.87 s

1.09 s

2026-07-11

2.23 s

294 ms

0.030

1.87 s

1.08 s

2026-07-04

2.20 s

296 ms

0.030

1.85 s

1.07 s

2026-06-27

2.19 s

299 ms

0.030

1.84 s

1.06 s

2026-06-20

2.18 s

304 ms

0.020

1.83 s

1.05 s

2026-06-13

2.17 s

307 ms

0.010

1.83 s

1.03 s

2026-06-06

2.18 s

312 ms

0.010

1.84 s

1.04 s

2026-05-30

2.18 s

309 ms

0.010

1.84 s

1.04 s

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	2.63 MB	2.63 MB	↓ -784 B	2.62 MB	2.63 MB
Requests	142	142	→ no change	142	142
Third-party Weight	957 kB	957 kB	↑ +359 B	953 kB	957 kB
Third-party CPU	298 ms	294 ms	↑ +4 ms (+1.4%)	294 ms	305 ms
Unused JS	346 kB	346 kB	↓ -499 B (-0.1%)	346 kB	416 kB
Unused CSS	34.1 kB	34.1 kB	→ no change	34.1 kB	34.1 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

2.63 MB

↓ -784 B

2.62 MB

2.63 MB

Requests

142

→ no change

142

Third-party Weight

957 kB

↑ +359 B

953 kB

957 kB

Third-party CPU

298 ms

294 ms

↑ +4 ms (+1.4%)

294 ms

305 ms

Unused JS

346 kB

↓ -499 B (-0.1%)

346 kB

416 kB

Unused CSS

34.1 kB

→ no change

34.1 kB

By resource type

script 1.53 MB · 83 req

font 641 kB · 11 req

image 285 kB · 24 req

document 81.0 kB · 1 req

other 55.3 kB · 14 req

stylesheet 41.4 kB · 3 req

third party 957 kB · 45 req

Third parties 8 entities

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

Google Tag Manager 501 kB · 186 ms CPU

sanity.io 284 kB · 0 ms CPU

posthog.com 128 kB · 81 ms CPU

LinkedIn Ads 41.3 kB · 29 ms CPU

SalesLoft 2.5 kB · 1 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	8.80 s	8.32 s	↑ +481 ms (+5.8%) significant	8.27 s	8.80 s
Long Tasks	20	20	→ no change	20	20
DOM Elements	2,553	2,553	→ no change	2,552	2,553
A11y Failures	4	4	→ no change	4	4
A11y Failing Nodes	95	95	→ no change	95	95

Main thread work

script evaluation 5.43 s

other 1.68 s

style layout 670 ms

script parse compile 503 ms

paint composite render 247 ms

garbage collection 161 ms

parse HTML 115 ms

Axe violations axe-core , full rule set

The axe run failed: Navigation timeout of 120000 ms exceeded

Accessibility failures 4 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. 47 nodes
svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 45 nodes
button-name — Buttons do not have an accessible name 2 nodes
meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 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 2 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:33 AM UTC	21	8.21 s	0.831	2.06 s	2.63 MB	3/3	±24	2,496	171.9s
Aug 22, 2026, 6:40 AM UTC	23	7.80 s	0.832	2.11 s	2.63 MB	3/3	±24	2,297	167.5s
Aug 21, 2026, 5:36 AM UTC	22	7.64 s	0.832	2.03 s	2.62 MB	3/3	±23	2,386	167.6s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 7:33 AM UTC

8.21 s

0.831

2.06 s

2.63 MB

3/3

±24

2,496

171.9s

Aug 22, 2026, 6:40 AM UTC

7.80 s

0.832

2.11 s

2.63 MB

3/3

±24

2,297

167.5s

Aug 21, 2026, 5:36 AM UTC

7.64 s

0.832

2.03 s

2.62 MB

3/3

±23

2,386

167.6s

Embed this score

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