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 ·

hamandhoney.com

https://www.hamandhoney.com/

72 94 92 100 CWV 21AXE

Data from Aug 21, 2026, 10:38 AM UTC — 8h old.

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

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

Scores

72
Performance
no change
94
Accessibility
no change
92
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 30.76 s 30.76 s 30.76 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 189 ms 189 ms 189 ms
FCP First Contentful Paint 905 ms 905 ms 905 ms
Speed Index 905 ms 905 ms 905 ms
TTFB Time to First Byte 605 ms 605 ms 605 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 155 ms
resource load duration 48 ms
resource load delay 31 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.44 MB 7.44 MB 7.44 MB
Requests 133 133 133
Third-party Weight 59.3 kB 59.3 kB 59.3 kB
Third-party CPU 34 ms 34 ms 34 ms
Unused JS 0 B 0 B 0 B
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

image 7.28 MB · 64 req
script 60.7 kB · 3 req
font 54.4 kB · 3 req
other 39.5 kB · 59 req
stylesheet 6.3 kB · 1 req
document 4.5 kB · 1 req
third party 80.3 kB · 103 req

Third parties 3 entities

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

Netlify 55.0 kB · 32 ms CPU
JSDelivr CDN 4.1 kB · 1 ms CPU
Google Analytics 103 B · 0 ms CPU

Page health

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

Main thread work

other 740 ms
script evaluation 115 ms
style layout 109 ms
script parse compile 36 ms
paint composite render 24 ms
parse HTML 19 ms

Axe violations axe-core 4.13.0, full rule set

21 violating nodes across 1 rule, 672 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 21 nodes

Accessibility failures 1 of 18 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. 13 nodes

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2 50 console errors

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, 10:38 AM UTC 72 30.76 s 0 189 ms 7.44 MB 3/3 ±9 3,020 26.3s

Embed this score

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