heroku.com

https://www.heroku.com/

Data from Aug 23, 2026, 12:39 PM UTC 10h old

Web Hosts #1 · 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 Self-hosted

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

INP 146 ms good

CLS 0 good

Scores

Performance

↑ +5 (+6.9%)

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.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	3.08 s	2.58 s	↑ +496 ms (+19.2%)	2.58 s	3.08 s
CLS Cumulative Layout Shift	0.017	0.017	→ no change	0.017	0.017
TBT Total Blocking Time	543 ms	998 ms	↓ -455 ms (-45.6%)	543 ms	998 ms
FCP First Contentful Paint	2.47 s	2.17 s	↑ +295 ms (+13.6%)	2.17 s	2.47 s
Speed Index	2.84 s	2.95 s	↓ -111 ms (-3.8%)	2.84 s	2.95 s
TTFB Time to First Byte	603 ms	632 ms	↓ -29 ms (-4.6%)	603 ms	632 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

3.08 s

2.58 s

↑ +496 ms (+19.2%)

2.58 s

3.08 s

CLS Cumulative Layout Shift

0.017

→ no change

0.017

TBT Total Blocking Time

543 ms

998 ms

↓ -455 ms (-45.6%)

543 ms

998 ms

FCP First Contentful Paint

2.47 s

2.17 s

↑ +295 ms (+13.6%)

2.17 s

2.47 s

Speed Index

2.84 s

2.95 s

↓ -111 ms (-3.8%)

2.84 s

2.95 s

TTFB Time to First Byte

603 ms

632 ms

↓ -29 ms (-4.6%)

603 ms

632 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 3.08 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 130 ms

time to first byte 4 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	1.49 s	good	90.8% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	146 ms	good	86.3% good
CLS CWV	0	good	96.9% good
FCP	1.30 s	good	86.2% good
TTFB	617 ms	good	82.7% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.49 s

good

90.8% good

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

146 ms

good

86.3% good

CLS CWV

good

96.9% good

FCP

1.30 s

good

86.2% good

TTFB

617 ms

good

82.7% good

Lab vs field

Lab LCP 3.08 s · field p75 1.49 s · real users are 0.48× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	FCP	TTFB
2026-08-15	1.52 s	146 ms	1.33 s	627 ms
2026-08-08	1.45 s	148 ms	1.29 s	616 ms
2026-08-01	1.54 s	147 ms	1.35 s	657 ms
2026-07-25	1.53 s	148 ms	1.35 s	664 ms
2026-07-18	1.51 s	148 ms	1.33 s	671 ms
2026-07-11	1.66 s	150 ms	1.42 s	726 ms
2026-07-04	1.55 s	154 ms	1.36 s	695 ms
2026-06-27	1.55 s	155 ms	1.37 s	700 ms
2026-06-20	1.53 s	155 ms	1.35 s	698 ms
2026-06-13	1.45 s	154 ms	1.28 s	660 ms
2026-06-06	1.47 s	152 ms	1.29 s	665 ms
2026-05-30	1.47 s	152 ms	1.29 s	656 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.52 s

146 ms

1.33 s

627 ms

2026-08-08

1.45 s

148 ms

1.29 s

616 ms

2026-08-01

1.54 s

147 ms

1.35 s

657 ms

2026-07-25

1.53 s

148 ms

1.35 s

664 ms

2026-07-18

1.51 s

148 ms

1.33 s

671 ms

2026-07-11

1.66 s

150 ms

1.42 s

726 ms

2026-07-04

1.55 s

154 ms

1.36 s

695 ms

2026-06-27

1.55 s

155 ms

1.37 s

700 ms

2026-06-20

1.53 s

155 ms

1.35 s

698 ms

2026-06-13

1.45 s

154 ms

1.28 s

660 ms

2026-06-06

1.47 s

152 ms

1.29 s

665 ms

2026-05-30

1.47 s

152 ms

1.29 s

656 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	2.65 MB	2.65 MB	↓ -7 B	2.65 MB	2.65 MB
Requests	107	107	→ no change	106	107
Third-party Weight	1.06 MB	1.06 MB	↑ +56 B	1.06 MB	1.06 MB
Third-party CPU	259 ms	360 ms	↓ -100 ms (-27.9%)	259 ms	360 ms
Unused JS	737 kB	737 kB	↑ +38 B	737 kB	737 kB
Unused CSS	97.7 kB	97.7 kB	→ no change	97.7 kB	97.7 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

2.65 MB

↓ -7 B

2.65 MB

Requests

107

→ no change

106

107

Third-party Weight

1.06 MB

↑ +56 B

1.06 MB

Third-party CPU

259 ms

360 ms

↓ -100 ms (-27.9%)

259 ms

360 ms

Unused JS

737 kB

↑ +38 B

737 kB

Unused CSS

97.7 kB

→ no change

97.7 kB

By resource type

script 1.70 MB · 49 req

other 466 kB · 16 req

font 212 kB · 6 req

stylesheet 130 kB · 7 req

document 80.0 kB · 2 req

image 61.9 kB · 25 req

third party 1.17 MB · 30 req

Third parties 10 entities

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

Google Tag Manager 512 kB · 153 ms CPU

Google CDN 320 kB · 79 ms CPU

herokucdn.com 146 kB · 0 ms CPU

LinkedIn Ads 41.1 kB · 10 ms CPU

Parse.ly 22.9 kB · 14 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	3.80 s	5.15 s	↓ -1346 ms (-26.1%)	3.80 s	5.15 s
Long Tasks	18	20	↓ -2 (-10%)	18	20
DOM Elements	2,315	2,315	→ no change	2,312	2,315
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	4	4	→ no change	4	4
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	12	12	→ no change	12	12

Main thread work

script evaluation 2.03 s

other 693 ms

style layout 411 ms

script parse compile 325 ms

parse HTML 173 ms

paint composite render 117 ms

garbage collection 55 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 3 rules, 1556 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.

serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 29 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.

target-size — Touch targets do not have sufficient size or spacing. 10 nodes
color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 2 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 1 console error

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, 12:39 PM UTC	77	3.08 s	0.017	543 ms	2.65 MB	3/3	±10	2,977	38.9s
Aug 22, 2026, 11:21 AM UTC	72	2.58 s	0.017	998 ms	2.65 MB	3/3	±5	2,475	45.6s
Aug 21, 2026, 10:39 AM UTC	76	2.94 s	0.017	628 ms	2.65 MB	3/3	±2	2,918	38.7s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 12:39 PM UTC

3.08 s

0.017

543 ms

2.65 MB

3/3

±10

2,977

38.9s

Aug 22, 2026, 11:21 AM UTC

2.58 s

0.017

998 ms

2.65 MB

3/3

±5

2,475

45.6s

Aug 21, 2026, 10:39 AM UTC

2.94 s

0.017

628 ms

2.65 MB

3/3

±2

2,918

38.7s

Embed this score

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