firebase.google.com/products/hosting

https://firebase.google.com/products/hosting

Data from Aug 22, 2026, 11:20 PM UTC 22h old

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

The measuring machine was slower than usual.

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

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.

Go Hosted by Google Frontend

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-24 → 2026-08-20). This is what Google measures you on.

LCP 3.05 s needs-improvement

INP 194 ms good

CLS 0 good

Scores

Performance

↓ -5 (-8.2%)

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	5.02 s	5.03 s	↓ -17 ms (-0.3%)	5.02 s	8.42 s
CLS Cumulative Layout Shift	0	0	→ no change	0	0
TBT Total Blocking Time	776 ms	371 ms	↑ +405 ms (+109.2%) significant	371 ms	776 ms
FCP First Contentful Paint	3.22 s	4.58 s	↓ -1368 ms (-29.8%) significant	3.22 s	4.96 s
Speed Index	3.68 s	4.58 s	↓ -906 ms (-19.8%)	3.68 s	5.47 s
TTFB Time to First Byte	773 ms	783 ms	↓ -10 ms (-1.3%)	629 ms	783 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

5.02 s

5.03 s

↓ -17 ms (-0.3%)

5.02 s

8.42 s

CLS Cumulative Layout Shift

→ no change

TBT Total Blocking Time

776 ms

371 ms

↑ +405 ms (+109.2%) significant

371 ms

776 ms

FCP First Contentful Paint

3.22 s

4.58 s

↓ -1368 ms (-29.8%) significant

3.22 s

4.96 s

Speed Index

3.68 s

4.58 s

↓ -906 ms (-19.8%)

3.68 s

5.47 s

TTFB Time to First Byte

773 ms

783 ms

↓ -10 ms (-1.3%)

629 ms

783 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.02 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.

time to first byte 571 ms

element render delay 161 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-24 → 2026-08-20). This is what Google measures you on.

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	3.05 s	needs-improvement	61.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	194 ms	good	76.3% good
CLS CWV	0	good	97.1% good
FCP	2.96 s	needs-improvement	42.4% good
TTFB	2.14 s	poor	5% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

3.05 s

needs-improvement

61.9% good

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

194 ms

good

76.3% good

CLS CWV

good

97.1% good

FCP

2.96 s

needs-improvement

42.4% good

TTFB

2.14 s

poor

5% good

Lab vs field

Lab LCP 5.02 s · field p75 3.05 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	FCP	TTFB
2026-08-15	3.00 s	190 ms	2.87 s	2.13 s
2026-08-08	2.92 s	192 ms	2.81 s	2.08 s
2026-08-01	2.83 s	202 ms	2.73 s	2.01 s
2026-07-25	2.79 s	206 ms	2.69 s	1.99 s
2026-07-18	2.77 s	210 ms	2.68 s	1.91 s
2026-07-11	2.78 s	214 ms	2.68 s	1.86 s
2026-07-04	2.77 s	212 ms	2.63 s	1.86 s
2026-06-27	2.75 s	213 ms	2.61 s	1.83 s
2026-06-20	2.79 s	218 ms	2.62 s	1.86 s
2026-06-13	2.81 s	206 ms	2.63 s	1.89 s
2026-06-06	2.83 s	218 ms	2.68 s	1.87 s
2026-05-30	2.88 s	221 ms	2.73 s	1.92 s

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

3.00 s

190 ms

2.87 s

2.13 s

2026-08-08

2.92 s

192 ms

2.81 s

2.08 s

2026-08-01

2.83 s

202 ms

2.73 s

2.01 s

2026-07-25

2.79 s

206 ms

2.69 s

1.99 s

2026-07-18

2.77 s

210 ms

2.68 s

1.91 s

2026-07-11

2.78 s

214 ms

2.68 s

1.86 s

2026-07-04

2.77 s

212 ms

2.63 s

1.86 s

2026-06-27

2.75 s

213 ms

2.61 s

1.83 s

2026-06-20

2.79 s

218 ms

2.62 s

1.86 s

2026-06-13

2.81 s

206 ms

2.63 s

1.89 s

2026-06-06

2.83 s

218 ms

2.68 s

1.87 s

2026-05-30

2.88 s

221 ms

2.73 s

1.92 s

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	1.93 MB	1.99 MB	↓ -61.7 kB (-3.2%)	1.50 MB	1.99 MB
Requests	78	78	→ no change	76	78
Third-party Weight	1.82 MB	1.61 MB	↑ +200.2 kB (+12.7%)	1.61 MB	2.94 MB
Third-party CPU	428 ms	316 ms	↑ +112 ms (+35.5%) significant	316 ms	428 ms
Unused JS	549 kB	549 kB	↑ +10 B	381 kB	549 kB
Unused CSS	204 kB	204 kB	↓ -6 B	204 kB	204 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

1.93 MB

1.99 MB

↓ -61.7 kB (-3.2%)

1.50 MB

1.99 MB

Requests

→ no change

Third-party Weight

1.82 MB

1.61 MB

↑ +200.2 kB (+12.7%)

1.61 MB

2.94 MB

Third-party CPU

428 ms

316 ms

↑ +112 ms (+35.5%) significant

316 ms

428 ms

Unused JS

549 kB

↑ +10 B

381 kB

549 kB

Unused CSS

204 kB

↓ -6 B

204 kB

By resource type

script 1.15 MB · 50 req

image 321 kB · 10 req

font 197 kB · 3 req

stylesheet 170 kB · 6 req

document 88.8 kB · 2 req

other 1.4 kB · 7 req

third party 1.52 MB · 63 req

Third parties 3 entities

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

Google CDN 851 kB · 135 ms CPU

Google Tag Manager 764 kB · 293 ms CPU

Google Fonts 205 kB · 0 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	3.69 s	2.78 s	↑ +909 ms (+32.6%) significant	2.53 s	3.69 s
Long Tasks	14	11	↑ +3 (+27.3%)	10	14
DOM Elements	762	762	→ no change	762	762
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	7	7	→ no change	7	7
A11y Failures	1	1	→ no change	1	1
A11y Failing Nodes	4	4	→ no change	4	4

Main thread work

script evaluation 1.85 s

other 832 ms

style layout 461 ms

script parse compile 341 ms

parse HTML 118 ms

paint composite render 81 ms

garbage collection 10 ms

Axe violations axe-core 4.13.0, full rule set

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

critical image-alt — Images must have alternative text 4 nodes
moderate landmark-main-is-top-level — Main landmark should not be contained in another landmark 1 node
moderate landmark-no-duplicate-main — Document should not have more than one main landmark 1 node
moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 1 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.

image-alt — Image elements do not have `[alt]` attributes 4 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	TBT	Weight	Runs	Spread	Bench	Took
Aug 22, 2026, 11:20 PM UTC	56	5.02 s	776 ms	1.93 MB	3/3	±8	2,463	40.7s
Aug 21, 2026, 10:23 PM UTC	61	5.03 s	371 ms	1.99 MB	3/3	±5	3,025	35.8s
Aug 20, 2026, 9:34 PM UTC	53	8.42 s	386 ms	1.50 MB	3/3	±4	3,198	39.8s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 22, 2026, 11:20 PM UTC

5.02 s

776 ms

1.93 MB

3/3

±8

2,463

40.7s

Aug 21, 2026, 10:23 PM UTC

5.03 s

371 ms

1.99 MB

3/3

±5

3,025

35.8s

Aug 20, 2026, 9:34 PM UTC

8.42 s

386 ms

1.50 MB

3/3

±4

3,198

39.8s

Embed this score

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