Skip to content

What is p99 Latency

Key idea:

p99 latency — the 99th percentile of response time: the value above which 1% of requests fall. It reflects the worst-case experience for roughly 1 out of 100 users. Matters more than median (p50) because the "middle" user is happy but the worst 1% are your loudest critics. Typical ratio: p99 = 10-20× p50. Cloud-native apps aim for p99 < 500ms.

Below: details, example, related terms, FAQ.

Details

  • p50 (median): half of requests faster, half slower
  • p95: 95% faster, 5% slower
  • p99: 99% faster, 1% slower (tail)
  • p99.9: 999 / 1000 — tighter, "three nines"
  • Causes of p99 outliers: cold start, GC pause, network retries, DB lock

Example

Response times: 50, 80, 100, 120, 150, ..., 850, 2400 ms
p50 = 120 ms (middle)
p99 = 2400 ms (1-of-100 worst)
p99/p50 ratio = 20× (high tail)

Related Terms

PerformanceOverall speed score 0-100
Core Web VitalsLCP, FID, CLS — Google metrics
Page SizeSize of HTML, CSS, JS, images
RecommendationsSpecific tips for improvement

Why teams trust us

Lighthouse
analysis engine
CWV
Core Web Vitals
4
Lighthouse categories
Precise
recommendations

How it works

1

Enter page URL

2

Lighthouse analyzes

3

Get CWV scores & tips

Why Does Site Speed Matter?

Page load speed directly impacts conversion, SEO rankings, and user satisfaction. Google uses Core Web Vitals as a ranking factor. Every extra second of load time cancost up to 7% in conversions.

Lighthouse Analysis

Google Lighthouse-based analysis: Performance, Accessibility, Best Practices, SEO.

Core Web Vitals

LCP (rendering), FID (interactivity), CLS (visual stability) — key Google metrics.

Resource Analysis

Breakdown by type: HTML, CSS, JavaScript, images, fonts. Size, request count, blocking resources.

Actionable Advice

Specific recommendations with savings estimates: image compression, caching, minification, etc.

Mobile vs Desktop

Mobile
  • Tested on Moto G Power emulation (slow CPU)
  • Network: 4G (1.6 Mbps, 150ms RTT)
  • Stricter speed scoring
  • Google indexes mobile-first
  • Priority for SEO optimization
Desktop
  • High CPU performance
  • Fast connection without throttling
  • Scores typically 20-40 points higher
  • Important for B2B and corporate sites
  • Use for baseline comparisons

Who uses this

SEO

Core Web Vitals for rankings

Developers

performance optimization

Marketers

speed = conversions

DevOps

performance regression

Common Mistakes

Unoptimized imagesImages can be up to 70% of page weight. Use WebP/AVIF and lazy loading.
Render-blocking JS in &lt;head&gt;Scripts without async/defer block rendering. Move to end or add attribute.
No static asset cachingWithout Cache-Control, the browser reloads CSS/JS on every visit.
Too many HTTP requestsEach request adds latency. Bundle files, use sprites, or inline critical CSS.
Missing compression (gzip/brotli)Compression reduces text resource size by 60-80%. Enable brotli on the server.

Best Practices

Optimize imagesWebP for photos, SVG for icons. loading="lazy" for images below the fold.
Enable brotli compressionBrotli is 15-20% more efficient than gzip. Configure in nginx: brotli on;
Set up cachingStatic: Cache-Control: max-age=31536000, immutable. HTML: max-age=0, s-maxage=60.
Preload critical resources<link rel="preload"> for fonts and CSS. Reduces LCP by 200-500ms.
Test regularlySpeed degrades over time. Check after each deploy and monthly.

Get more with a free account

Speed check history, competitor comparison and PageSpeed monitoring.

Sign up free

Learn more

Frequently Asked Questions

Why not the mean?

Mean is skewed by outliers. p50/p95/p99 are more stable and reflect user experience.

How to measure at low traffic?

Histogram buckets (Prometheus, DataDog). At 100 req/day p99 = worst-1, which is noisy. Use p95 + weekly rolling.

How to improve p99?

1) Cache hit ratio. 2) Connection pools (DB, Redis). 3) Circuit breakers. 4) Timeout + retry + jitter. 5) Async I/O.