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 ·

azure.microsoft.com/en-us/products/app-service/static

https://azure.microsoft.com/en-us/products/app-service/static

28 97 54 85 ✗CWV 5AXE

Data from Aug 21, 2026, 4:38 PM UTC — 2h old.

Web Hosts · 2 measurements · since Aug 20, 2026 · last attempt 2h

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 3.63 s needs-improvement
INP — no data
CLS 0.110 needs-improvement

Scores

28
Performance
↑ +2 (+7.7%)
97
Accessibility
no change
54
Best Practices
no change
85
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 38.20 s 39.67 s ↓ -1466 ms (-3.7%) 38.20 s 39.67 s
CLS Cumulative Layout Shift 0.103 0.103 → no change 0.103 0.103
TBT Total Blocking Time 1.29 s 1.60 s ↓ -311 ms (-19.5%) 1.29 s 1.60 s
FCP First Contentful Paint 20.73 s 18.93 s ↑ +1805 ms (+9.5%) 18.93 s 20.73 s
Speed Index 20.73 s 18.93 s ↑ +1805 ms (+9.5%) 18.93 s 20.73 s
TTFB Time to First Byte 619 ms 631 ms ↓ -12 ms (-1.9%) 619 ms 631 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.

resource load delay 1.29 s
element render delay 925 ms
time to first byte 253 ms
resource load duration 58 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 3.63 s needs-improvement 58.2% good
CLS CWV 0.110 needs-improvement 44.7% good
FCP 2.35 s needs-improvement 61.6% good
TTFB 955 ms needs-improvement 63.3% good

Lab vs field

Lab LCP 38.20 s · field p75 3.63 s · real users are 0.09× 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 3.80 s — 0.110 2.62 s 955 ms
2026-08-08 3.37 s — 0.110 2.41 s 911 ms
2026-08-01 3.27 s — 0.110 2.27 s 876 ms
2026-07-25 3.10 s — 0.110 2.23 s 867 ms
2026-07-18 3.10 s — 0.110 2.32 s 811 ms
2026-07-11 2.90 s — 0.110 2.06 s 706 ms
2026-07-04 2.89 s — 0.110 2.04 s 719 ms
2026-06-27 3.15 s — 0.110 2.23 s 706 ms
2026-06-20 2.99 s — 0.110 1.97 s 684 ms
2026-06-13 3.41 s — 0.110 2.33 s 768 ms
2026-06-06 3.63 s 135 ms 0.110 2.43 s 834 ms
2026-05-30 3.61 s — 0.110 2.43 s 891 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 7.17 MB 7.18 MB ↓ -9.6 kB (-0.1%) 7.17 MB 7.18 MB
Requests 163 175 ↓ -12 (-6.9%) 163 175
Third-party Weight 799.9 kB 808.4 kB ↓ -8.3 kB (-1.1%) 799.9 kB 808.4 kB
Third-party CPU 310 ms 361 ms ↓ -51 ms (-14.1%) 310 ms 361 ms
Unused JS 1.47 MB 1.46 MB ↑ +4.3 kB (+0.3%) 1.46 MB 1.47 MB
Unused CSS 174.7 kB 174.7 kB → no change 174.7 kB 174.7 kB

By resource type

script 3.95 MB · 84 req
image 2.01 MB · 30 req
font 946.7 kB · 5 req
stylesheet 211.5 kB · 21 req
document 42.7 kB · 2 req
other 12.2 kB · 21 req
third party 7.17 MB · 163 req

Third parties 19 entities

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

Facebook 221.4 kB · 109 ms CPU
Adobe Tag Manager 177.8 kB · 84 ms CPU
TikTok 165.3 kB · 62 ms CPU
s-microsoft.com 63.9 kB · 0 ms CPU
mPulse 58.5 kB · 12 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 7.18 s 8.02 s ↓ -839 ms (-10.5%) 7.18 s 8.02 s
Long Tasks 20 20 → no change 20 20
DOM Elements 1,985 1,985 → no change 1,985 1,985
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 5 5 → no change 5 5
A11y Failures 1 1 → no change 1 1
A11y Failing Nodes 4 4 → no change 4 4

Main thread work

script evaluation 3.50 s
other 1.60 s
style layout 958 ms
script parse compile 775 ms
parse HTML 195 ms
garbage collection 75 ms
paint composite render 75 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 2 rules, 1996 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 tabindex — Elements should not have tabindex greater than zero 4 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 31 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.

  • tabindex — Some elements have a `[tabindex]` value greater than 0 4 nodes

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache http/1.1 6 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, 4:38 PM UTC 28 38.20 s 0.103 1.29 s 7.17 MB 3/3 ±3 2,673 62.3s
Aug 20, 2026, 4:30 PM UTC 26 39.67 s 0.103 1.60 s 7.18 MB 3/3 ±2 2,485 68.3s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show azure.microsoft.com/en-us/products/app-service/static'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://azure.microsoft.com/en-us/products/app-service/static"></speedlify-score>