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 ·

docs.gitlab.com/user/project/pages

https://docs.gitlab.com/user/project/pages

46 100 54 100 ✗CWV 3AXE

Data from Aug 20, 2026, 8:30 PM UTC — 22h old.

Web Hosts · 1 measurement · since Aug 20, 2026 · last attempt 22h

This URL redirects to https://docs.gitlab.com/user/project/pages/.

A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.

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.

Cloudflare Hosted by Cloudflare

Core Web Vitals field data, origin-level

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

LCP 1.33 s good
INP 560 ms poor
CLS 0.110 needs-improvement

Scores

46
Performance
no change
100
Accessibility
no change
54
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.22 s — — 6.22 s 6.22 s
CLS Cumulative Layout Shift 0.113 — — 0.113 0.113
TBT Total Blocking Time 1.38 s — — 1.38 s 1.38 s
FCP First Contentful Paint 1.87 s — — 1.87 s 1.87 s
Speed Index 3.99 s — — 3.99 s 3.99 s
TTFB Time to First Byte 674 ms — — 674 ms 674 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 202 ms
time to first byte 62 ms

Field data Chrome UX Report, origin-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.33 s good 91.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 560 ms poor 54.3% good
CLS CWV 0.110 needs-improvement 72.5% good
FCP 1.26 s good 86% good
TTFB 594 ms good 83.2% good

Lab vs field

Lab LCP 6.22 s · field p75 1.33 s · real users are 0.21× 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.33 s 561 ms 0.090 1.26 s 590 ms
2026-08-08 1.31 s 564 ms 0.010 1.24 s 579 ms
2026-08-01 1.26 s 566 ms 0 1.20 s 569 ms
2026-07-25 1.26 s 556 ms 0 1.20 s 573 ms
2026-07-18 1.28 s 514 ms 0 1.22 s 584 ms
2026-07-11 1.30 s 338 ms 0 1.25 s 597 ms
2026-07-04 1.35 s 342 ms 0 1.29 s 614 ms
2026-06-27 1.35 s 475 ms 0 1.29 s 610 ms
2026-06-20 1.31 s 554 ms 0 1.25 s 591 ms
2026-06-13 1.26 s 560 ms 0 1.21 s 569 ms
2026-06-06 1.20 s 558 ms 0 1.15 s 557 ms
2026-05-30 1.20 s 556 ms 0 1.16 s 586 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 2.53 MB — — 2.53 MB 2.53 MB
Requests 170 — — 170 170
Third-party Weight 1.03 MB — — 1.03 MB 1.03 MB
Third-party CPU 405 ms — — 405 ms 405 ms
Unused JS 502.9 kB — — 502.9 kB 502.9 kB
Unused CSS 63.5 kB — — 63.5 kB 63.5 kB

By resource type

script 1.36 MB · 78 req
other 586.4 kB · 62 req
font 412.9 kB · 3 req
stylesheet 104.5 kB · 6 req
document 42.0 kB · 3 req
image 23.3 kB · 17 req
third party 1.12 MB · 59 req

Third parties 12 entities

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

Google Tag Manager 375.6 kB · 220 ms CPU
Google CDN 344.0 kB · 83 ms CPU
Optanon 226.2 kB · 60 ms CPU
LinkedIn Ads 43.0 kB · 14 ms CPU
Bizible 26.2 kB · 16 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 5.40 s — — 5.40 s 5.40 s
Long Tasks 20 — — 20 20
DOM Elements 1,498 — — 1,498 1,498
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 3 — — 3 3
A11y Failures 1 — — 1 1
A11y Failing Nodes 4 — — 4 4

Main thread work

script evaluation 3.37 s
other 996 ms
style layout 349 ms
script parse compile 305 ms
garbage collection 156 ms
paint composite render 137 ms
parse HTML 84 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 1 rule, 1442 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 3 nodes

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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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 35 console errors

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, 8:30 PM UTC 46 6.22 s 0.113 1.38 s 2.53 MB 3/3 ±17 2,490 42.8s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show docs.gitlab.com/user/project/pages'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://docs.gitlab.com/user/project/pages"></speedlify-score>