speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time. Follow us on Mastodon or Bluesky.

Charts Compare Measurement runs Embed a score Open to Work

tripgazer.com

https://www.tripgazer.com/

39PERF 92A11Y 77BEST 100SEO ✗AXE –CWV

Ranks Overall #1,731 Built Awesome #1,105

Data from Oct 6, 2026, 12:00 AM UTC old Measured once a week · 7 runs since Aug 21, 2026

Elsewhere: PageSpeed Insights · Calibre · Treo · CrUX Vis · Tame the Bots · Scoring Calculator · Wayback Machine

Lab data is measured using Lighthouse, Mobile mode unless otherwise specified. Field data is reported from Chrome UX Report (using p75 measurements).

Stack

Uses Lit 3.3.3Lit 3.3.3Font AwesomeFont Awesome
Netlify Hosted by Netlify

Lighthouse Scores LAB Simulated

39
Performance
↓ -12 (-23.5%)
92
Accessibility
↑ +1 (+1.1%)
77
Best Practices
no change
100
SEO
no change

Metrics LAB

No field data: the Chrome UX Report is not being collected for this project, so every figure below is from the Lighthouse run.

Metric Lab Simulated
Value Change / range Trend
LCP CWV (estimate) Largest Contentful Paint 18.99 s poor ↑ +8155 ms (+75.3%) significant 10.84 s – 25.09 s
INP CWV Interaction to Next Paint — field only, no lab run can measure it n/a —
CLS CWV (estimate) Cumulative Layout Shift 0.119 needs work ↑ +0.119 0 – 0.119
TBT Total Blocking Time 791 ms poor ↑ +152 ms (+23.8%) 639 ms – 1.13 s
FCP First Contentful Paint 2.77 s needs work ↓ -169 ms (-5.7%) 2.15 s – 3.48 s
Speed Index 9.39 s poor ↑ +4327 ms (+85.5%) significant 5.06 s – 9.39 s
TTFB Time to First Byte 622 ms good ↓ -7 ms (-1.1%) 605 ms – 635 ms

LCP Subparts LAB Unthrottled

The subparts attribute LCP to your server, resource discovery, download, or rendering. Note that the Lab LCP shown above is a simulated throttled estimate.

resource load delay 489 ms
element render delay 81 ms
resource load duration 43 ms
time to first byte 24 ms

Page weight

Metric Value Change / range Trend
Page Weight 12.30 MB ↑ +8012.2 kB (+200.4%) significant 3.75 MB – 12.30 MB
Requests 300 ↑ +106 (+54.6%) significant 187 – 300
Third-party Weight 1.81 MB ↑ +310.5 kB (+21.3%) significant 1.45 MB – 1.81 MB
Third-party CPU 545 ms ↑ +81 ms (+17.4%) significant 465 ms – 646 ms
Unused JS 660 kB ↑ +77.2 kB (+13.6%) 573 kB – 660 kB
Unused CSS 44.8 kB ↑ +3 B 44.8 kB – 44.8 kB

By resource type

Type Transfer Share Size Requests
image 80.1% 9.85 MB 49
script 15.6% 1.92 MB 69
document 1.9% 229 kB 17
font 1.8% 224 kB 8
other 0.4% 50.6 kB 58
stylesheet 0.2% 25.9 kB 12
Total 12.30 MB 300

Third parties 20 entities

Entity Transfer Size Main thread Simulated
Google Tag Manager script 491 kB 180 ms
grow.me script 382 kB 6 ms
Google/Doubleclick Ads script 309 kB 140 ms
Google Fonts font 208 kB 0 ms
iubenda script 122 kB 41 ms
All 20 1.81 MB 545 ms

Page health

Metric Value Change / range Trend
Main Thread Work 6.11 s ↑ +1640 ms (+36.7%) significant 4.47 s – 6.25 s
Long Tasks 17 ↑ +2 (+13.3%) significant 15 – 20
DOM Elements 1,415 ↑ +70 (+5.2%) significant 1,292 – 1,415
Axe Violations Violating nodes from a full Axe CLI run (more than Lighthouse reports) 85 ↑ +2 (+2.4%) 78 – 101
A11y Failures 4 → no change 3 – 5
A11y Failing Nodes 85 ↑ +3 (+3.7%) 78 – 85

Main thread work

