pypi.org

https://pypi.org/

Data from Aug 25, 2026, 4:37 PM UTC 13h old

Overall #1,261 Package Managers #8 · 1 measurement · since Aug 25, 2026

Core Web Vitals field data, url-level

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

LCP 1.73 s good

INP 126 ms good

CLS 0 good

Scores

Performance

no change

Accessibility

no change

Best Practices

no change

100

SEO

no change

Lab metrics Lighthouse, mobile

Metric	Current	Previous	Change	Best	Worst
LCP Largest Contentful Paint	4.28 s	—	—	4.28 s	4.28 s
CLS Cumulative Layout Shift	0.331	—	—	0.331	0.331
TBT Total Blocking Time	20 ms	—	—	20 ms	20 ms
FCP First Contentful Paint	2.70 s	—	—	2.70 s	2.70 s
Speed Index	2.70 s	—	—	2.70 s	2.70 s
TTFB Time to First Byte	603 ms	—	—	603 ms	603 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 4.28 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.

element render delay 87 ms

time to first byte 19 ms

Field data Chrome UX Report, url-level

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

Metric	p75	Rating	Distribution (good / needs work / poor)
LCP CWV	1.73 s	good	86.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run	126 ms	good	86.4% good
CLS CWV	0	good	95.1% good
FCP	1.74 s	good	75.9% good
TTFB	904 ms	needs-improvement	71.4% good

Metric

p75

Rating

Distribution (good / needs work / poor)

LCP CWV

1.73 s

good

86.3% good

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

126 ms

good

86.4% good

CLS CWV

good

95.1% good

FCP

1.74 s

good

75.9% good

TTFB

904 ms

needs-improvement

71.4% good

Lab vs field

Lab LCP 4.28 s · field p75 1.73 s · real users are 0.4× faster than the lab.

Field history 25 weeks

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

Week ending	LCP	INP	FCP	TTFB
2026-08-22	1.74 s	126 ms	1.75 s	912 ms
2026-08-15	1.84 s	127 ms	1.86 s	982 ms
2026-08-08	1.83 s	125 ms	1.85 s	979 ms
2026-08-01	1.80 s	121 ms	1.82 s	972 ms
2026-07-25	1.68 s	118 ms	1.71 s	909 ms
2026-07-18	1.42 s	114 ms	1.45 s	749 ms
2026-07-11	1.36 s	113 ms	1.38 s	681 ms
2026-07-04	1.37 s	112 ms	1.39 s	675 ms
2026-06-27	1.30 s	105 ms	1.32 s	642 ms
2026-06-20	1.34 s	104 ms	1.35 s	665 ms
2026-06-13	1.36 s	103 ms	1.37 s	685 ms
2026-06-06	1.41 s	104 ms	1.42 s	719 ms

Week ending

LCP

INP

CLS

FCP

TTFB

2026-08-22

1.74 s

126 ms

1.75 s

912 ms

2026-08-15

1.84 s

127 ms

1.86 s

982 ms

2026-08-08

1.83 s

125 ms

1.85 s

979 ms

2026-08-01

1.80 s

121 ms

1.82 s

972 ms

2026-07-25

1.68 s

118 ms

1.71 s

909 ms

2026-07-18

1.42 s

114 ms

1.45 s

749 ms

2026-07-11

1.36 s

113 ms

1.38 s

681 ms

2026-07-04

1.37 s

112 ms

1.39 s

675 ms

2026-06-27

1.30 s

105 ms

1.32 s

642 ms

2026-06-20

1.34 s

104 ms

1.35 s

665 ms

2026-06-13

1.36 s

103 ms

1.37 s

685 ms

2026-06-06

1.41 s

104 ms

1.42 s

719 ms

Page weight

Metric	Current	Previous	Change	Best	Worst
Page Weight	576 kB	—	—	576 kB	576 kB
Requests	21	—	—	21	21
Third-party Weight	13.3 kB	—	—	13.3 kB	13.3 kB
Third-party CPU	6 ms	—	—	6 ms	6 ms
Unused JS	68.7 kB	—	—	68.7 kB	68.7 kB
Unused CSS	192 kB	—	—	192 kB	192 kB

By resource type

stylesheet 204 kB · 3 req

font 183 kB · 6 req

script 121 kB · 4 req

image 53.9 kB · 2 req

other 7.9 kB · 5 req

document 7.0 kB · 1 req

third party 13.3 kB · 4 req

Third parties 3 entities

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

ethicalads.io 9.0 kB · 3 ms CPU

python.org 3.0 kB · 3 ms CPU

Statuspage 1.2 kB · 0 ms CPU

Page health

Metric	Current	Previous	Change	Best	Worst
Main Thread Work	536 ms	—	—	536 ms	536 ms
Long Tasks	2	—	—	2	2
DOM Elements	215	—	—	215	215
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset	14	—	—	14	14
A11y Failures	1	—	—	1	1
A11y Failing Nodes	15	—	—	15	15

Main thread work

style layout 168 ms

other 158 ms

script evaluation 146 ms

script parse compile 26 ms

parse HTML 19 ms

paint composite render 18 ms

Axe violations axe-core 4.13.0, full rule set

14 violating nodes across 1 rule, 448 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.

moderate region — All page content should be contained by landmarks 14 nodes

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

target-size — Touch targets do not have sufficient size or spacing. 15 nodes

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	Perf	LCP	CLS	TBT	Weight	Runs	Spread	Bench	Took
Aug 25, 2026, 4:37 PM UTC	65	4.28 s	0.331	20 ms	576 kB	3/3	±6	2,506	51.7s

When

Perf

LCP

CLS

TBT

Weight

Runs

Spread

Bench

Took

Aug 25, 2026, 4:37 PM UTC

4.28 s

0.331

20 ms

576 kB

3/3

±6

2,506

51.7s

Embed this score

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