fastly.com

https://www.fastly.com/

Data from Aug 23, 2026, 12:37 PM UTC 9h old

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

Built with Gatsby 5.16.1

Ar Hosted by Artisanal bits

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

INP 291 ms needs-improvement

CLS 0.060 good

Scores

Performance

↑ +2 (+5.1%)

Accessibility

↑ +4 (+4.8%)

Best Practices

no change

100

SEO

↑ +8 (+8.7%)

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	9.42 s	9.67 s	↓ -243 ms (-2.5%)	9.42 s	12.03 s
CLS Cumulative Layout Shift	0.055	0.055	→ no change	0.055	0.055
TBT Total Blocking Time	1.61 s	2.24 s	↓ -631 ms (-28.2%)	1.34 s	2.24 s
FCP First Contentful Paint	3.42 s	3.48 s	↓ -65 ms (-1.9%)	3.42 s	3.48 s
Speed Index	3.42 s	3.56 s	↓ -145 ms (-4.1%)	3.42 s	3.99 s
TTFB Time to First Byte	607 ms	610 ms	↓ -3 ms (-0.5%)	605 ms	610 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

9.42 s

9.67 s

↓ -243 ms (-2.5%)

9.42 s

12.03 s

CLS Cumulative Layout Shift

0.055

→ no change

0.055

TBT Total Blocking Time

1.61 s

2.24 s

↓ -631 ms (-28.2%)

1.34 s

2.24 s

FCP First Contentful Paint

3.42 s

3.48 s

↓ -65 ms (-1.9%)

3.42 s

3.48 s

Speed Index

3.42 s

3.56 s

↓ -145 ms (-4.1%)

3.42 s

3.99 s

TTFB Time to First Byte

607 ms

610 ms

↓ -3 ms (-0.5%)

605 ms

610 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 9.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 389 ms

resource load delay 16 ms

resource load duration 14 ms

time to first byte 6 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.95 s	needs-improvement	65.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	291 ms	needs-improvement	62.7% good
CLS CWV	0.060	good	94.4% good
FCP	2.51 s	needs-improvement	50.9% good
TTFB	803 ms	needs-improvement	74.9% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

2.95 s

needs-improvement

65.9% good

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

291 ms

needs-improvement

62.7% good

CLS CWV

0.060

good

94.4% good

FCP

2.51 s

needs-improvement

50.9% good

TTFB

803 ms

needs-improvement

74.9% good

Lab vs field

Lab LCP 9.42 s · field p75 2.95 s · real users are 0.31× 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.84 s	287 ms	0.060	2.40 s	763 ms
2026-08-08	2.88 s	290 ms	0.060	2.42 s	777 ms
2026-08-01	2.85 s	288 ms	0.060	2.40 s	747 ms
2026-07-25	3.03 s	286 ms	0.050	2.63 s	913 ms
2026-07-18	3.39 s	286 ms	0.040	2.92 s	1.05 s
2026-07-11	3.54 s	281 ms	0.030	2.98 s	1.07 s
2026-07-04	3.54 s	280 ms	0.040	2.98 s	1.10 s
2026-06-27	3.50 s	288 ms	0.050	2.99 s	1.13 s
2026-06-20	3.45 s	292 ms	0.060	2.94 s	1.17 s
2026-06-13	3.40 s	293 ms	0.060	2.87 s	1.16 s
2026-06-06	3.44 s	290 ms	0.060	2.85 s	1.12 s
2026-05-30	3.18 s	270 ms	0.060	2.61 s	860 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

2.84 s

287 ms

0.060

2.40 s

763 ms

2026-08-08

2.88 s

290 ms

0.060

2.42 s

777 ms

2026-08-01

2.85 s

288 ms

0.060

2.40 s

747 ms

2026-07-25

3.03 s

286 ms

0.050

2.63 s

913 ms

2026-07-18

3.39 s

286 ms

0.040

2.92 s

1.05 s

2026-07-11

3.54 s

281 ms

0.030

2.98 s

1.07 s

2026-07-04

3.54 s

280 ms

0.040

2.98 s

1.10 s

2026-06-27

3.50 s

288 ms

0.050

2.99 s

1.13 s

2026-06-20

3.45 s

292 ms

0.060

2.94 s

1.17 s

2026-06-13

3.40 s

293 ms

