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 ·

foursquare.com

https://foursquare.com/

63 95 73 92 ✗CWV 3AXE

Data from Aug 20, 2026, 10:42 PM UTC — 20h old.

11ty Emeritus · 1 measurement · since Aug 20, 2026 · last attempt 20h

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.

WordPress 6.9.7 Built with WordPress 6.9.7
Self-hosted · nginx Hosted by Self-hosted

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 1.64 s good
INP 218 ms needs-improvement
CLS 0.190 needs-improvement

Scores

63
Performance
no change
95
Accessibility
no change
73
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.10 s — — 5.10 s 5.10 s
CLS Cumulative Layout Shift 0.190 — — 0.190 0.190
TBT Total Blocking Time 261 ms — — 261 ms 261 ms
FCP First Contentful Paint 1.51 s — — 1.51 s 1.51 s
Speed Index 5.19 s — — 5.19 s 5.19 s
TTFB Time to First Byte 615 ms — — 615 ms 615 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 343 ms
time to first byte 17 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 1.64 s good 88% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 218 ms needs-improvement 71.4% good
CLS CWV 0.190 needs-improvement 56.2% good
FCP 1.05 s good 90.4% good
TTFB 595 ms good 85.9% good

Lab vs field

Lab LCP 5.10 s · field p75 1.64 s · real users are 0.32× 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 1.64 s 219 ms 0.180 1.05 s 589 ms
2026-08-08 1.66 s 211 ms 0.180 1.03 s 572 ms
2026-08-01 1.67 s 210 ms 0.170 1.02 s 570 ms
2026-07-25 1.62 s 216 ms 0.170 1.00 s 560 ms
2026-07-18 1.57 s 219 ms 0.170 992 ms 554 ms
2026-07-11 1.57 s 226 ms 0.170 1.01 s 563 ms
2026-07-04 1.55 s 228 ms 0.170 1.01 s 557 ms
2026-06-27 1.57 s 227 ms 0.170 1.01 s 549 ms
2026-06-20 1.58 s 229 ms 0.170 1.00 s 547 ms
2026-06-13 1.57 s 218 ms 0.170 1.00 s 550 ms
2026-06-06 1.58 s 217 ms 0.170 1.01 s 551 ms
2026-05-30 1.60 s 218 ms 0.170 1.02 s 555 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 5.74 MB — — 5.74 MB 5.74 MB
Requests 102 — — 102 102
Third-party Weight 433.3 kB — — 433.3 kB 433.3 kB
Third-party CPU 145 ms — — 145 ms 145 ms
Unused JS 268.6 kB — — 268.6 kB 268.6 kB
Unused CSS 85.7 kB — — 85.7 kB 85.7 kB

By resource type

image 4.72 MB · 71 req
script 631.9 kB · 8 req
other 140.7 kB · 6 req
font 109.7 kB · 3 req
stylesheet 100.7 kB · 4 req
document 38.3 kB · 1 req
third party 433.3 kB · 14 req

Third parties 6 entities

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

Hubspot 212.8 kB · 65 ms CPU
Google Tag Manager 188.2 kB · 75 ms CPU
leandata.com 24.8 kB · 3 ms CPU
trakkr.ai 5.5 kB · 1 ms CPU
WordPress Site Stats 1.9 kB · 1 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 3.14 s — — 3.14 s 3.14 s
Long Tasks 9 — — 9 9
DOM Elements 1,639 — — 1,639 1,639
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 3 — — 3 3
A11y Failures 2 — — 2 2
A11y Failing Nodes 2 — — 2 2

Main thread work

script evaluation 1.12 s
other 1.07 s
style layout 437 ms
paint composite render 201 ms
script parse compile 194 ms
parse HTML 123 ms

Axe violations axe-core 4.13.0, full rule set

3 violating nodes across 3 rules, 1307 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.

  • minor empty-heading — Headings should not be empty 1 node
  • moderate heading-order — Heading levels should only increase by one 1 node
  • serious link-name — Links must have discernible text 1 node

Accessibility failures 2 of 33 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.

  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • link-name — Links do not have a discernible name 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 20, 2026, 10:42 PM UTC 63 5.10 s 0.190 261 ms 5.74 MB 3/3 ±12 2,749 50.7s

Embed this score

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