Skip to content

How to Reduce Time to First Byte

TL;DR:

To reduce TTFB: (1) deploy a CDN (Cloudflare/Fastly) — edge caching for static assets; (2) enable server-level cache (Redis/Memcached for DB queries); (3) optimise slow SQL queries via EXPLAIN; (4) enable HTTP/2 and TLS 1.3. Target TTFB — < 200 ms.

Step-by-step guide

  1. Measure current TTFB. Via PageSpeed checker or Chrome DevTools → Network → pick HTML request → Timing.
  2. Enable CDN. Cloudflare (free) or Fastly — caches static assets on 300+ edge servers. Reduces TTFB by 30-70%.
  3. Server-side caching. For dynamic pages: Redis/Memcached for SQL results. Nginx fastcgi_cache for HTML.
  4. Optimise SQL. EXPLAIN on slow queries. Add indexes. Kill N+1 queries via eager loading.
  5. Database tuning. Ensure DB is on different disks than the web server. Minimum — SSD.
  6. HTTP/2 and TLS 1.3. Multiplexing + 1-RTT handshake save 100-300 ms.
  7. Geographic distribution. If your audience is global — use multi-region hosting + DNS load balancer.

Open tool →

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

Signup required?

No for quick check. For continuous monitoring — free account.