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 ·

tripgazer.com

https://www.tripgazer.com/

40 86 73 100 –CWV 101AXE

Data from Aug 21, 2026, 2:38 PM UTC — 4h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 4h

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.

Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP — no data
INP — no data
CLS — no data

Scores

40
Performance
no change
86
Accessibility
no change
73
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 14.69 s — — 14.69 s 14.69 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 959 ms — — 959 ms 959 ms
FCP First Contentful Paint 3.48 s — — 3.48 s 3.48 s
Speed Index 7.11 s — — 7.11 s 7.11 s
TTFB Time to First Byte 606 ms — — 606 ms 606 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.

resource load delay 741 ms
element render delay 55 ms
time to first byte 8 ms
resource load duration 8 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 — — — — —
2026-07-11 — — — — —
2026-07-04 2.64 s — 0 2.13 s 1.44 s
2026-06-27 — — — — —
2026-06-20 — — — — —
2026-06-13 — — — — —
2026-06-06 — — — — —
2026-05-30 — — — — —

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.12 MB — — 4.12 MB 4.12 MB
Requests 227 — — 227 227
Third-party Weight 1.65 MB — — 1.65 MB 1.65 MB
Third-party CPU 586 ms — — 586 ms 586 ms
Unused JS 594.4 kB — — 594.4 kB 594.4 kB
Unused CSS 44.8 kB — — 44.8 kB 44.8 kB

By resource type

image 2.07 MB · 16 req
script 1.57 MB · 52 req
font 231.0 kB · 7 req
document 190.7 kB · 13 req
other 28.7 kB · 44 req
stylesheet 26.9 kB · 12 req
third party 3.88 MB · 140 req

Third parties 20 entities

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

Google Tag Manager 473.7 kB · 155 ms CPU
Google/Doubleclick Ads 255.6 kB · 68 ms CPU
Google Fonts 217.0 kB · 0 ms CPU
grow.me 150.1 kB · 3 ms CPU
tp-em.com 123.5 kB · 184 ms CPU

Page health

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

Main thread work

script evaluation 3.72 s
other 1.16 s
style layout 564 ms
script parse compile 409 ms
paint composite render 210 ms
garbage collection 117 ms
parse HTML 61 ms

Axe violations axe-core 4.13.0, full rule set

101 violating nodes across 8 rules, 2455 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 88 nodes
  • serious link-name — Links must have discernible text 6 nodes
  • serious frame-title — Frames must have an accessible name 2 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node
  • moderate meta-viewport — Zooming and scaling must not be disabled 1 node

Accessibility failures 5 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 76 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 1 node
  • meta-viewport — `[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5. 1 node
  • 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 1 console error

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 21, 2026, 2:38 PM UTC 40 14.69 s 0 959 ms 4.12 MB 3/3 ±8 2,485 65s

Embed this score

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