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 ·

gulpjs.com

https://gulpjs.com/

80 96 100 92 ✓CWV 1AXE

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

Test Runners · 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.

Docusaurus 3.2.1 Built with Docusaurus 3.2.1
GitHub Pages Hosted by GitHub Pages

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 2.26 s good
INP — no data
CLS 0.080 good

Scores

80
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.59 s — — 3.59 s 3.59 s
CLS Cumulative Layout Shift 0.107 — — 0.107 0.107
TBT Total Blocking Time 218 ms — — 218 ms 218 ms
FCP First Contentful Paint 2.44 s — — 2.44 s 2.44 s
Speed Index 2.44 s — — 2.44 s 2.44 s
TTFB Time to First Byte 610 ms — — 610 ms 610 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 80 ms
time to first byte 25 ms
resource load duration 18 ms
resource load delay 10 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 2.26 s good 83.5% good
CLS CWV 0.080 good 86.8% good
FCP 2.04 s needs-improvement 65.9% good

Lab vs field

Lab LCP 3.59 s · field p75 2.26 s · real users are 0.63× 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 2.27 s — 0.080 2.09 s —
2026-08-08 — — 0.080 1.93 s —
2026-08-01 — — — 1.78 s —
2026-07-25 — — 0.080 2.09 s —
2026-07-18 2.15 s — 0.080 2.03 s 1.25 s
2026-07-11 2.22 s — 0.080 2.14 s 1.17 s
2026-07-04 2.22 s — 0.080 2.14 s 1.17 s
2026-06-27 2.26 s — 0.080 2.17 s 1.20 s
2026-06-20 2.30 s — 0.080 2.20 s 1.31 s
2026-06-13 2.30 s — 0.080 1.99 s 1.40 s
2026-06-06 2.11 s — 0.080 1.70 s 1.23 s
2026-05-30 1.70 s — 0.090 1.66 s —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 767.1 kB — — 767.1 kB 767.1 kB
Requests 43 — — 43 43
Third-party Weight 348.2 kB — — 348.2 kB 348.2 kB
Third-party CPU 102 ms — — 102 ms 102 ms
Unused JS 181.9 kB — — 181.9 kB 181.9 kB
Unused CSS 13.8 kB — — 13.8 kB 13.8 kB

By resource type

script 453.1 kB · 7 req
image 218.5 kB · 18 req
other 35.3 kB · 12 req
font 32.2 kB · 3 req
stylesheet 22.3 kB · 2 req
document 5.6 kB · 1 req
third party 348.2 kB · 8 req

Third parties 3 entities

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

Google Tag Manager 293.1 kB · 81 ms CPU
Google Fonts 34.1 kB · 0 ms CPU
Google Analytics 20.9 kB · 21 ms CPU

Page health

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

Main thread work

script evaluation 732 ms
other 247 ms
script parse compile 175 ms
style layout 109 ms
paint composite render 26 ms
parse HTML 18 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 431 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 1 node

Accessibility failures 1 of 26 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. 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:30 PM UTC 80 3.59 s 0.107 218 ms 767.1 kB 3/3 ±1 2,453 29.2s

Embed this score

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