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 ·

belocalpub.com

https://www.belocalpub.com/

45 81 73 100 ✓CWV 21AXE

Data from Aug 21, 2026, 9:41 AM UTC — 9h old.

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

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-23 → 2026-08-19). This is what Google measures you on.

LCP 1.79 s good
INP 76 ms good
CLS 0.020 good

Scores

45
Performance
no change
81
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 8.69 s — — 8.69 s 8.69 s
CLS Cumulative Layout Shift 0.022 — — 0.022 0.022
TBT Total Blocking Time 727 ms — — 727 ms 727 ms
FCP First Contentful Paint 2.26 s — — 2.26 s 2.26 s
Speed Index 27.88 s — — 27.88 s 27.88 s
TTFB Time to First Byte 9.03 s — — 9.03 s 9.03 s

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.

time to first byte 9.03 s
resource load delay 8.96 s
resource load duration 218 ms
element render delay 105 ms

Field data Chrome UX Report, origin-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.79 s good 87% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 76 ms good 95.6% good
CLS CWV 0.020 good 95.8% good
FCP 1.15 s good 88.6% good
TTFB 735 ms good 80% good

Lab vs field

Lab LCP 8.69 s · field p75 1.79 s · real users are 0.21× 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 — — — — —
2026-08-08 — — — — —
2026-08-01 — — — — —
2026-07-25 — — — — —
2026-07-18 1.85 s — 0 1.12 s —
2026-07-11 1.84 s — 0 1.25 s 678 ms
2026-07-04 — — — — —
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 2.23 MB — — 2.23 MB 2.23 MB
Requests 61 — — 61 61
Third-party Weight 1.47 MB — — 1.47 MB 1.47 MB
Third-party CPU 448 ms — — 448 ms 448 ms
Unused JS 411.1 kB — — 411.1 kB 411.1 kB
Unused CSS 48.6 kB — — 48.6 kB 48.6 kB

By resource type

script 1.07 MB · 22 req
image 873.0 kB · 7 req
font 131.0 kB · 4 req
other 106.8 kB · 17 req
stylesheet 41.7 kB · 7 req
document 7.5 kB · 2 req
third party 1.47 MB · 49 req

Third parties 13 entities

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

Google Tag Manager 490.7 kB · 195 ms CPU
Amazon Web Services 445.9 kB · 0 ms CPU
Facebook 228.0 kB · 111 ms CPU
LiveHelpNow 128.9 kB · 43 ms CPU
Netlify 55.3 kB · 28 ms CPU

Page health

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

Main thread work

script evaluation 1.68 s
other 520 ms
script parse compile 365 ms
style layout 212 ms
parse HTML 88 ms
garbage collection 53 ms
paint composite render 45 ms

Axe violations axe-core 4.13.0, full rule set

21 violating nodes across 7 rules, 490 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 link-name — Links must have discernible text 8 nodes
  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 6 nodes
  • critical button-name — Buttons must have discernible text 3 nodes
  • critical aria-allowed-attr — Elements must only use supported ARIA attributes 1 node
  • minor aria-allowed-role — ARIA role should be appropriate for the element 1 node
  • serious frame-title — Frames must have an accessible name 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

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

  • link-name — Links do not have a discernible name 8 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 6 nodes
  • button-name — Buttons do not have an accessible name 4 nodes
  • aria-allowed-attr — `[aria-*]` attributes do not match their roles 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 2 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, 9:41 AM UTC 45 8.69 s 0.022 727 ms 2.23 MB 2/3 ±1 2,457 160.9s

Embed this score

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