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 ·

gurumedia.com

https://gurumedia.com/

67 92 58 100 ✗CWV 79AXE

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

11ty Emeritus · 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.

Next.js Built with Next.js
Vercel Hosted by Vercel

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.08 s good
INP 294 ms needs-improvement
CLS 0 good

Scores

67
Performance
no change
92
Accessibility
no change
58
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.69 s — — 5.69 s 5.69 s
CLS Cumulative Layout Shift 0.001 — — 0.001 0.001
TBT Total Blocking Time 486 ms — — 486 ms 486 ms
FCP First Contentful Paint 944 ms — — 944 ms 944 ms
Speed Index 1.70 s — — 1.70 s 1.70 s
TTFB Time to First Byte 631 ms — — 631 ms 631 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 452 ms
time to first byte 24 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.08 s good 83.1% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 294 ms needs-improvement 69.7% good
CLS CWV 0 good 95.2% good
FCP 1.45 s good 85% good
TTFB 780 ms good 76.1% good

Lab vs field

Lab LCP 5.69 s · field p75 2.08 s · real users are 0.37× 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.08 s 303 ms 0 1.45 s 778 ms
2026-08-08 2.10 s 246 ms 0 1.39 s 708 ms
2026-08-01 2.10 s 258 ms 0 1.40 s 687 ms
2026-07-25 2.20 s 240 ms 0 1.53 s 708 ms
2026-07-18 2.12 s 219 ms 0 1.55 s 694 ms
2026-07-11 2.07 s 219 ms 0 1.65 s 739 ms
2026-07-04 2.15 s 218 ms 0 1.79 s 809 ms
2026-06-27 2.19 s 230 ms 0 1.90 s 826 ms
2026-06-20 2.41 s 246 ms 0 2.02 s 874 ms
2026-06-13 2.43 s 261 ms 0 2.08 s 889 ms
2026-06-06 2.33 s 261 ms 0 2.00 s 868 ms
2026-05-30 2.20 s 261 ms 0 1.90 s 720 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 796.9 kB — — 796.9 kB 796.9 kB
Requests 35 — — 35 35
Third-party Weight 405.0 kB — — 405.0 kB 405.0 kB
Third-party CPU 157 ms — — 157 ms 157 ms
Unused JS 193.1 kB — — 193.1 kB 193.1 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 574.5 kB · 15 req
image 115.9 kB · 9 req
font 77.0 kB · 5 req
document 14.6 kB · 1 req
stylesheet 12.3 kB · 1 req
other 2.6 kB · 4 req
third party 405.0 kB · 9 req

Third parties 3 entities

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

Google Tag Manager 189.8 kB · 62 ms CPU
Facebook 173.9 kB · 80 ms CPU
LinkedIn Ads 41.4 kB · 15 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.49 s — — 3.49 s 3.49 s
Long Tasks 6 — — 6 6
DOM Elements 640 — — 640 640
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 79 — — 79 79
A11y Failures 2 — — 2 2
A11y Failing Nodes 6 — — 6 6

Main thread work

other 1.79 s
script evaluation 1.01 s
style layout 322 ms
script parse compile 191 ms
paint composite render 129 ms
parse HTML 29 ms
garbage collection 18 ms

Axe violations axe-core 4.13.0, full rule set

79 violating nodes across 3 rules, 605 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 73 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 5 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node

Accessibility failures 2 of 25 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. 5 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 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:29 PM UTC 67 5.69 s 0.001 486 ms 796.9 kB 3/3 ±12 2,328 30.3s

Embed this score

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