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

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

Data from Aug 23, 2026, 6:30 PM UTC 3h old

Web Hosts #17 · 4 measurements · since Aug 20, 2026

Core Web Vitals field data, url-level

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

LCP 3.65 s needs-improvement

INP site-wide 304 ms needs-improvement

CLS 0.110 needs-improvement

Scores

Performance

↓ -6 (-18.7%)

Accessibility

no change

Best Practices

no change

SEO

no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.95 s.

494 ms
987 ms
1.48 s
1.98 s
2.47 s
2.96 s
3.46 s
3.95 s

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	22.40 s	36.82 s	↓ -14421 ms (-39.2%) significant	22.40 s	39.67 s
CLS Cumulative Layout Shift	0.103	0.103	→ no change	0.103	0.103
TBT Total Blocking Time	1.58 s	878 ms	↑ +698 ms (+79.5%) significant	878 ms	1.60 s
FCP First Contentful Paint	12.27 s	18.50 s	↓ -6232 ms (-33.7%) significant	12.27 s	20.73 s
Speed Index	12.27 s	18.50 s	↓ -6232 ms (-33.7%) significant	12.27 s	20.73 s
TTFB Time to First Byte	650 ms	644 ms	↑ +6 ms (+0.9%)	619 ms	650 ms

Metric

Current

Change

Best

Worst

Trend

LCP Largest Contentful Paint

22.40 s

36.82 s

↓ -14421 ms (-39.2%) significant

22.40 s

39.67 s

CLS Cumulative Layout Shift

0.103

→ no change

0.103

TBT Total Blocking Time

1.58 s

878 ms

↑ +698 ms (+79.5%) significant

878 ms

1.60 s

FCP First Contentful Paint

12.27 s

18.50 s

↓ -6232 ms (-33.7%) significant

12.27 s

20.73 s

Speed Index

12.27 s

18.50 s

↓ -6232 ms (-33.7%) significant

12.27 s

20.73 s

TTFB Time to First Byte

650 ms

644 ms

↑ +6 ms (+0.9%)

619 ms

650 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 22.40 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.

resource load delay 850 ms

time to first byte 530 ms

element render delay 139 ms

resource load duration 87 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	3.65 s	needs-improvement	57.2% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	304 ms	needs-improvement	63.4% good
CLS CWV	0.110	needs-improvement	44.3% good
FCP	2.35 s	needs-improvement	61.7% good
TTFB	955 ms	needs-improvement	62.8% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

3.65 s

needs-improvement

57.2% good

INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run

304 ms

needs-improvement

63.4% good

CLS CWV

0.110

needs-improvement

44.3% good

FCP

2.35 s

needs-improvement

61.7% good

TTFB

955 ms

needs-improvement

62.8% good

Lab vs field

Lab LCP 22.40 s · field p75 3.65 s · real users are 0.16× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending	LCP	INP	CLS	FCP	TTFB
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
Page Weight	6.66 MB	6.94 MB	↓ -273.0 kB (-4%)	6.66 MB	7.18 MB
Requests	161	163	↓ -2 (-1.2%)	161	175
Third-party Weight	801 kB	800 kB	↑ +1.1 kB (+0.1%)	800 kB	808 kB
Third-party CPU	332 ms	243 ms	↑ +90 ms (+36.9%)	243 ms	361 ms
Unused JS	1.47 MB	1.43 MB	↑ +36.9 kB (+2.6%)	1.43 MB	1.47 MB
Unused CSS	175 kB	175 kB	→ no change	175 kB	175 kB

Metric

Current

Change

Best

Worst

Trend

Page Weight

6.66 MB

6.94 MB

↓ -273.0 kB (-4%)

6.66 MB

7.18 MB

Requests

161

163

↓ -2 (-1.2%)

161

175

Third-party Weight

801 kB

800 kB

↑ +1.1 kB (+0.1%)

800 kB

808 kB

Third-party CPU

332 ms

243 ms

↑ +90 ms (+36.9%)

243 ms

361 ms

Unused JS

1.47 MB

1.43 MB

↑ +36.9 kB (+2.6%)

1.43 MB

1.47 MB

Unused CSS

175 kB

→ no change

175 kB

By resource type

script 3.96 MB · 84 req

image 1.49 MB · 26 req

font 947 kB · 5 req

stylesheet 212 kB · 21 req

document 42.6 kB · 2 req

other 13.9 kB · 23 req

third party 6.66 MB · 161 req

Third parties 19 entities

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

Facebook 222 kB · 111 ms CPU

Adobe Tag Manager 178 kB · 86 ms CPU

TikTok 165 kB · 75 ms CPU

s-microsoft.com 63.9 kB · 0 ms CPU

mPulse 58.5 kB · 15 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	7.50 s	5.38 s	↑ +2123 ms (+39.5%)	5.38 s	8.02 s
Long Tasks	20	18	↑ +2 (+11.1%)	18	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.61 s

other 1.66 s

style layout 1.03 s

script parse compile 822 ms

parse HTML 176 ms

paint composite render 120 ms

garbage collection 90 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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 23, 2026, 6:30 PM UTC	26	22.40 s	0.103	1.58 s	6.66 MB	3/3	±1	2,439	66.7s
Aug 22, 2026, 5:22 PM UTC	32	36.82 s	0.103	878 ms	6.94 MB	3/3	±10	3,359	76s
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

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 23, 2026, 6:30 PM UTC

22.40 s

0.103

1.58 s

6.66 MB

3/3

±1

2,439

66.7s

Aug 22, 2026, 5:22 PM UTC

36.82 s

0.103

878 ms

6.94 MB

3/3

±10

3,359

76s

Aug 21, 2026, 4:38 PM UTC

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

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 speedlify2-score.js component code into your site!

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://azure.microsoft.com/en-us/products/app-service/static"></speedlify2-score>