0.060

2.87 s

1.16 s

2026-06-06

3.44 s

290 ms

0.060

2.85 s

1.12 s

2026-05-30

3.18 s

270 ms

0.060

2.61 s

860 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	3.08 MB	3.06 MB	↑ +26.4 kB (+0.9%)	3.06 MB	3.08 MB
Requests	147	150	↓ -3 (-2%)	139	150
Third-party Weight	708 kB	709 kB	↓ -504 B (-0.1%)	707 kB	709 kB
Third-party CPU	486 ms	521 ms	↓ -35 ms (-6.7%)	406 ms	521 ms
Unused JS	548 kB	551 kB	↓ -3.2 kB (-0.6%)	548 kB	551 kB
Unused CSS	75.5 kB	75.5 kB	→ no change	75.5 kB	75.5 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

3.08 MB

3.06 MB

↑ +26.4 kB (+0.9%)

3.06 MB

3.08 MB

Requests

147

150

↓ -3 (-2%)

139

150

Third-party Weight

708 kB

709 kB

↓ -504 B (-0.1%)

707 kB

709 kB

Third-party CPU

486 ms

521 ms

↓ -35 ms (-6.7%)

406 ms

521 ms

Unused JS

548 kB

551 kB

↓ -3.2 kB (-0.6%)

548 kB

551 kB

Unused CSS

75.5 kB

→ no change

75.5 kB

By resource type

script 2.09 MB · 41 req

image 462 kB · 29 req

font 258 kB · 5 req

document 155 kB · 7 req

other 114 kB · 61 req

stylesheet 227 B · 1 req

third party 1.35 MB · 105 req

Third parties 24 entities

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

Pendo 192 kB · 69 ms CPU

Facebook 151 kB · 58 ms CPU

intellimize.co 114 kB · 243 ms CPU

LinkedIn Ads 41.3 kB · 21 ms CPU

zoominfo.com 35.9 kB · 9 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	5.79 s	7.55 s	↓ -1767 ms (-23.4%)	5.79 s	7.55 s
Long Tasks	19	20	↓ -1 (-5%) significant	19	20
DOM Elements	1,193	1,205	↓ -12 (-1%)	1,193	1,205
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	14	22	↓ -8 (-36.4%)	14	22
A11y Failures	5	6	↓ -1 (-16.7%)	5	6
A11y Failing Nodes	13	15	↓ -2 (-13.3%)	13	15

Main thread work

script evaluation 3.52 s

other 1.09 s

script parse compile 457 ms

style layout 419 ms

parse HTML 104 ms

paint composite render 101 ms

garbage collection 100 ms

Axe violations axe-core 4.13.0, full rule set

14 violating nodes across 7 rules, 1525 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 4 nodes
moderate region — All page content should be contained by landmarks 4 nodes
critical button-name — Buttons must have discernible text 2 nodes
moderate heading-order — Heading levels should only increase by one 1 node
serious link-name — Links must have discernible text 1 node
serious nested-interactive — Interactive controls must not be nested 1 node
serious svg-img-alt — <svg> elements with an img or image role must have alternative text 1 node

Accessibility failures 5 of 33 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.

button-name — Buttons do not have an accessible name 6 nodes
color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 4 nodes
heading-order — Heading elements are not in a sequentially-descending order 1 node
link-name — Links do not have a discernible name 1 node
svg-img-alt — SVG elements with an `img` role do not have an accessible text alternative 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

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:37 PM UTC	41	9.42 s	0.055	1.61 s	3.08 MB	3/3	±11	2,923	86.7s
Aug 22, 2026, 11:20 AM UTC	39	9.67 s	0.055	2.24 s	3.06 MB	3/3	±11	2,504	61.9s
Aug 21, 2026, 10:30 AM UTC	41	12.03 s	0.055	1.34 s	3.07 MB	3/3	±10	2,986	48.5s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 12:37 PM UTC

9.42 s

0.055

1.61 s

3.08 MB

3/3

±11

2,923

86.7s

Aug 22, 2026, 11:20 AM UTC

9.67 s

0.055

2.24 s

3.06 MB

3/3

±11

2,504

61.9s

Aug 21, 2026, 10:30 AM UTC

12.03 s

0.055

1.34 s

3.07 MB

3/3

±10

2,986

48.5s

Embed this score

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