speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

gohugo.io

https://gohugo.io/

98 97 100 100 CWV 7AXE

Data from Aug 20, 2026, 11:34 PM UTC — 19h old.

Site Generators · 1 measurement · since Aug 20, 2026 · last attempt 19h

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.

Hugo 0.165.0 Built with Hugo 0.165.0
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

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

LCP 1.27 s good
INP 76 ms good
CLS 0 good

Scores

98
Performance
no change
97
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.15 s 2.15 s 2.15 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 95 ms 95 ms 95 ms
FCP First Contentful Paint 957 ms 957 ms 957 ms
Speed Index 992 ms 992 ms 992 ms
TTFB Time to First Byte 614 ms 614 ms 614 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 84 ms
time to first byte 15 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.27 s good 93% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 76 ms good 95.5% good
CLS CWV 0 good 97.9% good
FCP 1.29 s good 87% good
TTFB 701 ms good 79.5% good

Lab vs field

Lab LCP 2.15 s · field p75 1.27 s · real users are 0.59× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 1.26 s 72 ms 0 1.28 s 701 ms
2026-08-08 1.29 s 71 ms 0 1.30 s 717 ms
2026-08-01 1.30 s 71 ms 0 1.31 s 724 ms
2026-07-25 1.25 s 71 ms 0 1.27 s 710 ms
2026-07-18 1.23 s 71 ms 0 1.24 s 704 ms
2026-07-11 1.21 s 72 ms 0 1.21 s 686 ms
2026-07-04 1.18 s 69 ms 0 1.18 s 661 ms
2026-06-27 1.20 s 70 ms 0 1.19 s 661 ms
2026-06-20 1.21 s 76 ms 0 1.21 s 661 ms
2026-06-13 1.22 s 80 ms 0 1.22 s 674 ms
2026-06-06 1.21 s 83 ms 0 1.23 s 673 ms
2026-05-30 1.22 s 86 ms 0 1.23 s 671 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 442.7 kB 442.7 kB 442.7 kB
Requests 13 13 13
Third-party Weight 170.3 kB 170.3 kB 170.3 kB
Third-party CPU 50 ms 50 ms 50 ms
Unused JS 73.3 kB 73.3 kB 73.3 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 194.5 kB · 3 req
font 193.4 kB · 2 req
document 22.1 kB · 1 req
stylesheet 13.7 kB · 1 req
other 9.9 kB · 3 req
image 9.0 kB · 3 req
third party 170.3 kB · 1 req

Third parties 1 entities

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

Google Tag Manager 170.3 kB · 50 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 502 ms 502 ms 502 ms
Long Tasks 2 2 2
DOM Elements 332 332 332
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 7 7 7
A11y Failures 2 2 2
A11y Failing Nodes 4 4 4

Main thread work

script evaluation 244 ms
other 118 ms
style layout 51 ms
script parse compile 50 ms
parse HTML 33 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 PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 11:34 PM UTC 98 2.15 s 0 95 ms 442.7 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 speedlify-score.js component code into your site!

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://gohugo.io/"></speedlify-score>