Task Time Share Duration Simulated
script evaluation 53% 3.23 s
other 20% 1.23 s
style layout 14% 850 ms
script parse compile 5% 329 ms
paint composite render 5% 314 ms
garbage collection 2% 100 ms
parse HTML 1% 60 ms
Total 6.11 s

Axe violations axe-core 4.13.0, full rule set

85 violating nodes across 5 rules, 2681 passing. This is a standalone Axe CLI run and is stricter than the subset Lighthouse already includes.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 81 nodes
    Offending elements (5 of 81)
    1. li:nth-child(1) > article > .btn-cont > .btn
      <a class="btn" href="/things-to-do-near-yankee-candle-deerfield-ma/">READ <span class="line-1"></span> <span class="line-2"></span> <span class="line-3"></span> <span class="line-4"></span></a>
    2. .btn[href="/disney-cruise-packing-list/"]
      <a class="btn" href="/disney-cruise-packing-list/">READ <span class="line-1"></span> <span class="line-2"></span> <span class="line-3"></span> <span class="line-4"></span></a>
    3. li:nth-child(5) > article > .btn-cont > .btn
      <a class="btn" href="/alaska-cruise-packing-checklist/">READ <span class="line-1"></span> <span class="line-2"></span> <span class="line-3"></span> <span class="line-4"></span></a>
    4. .btn[href$="packmytrip-vs-packpoint/"]
      <a class="btn" href="/packmytrip-vs-packpoint/">READ <span class="line-1"></span> <span class="line-2"></span> <span class="line-3"></span> <span class="line-4"></span></a>
    5. li:nth-child(9) > article > .btn-cont > .btn[href$="cruise-packing-list/"]
      <a class="btn" href="/cruise-packing-list/">READ <span class="line-1"></span> <span class="line-2"></span> <span class="line-3"></span> <span class="line-4"></span></a>
  • moderate heading-order — Heading levels should only increase by one 1 node
    Offending element
    1. li:nth-child(1) > article > h3
      <h3><a href="/things-to-do-near-yankee-candle-deerfield-ma/">7 Things To Do Near Yankee Candle in Deerfield, MA</a></h3>
  • moderate landmark-no-duplicate-banner — Document should not have more than one banner landmark 1 node
    Offending element
    1. .site-header
      <header class="site-header">
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node
    Offending element
    1. .site-header
      <header class="site-header">
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node
    Offending element
    1. .article-post
      <ul class="article-post columns-2" style="height: auto !important;">

Accessibility failures 4 of 30 audits

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 81 nodes
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 2 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

Best Practices failures 2 of 20 audits

  • third-party-cookies — Uses third-party cookies 22 items
  • inspector-issues — Issues were logged in the `Issues` panel in Chrome Devtools 1 item

Hygiene

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-07-11 → 2026-09-26 No data — 12 weeks under the CrUX reporting threshold
2026-07-04 2.64 s — 0 2.13 s 1.44 s
2026-04-11 → 2026-06-27 No data — 12 weeks under the CrUX reporting threshold

Runs

Every stored run for this URL, newest first.

When Scores PerfLCPCLSTBTWeight RunsSpreadBenchTook Archive
Oct 6, 2026, 12:00 AM UTC 39 18.99 s 0.119 791 ms 12.30 MB 3/3 ±8 2,993 +20% 61.5s Wayback
Sep 28, 2026, 6:38 PM UTC 51 10.84 s 0 639 ms 4.09 MB 3/3 ±8 3,363 +35% 57.7s Wayback
Sep 21, 2026, 3:03 PM UTC 40 25.09 s 0 1.05 s 6.37 MB 2/3 ±3 2,387 -4% 68.9s Wayback
Sep 14, 2026, 12:03 PM UTC 42 12.03 s 0 1.13 s 3.75 MB 3/3 ±11 2,495 0% 63.2s Wayback
Sep 7, 2026, 9:07 AM UTC 45 14.29 s 0 1.12 s 4.06 MB 3/3 ±10 2,428 -2% 66.4s Wayback
Aug 31, 2026, 4:03 AM UTC 41 14.20 s 0 1.10 s 4.34 MB 2/3 ±1 2,289 -8% 68.5s Wayback
Aug 21, 2026, 2:38 PM UTC 40 14.69 s 0 959 ms 4.12 MB 3/3 ±8 2,485 0% 65s Wayback

Embed this score

Use this web component to show tripgazer.com's scores on any website, updated whenever this instance re-measures. Don’t forget to bundle the speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.tripgazer.com/"></speedlify2-score>