docs.gitlab.com/user/project/pages
https://docs.gitlab.com/user/project/pages
Data from Aug 22, 2026, 10:20 PM UTC 23h old
Web Hosts #16 · 3 measurements · since Aug 20, 2026
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.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-24 → 2026-08-20). This is what Google measures you on.
Scores
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 | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 6.21 s | 7.37 s | ↓ -1160 ms (-15.7%) | 6.21 s | 7.37 s | |
| CLS Cumulative Layout Shift | 0.113 | 0.113 | → no change | 0.113 | 0.113 | |
| TBT Total Blocking Time | 1.35 s | 1.17 s | ↑ +186 ms (+15.9%) | 1.17 s | 1.38 s | |
| FCP First Contentful Paint | 1.86 s | 2.72 s | ↓ -859 ms (-31.6%) | 1.86 s | 2.72 s | |
| Speed Index | 4.18 s | 3.46 s | ↑ +720 ms (+20.8%) | 3.46 s | 4.18 s | |
| TTFB Time to First Byte | 657 ms | 616 ms | ↑ +41 ms (+6.7%) | 616 ms | 674 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 6.21 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.
Field data Chrome UX Report, origin-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 | 1.34 s | good | 92.1% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 560 ms | poor | 56.6% good |
| CLS CWV | 0.120 | needs-improvement | 69.5% good |
| FCP | 1.27 s | good | 85.6% good |
| TTFB | 596 ms | good | 83.5% good |
Lab vs field
Lab LCP 6.21 s · field p75 1.34 s · real users are 0.22× 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 | 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.44 MB | 2.44 MB | ↑ +497 B | 2.44 MB | 2.53 MB | |
| Requests | 161 | 161 | → no change | 161 | 170 | |
| Third-party Weight | 1.01 MB | 1.01 MB | ↑ +417 B | 1.01 MB | 1.03 MB | |
| Third-party CPU | 358 ms | 339 ms | ↑ +19 ms (+5.7%) | 339 ms | 405 ms | |
| Unused JS | 493 kB | 571 kB | ↓ -76.7 kB (-13.7%) | 493 kB | 571 kB | |
| Unused CSS | 63.5 kB | 63.5 kB | → no change | 63.5 kB | 63.5 kB |
By resource type
Third parties 11 entities
1.01 MB transferred, 358 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 4.33 s | 4.18 s | ↑ +153 ms (+3.7%) | 4.18 s | 5.40 s | |
| Long Tasks | 17 | 16 | ↑ +1 (+6.3%) | 16 | 20 | |
| DOM Elements | 1,492 | 1,492 | → no change | 1,492 | 1,498 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 3 | 3 | → no change | 3 | 3 | |
| A11y Failures | 1 | 1 | → no change | 1 | 1 | |
| A11y Failing Nodes | 4 | 4 | → no change | 4 | 4 |
Main thread work
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.
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 22, 2026, 10:20 PM UTC | 46 | 6.21 s | 0.113 | 1.35 s | 2.44 MB | 3/3 | ±15 | 2,435 | 44.7s |
| Aug 21, 2026, 9:23 PM UTC | 44 | 7.37 s | 0.113 | 1.17 s | 2.44 MB | 3/3 | ±2 | 2,276 | 38.7s |
| 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 speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://docs.gitlab.com/user/project/pages"></speedlify2-score>