Loading…
Calculate your website load time based on total page size and visitor connection speeds. Understand how load time affects SEO rankings, bounce rate, and user experience. Get actionable recommendations to improve Core Web Vitals scores.
Website load time is one of the most critical factors for both user experience and SEO rankings. Google uses Core Web Vitals (LCP, FID/INP, CLS) as ranking signals. Studies show that 53% of mobile users abandon pages that take more than 3 seconds to load, and every 1-second delay reduces conversions by 7%.
Website load time depends on total page size, number of HTTP requests, server response time, CDN usage, browser caching, and the visitor connection speed. Optimizing all these factors is essential for good Core Web Vitals scores and high search rankings.
| Page Size | Load Time (WiFi 8MB/s) | Load Time (3G 1MB/s) | Assessment |
|---|---|---|---|
| < 500 KB | < 0.5s (fast WiFi) | < 2s (3G) | Excellent — text-heavy site |
| 500 KB - 1 MB | 0.5-1s | 2-4s | Good — well-optimized |
| 1 MB - 2 MB | 1-2s | 4-8s | Average — room for improvement |
| 2 MB - 5 MB | 2-5s | 8-20s | Slow — optimize images |
| 5 MB - 10 MB | 5-10s | 20-40s | Very slow — significant issues |
| > 10 MB | > 10s | > 40s | Unacceptable — major optimization needed |
Google Core Web Vitals are three metrics: LCP (Largest Contentful Paint — time to render main content, target under 2.5 seconds), INP (Interaction to Next Paint — response to user input, target under 200ms), and CLS (Cumulative Layout Shift — visual stability, target under 0.1). Failing these metrics can reduce search rankings.
Images account for 60-80% of page weight on most websites. Optimization tips: convert images to WebP format (25-35% smaller than JPEG), implement lazy loading for below-fold images, use responsive images with srcset, compress images with Squoosh or Cloudinary, minify CSS/JS/HTML (saves 10-30%), enable Gzip/Brotli compression on server (saves 60-80%), use a CDN for static assets, and leverage browser caching.
Over 60% of web traffic is mobile. Mobile connections are slower (typical mobile is 10-40 Mbps), and mobile CPUs are weaker at parsing JavaScript. Google uses mobile page speed as the primary ranking signal (mobile-first indexing). Always test page speed on mobile connection speeds, not just desktop WiFi.