gohugo.io

Data from Aug 23, 2026, 1:15 AM UTC 20h old

Site Generators #10 · 3 measurements · since Aug 20, 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 Hugo 0.165.0

Hosted by Netlify

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

INP 76 ms good

CLS 0 good

Scores

Performance

↑ +10 (+11.4%)

Accessibility

no change

100

Best Practices

no change

100

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	2.15 s	3.62 s	↓ -1464 ms (-40.5%)	2.15 s	3.62 s
CLS Cumulative Layout Shift	0	0	→ no change	0	0
TBT Total Blocking Time	92 ms	144 ms	↓ -52 ms (-36.1%)	92 ms	144 ms
FCP First Contentful Paint	945 ms	1.22 s	↓ -271 ms (-22.3%)	945 ms	1.22 s
Speed Index	983 ms	3.07 s	↓ -2083 ms (-67.9%)	983 ms	3.07 s
TTFB Time to First Byte	608 ms	670 ms	↓ -62 ms (-9.3%)	608 ms	670 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

2.15 s

3.62 s

↓ -1464 ms (-40.5%)

2.15 s

3.62 s

CLS Cumulative Layout Shift

→ no change

TBT Total Blocking Time

92 ms

144 ms

↓ -52 ms (-36.1%)

92 ms

144 ms

FCP First Contentful Paint

945 ms

1.22 s

↓ -271 ms (-22.3%)

945 ms

1.22 s

Speed Index

983 ms

3.07 s

↓ -2083 ms (-67.9%)

983 ms

3.07 s

TTFB Time to First Byte

608 ms

670 ms

↓ -62 ms (-9.3%)

608 ms

670 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 2.15 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 68 ms

time to first byte 13 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.28 s	good	92.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	76 ms	good	95.6% good
CLS CWV	0	good	97.4% good
FCP	1.30 s	good	86.5% good
TTFB	711 ms	good	79.3% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.28 s

good

92.9% good

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

76 ms

good

95.6% good

CLS CWV

good

97.4% good

FCP

1.30 s

good

86.5% good

TTFB

711 ms

good

79.3% good

Lab vs field

Lab LCP 2.15 s · field p75 1.28 s · real users are 0.6× 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.26 s	72 ms	1.28 s	701 ms
2026-08-08	1.29 s	71 ms	1.30 s	717 ms
2026-08-01	1.30 s	71 ms	1.31 s	724 ms
2026-07-25	1.25 s	71 ms	1.27 s	710 ms
2026-07-18	1.23 s	71 ms	1.24 s	704 ms
2026-07-11	1.21 s	72 ms	1.21 s	686 ms
2026-07-04	1.18 s	69 ms	1.18 s	661 ms
2026-06-27	1.20 s	70 ms	1.19 s	661 ms
2026-06-20	1.21 s	76 ms	1.21 s	661 ms
2026-06-13	1.22 s	80 ms	1.22 s	674 ms
2026-06-06	1.21 s	83 ms	1.23 s	673 ms
2026-05-30	1.22 s	86 ms	1.23 s	671 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-15

1.26 s

72 ms

1.28 s

701 ms

2026-08-08

1.29 s

71 ms

1.30 s

717 ms

2026-08-01

1.30 s

71 ms

1.31 s

724 ms

2026-07-25

1.25 s

71 ms

1.27 s

710 ms

2026-07-18

1.23 s

71 ms

1.24 s

704 ms

2026-07-11

1.21 s

72 ms

1.21 s

686 ms

2026-07-04

1.18 s

69 ms

1.18 s

661 ms

2026-06-27

1.20 s

70 ms

1.19 s

661 ms

2026-06-20

1.21 s

76 ms

1.21 s

661 ms

2026-06-13

1.22 s

80 ms

1.22 s

674 ms

2026-06-06

1.21 s

83 ms

1.23 s

673 ms

2026-05-30

1.22 s

86 ms

1.23 s

671 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	443 kB	443 kB	↓ -244 B (-0.1%)	443 kB	443 kB
Requests	13	13	→ no change	13	13
Third-party Weight	170 kB	170 kB	↑ +8 B	170 kB	170 kB
Third-party CPU	49 ms	54 ms	↓ -5 ms (-9%)	49 ms	54 ms
Unused JS	73.9 kB	74.0 kB	↓ -51 B (-0.1%)	73.3 kB	74.0 kB
Unused CSS	0 B	0 B	→ no change	0 B	0 B

Metric

Current

Change

Best

Worst

Trend

Page Weight

443 kB

↓ -244 B (-0.1%)

443 kB

Requests

→ no change

Third-party Weight

170 kB

↑ +8 B

170 kB

Third-party CPU

49 ms

54 ms

↓ -5 ms (-9%)

49 ms

54 ms

Unused JS

73.9 kB

74.0 kB

↓ -51 B (-0.1%)

73.3 kB

74.0 kB

Unused CSS

0 B

→ no change

0 B

By resource type

script 195 kB · 3 req

font 194 kB · 2 req

document 22.0 kB · 1 req

stylesheet 13.6 kB · 1 req

other 9.9 kB · 3 req

image 9.1 kB · 3 req

third party 170 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 170 kB · 49 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	496 ms	600 ms	↓ -105 ms (-17.4%)	496 ms	600 ms
Long Tasks	2	3	↓ -1 (-33.3%)	2	3
DOM Elements	332	332	→ no change	332	332
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	7	7	→ no change	7	7
A11y Failures	2	2	→ no change	2	2
A11y Failing Nodes	4	4	→ no change	4	4

Main thread work

script evaluation 244 ms

other 117 ms

style layout 53 ms

script parse compile 51 ms

parse HTML 25 ms

paint composite render 7 ms

Axe violations axe-core 4.13.0, full rule set

7 violating nodes across 2 rules, 394 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.

moderate region — All page content should be contained by landmarks 4 nodes
serious color-contrast — Elements must meet minimum color contrast ratio thresholds 3 nodes

Accessibility failures 2 of 30 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. 3 nodes
label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 1:15 AM UTC	98	2.15 s	92 ms	443 kB	3/3	±29	2,370	26.8s
Aug 22, 2026, 1:09 AM UTC	88	3.62 s	144 ms	443 kB	3/3	±3	2,492	28.2s
Aug 20, 2026, 11:34 PM UTC	98	2.15 s	95 ms	443 kB	3/3	±0	2,316	22.3s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 1:15 AM UTC

2.15 s

92 ms

443 kB

3/3

±29

2,370

26.8s

Aug 22, 2026, 1:09 AM UTC

3.62 s

144 ms

443 kB

3/3

±3

2,492

28.2s

Aug 20, 2026, 11:34 PM UTC

2.15 s

95 ms

443 kB

3/3

±0

2,316

22.3s

Embed this score

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