speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

wisc.edu

https://www.wisc.edu/

67 100 77 100 2AXE ✓CWV

Data from Aug 21, 2026, 2:42 PM UTC 2d old

Built Awesome #764 · 1 measurement · since Aug 21, 2026

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.

Amazon S3 Hosted by Amazon S3

Core Web Vitals field data, url-level

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

LCP 1.33 s good
INP 117 ms good
CLS 0.050 good

Scores

67
Performance
no change
100
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 10.13 s — — 10.13 s 10.13 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 240 ms — — 240 ms 240 ms
FCP First Contentful Paint 2.41 s — — 2.41 s 2.41 s
Speed Index 2.42 s — — 2.42 s 2.42 s
TTFB Time to First Byte 607 ms — — 607 ms 607 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 10.13 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 148 ms
element render delay 94 ms
resource load duration 13 ms
resource load delay 10 ms

Field data Chrome UX Report, url-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.33 s good 91.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 117 ms good 92.3% good
CLS CWV 0.050 good 77% good
FCP 1.25 s good 86.9% good
TTFB 818 ms needs-improvement 74.7% good

Lab vs field

Lab LCP 10.13 s · field p75 1.33 s · real users are 0.13× 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.33 s 117 ms 0.200 1.24 s 816 ms
2026-08-08 1.35 s 118 ms 0.210 1.26 s 851 ms
2026-08-01 1.39 s 119 ms 0.210 1.30 s 901 ms
2026-07-25 1.39 s 120 ms 0.210 1.29 s 897 ms
2026-07-18 1.41 s 118 ms 0.200 1.32 s 932 ms
2026-07-11 1.42 s 119 ms 0 1.33 s 941 ms
2026-07-04 1.43 s 119 ms 0 1.35 s 948 ms
2026-06-27 1.47 s 118 ms 0 1.38 s 989 ms
2026-06-20 1.47 s 120 ms 0 1.38 s 970 ms
2026-06-13 1.44 s 117 ms 0 1.36 s 935 ms
2026-06-06 1.39 s 114 ms 0 1.30 s 877 ms
2026-05-30 1.32 s 113 ms 0 1.24 s 814 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 4.39 MB — — 4.39 MB 4.39 MB
Requests 37 — — 37 37
Third-party Weight 720 kB — — 720 kB 720 kB
Third-party CPU 173 ms — — 173 ms 173 ms
Unused JS 271 kB — — 271 kB 271 kB
Unused CSS 17.2 kB — — 17.2 kB 17.2 kB

By resource type

image 3.61 MB · 16 req
script 602 kB · 8 req
font 124 kB · 5 req
stylesheet 25.5 kB · 4 req
document 23.9 kB · 1 req
other 602 B · 2 req
third party 720 kB · 14 req

Third parties 4 entities

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

Google Tag Manager 585 kB · 171 ms CPU
wisc.cloud 129 kB · 1 ms CPU
Oracle 7.0 kB · 1 ms CPU
Google Analytics 48 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.55 s — — 1.55 s 1.55 s
Long Tasks 7 — — 7 7
DOM Elements 565 — — 565 565
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 2 — — 2 2
A11y Failures 0 — — 0 0
A11y Failing Nodes 0 — — 0 0

Main thread work

script evaluation 606 ms
other 490 ms
style layout 233 ms
script parse compile 142 ms
paint composite render 35 ms
parse HTML 27 ms
garbage collection 22 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 852 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 1 node
  • moderate region — All page content should be contained by landmarks 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

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:42 PM UTC 67 10.13 s 0 240 ms 4.39 MB 3/3 ±6 2,452 28.2s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show wisc.edu's scores, updated whenever this instance re-measures — more about the component. 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.wisc.edu/"></speedlify2-score>