Page Speed Checker
Analyze your webpage performance with our free page speed test tool. Check TTFB, page size, compression, caching, and get actionable recommendations to improve your site's loading speed and Core Web Vitals.
Test Page Speed
Enter one or more URLs to analyze their loading performance and get optimization tips
Enter a URL with or without https://
What This Tool Measures
Our page speed checker analyzes key performance metrics for each URL:
Performance Score Guide
No Results Yet
Enter a URL and click "Test Page Speed" to analyze performance
Your page speed analysis will appear here
How to Use This Page Speed Checker Tool
Using our page speed checker is simple and provides instant insights into your website's loading performance. Follow these steps to test any URL:
Enter Your URL
Type or paste the webpage URL you want to analyze. You can enter it with or without "https://" - we'll handle the formatting automatically.
Click "Test Page Speed"
Our tool will fetch your page, measure response times, analyze compression and caching headers, and count all resources referenced in your HTML.
Review Your Results
Get an overall performance score (0-100), detailed metrics breakdown, identified issues, and actionable recommendations to improve your page speed.
For bulk analysis, switch to the "Bulk Check" tab and enter multiple URLs (one per line) to compare performance across different pages of your website.
Why Page Speed Matters for SEO
Page speed is a critical ranking factor that directly impacts your website's search visibility, user experience, and conversion rates. Google has confirmed that site speed affects rankings, and with the introduction of Core Web Vitals, performance metrics are more important than ever.
Mobile users abandon sites that take over 3 seconds to load
Conversion rate decrease for every 1 second delay in load time
Of users are less likely to return after a bad experience
Key SEO Impacts of Page Speed:
- Google Ranking Factor: Since 2010, page speed has been a ranking signal for desktop searches, and since 2018 for mobile searches. Faster sites tend to rank higher.
- Core Web Vitals: Google's page experience update uses metrics like LCP, FID, and CLS to evaluate user experience. These are directly influenced by page speed.
- Crawl Budget: Faster sites allow Google to crawl more pages in the same amount of time, improving indexation of your content.
- User Engagement: Slow pages lead to higher bounce rates, lower time on site, and fewer page views - all signals that can negatively impact rankings.
- Mobile-First Indexing: With Google's mobile-first approach, page speed on mobile devices is particularly critical for SEO success.
Understanding Page Speed Metrics
Our page speed test measures several key metrics that indicate how fast your page loads. Here's what each metric means and why it matters:
Time to First Byte (TTFB)
TTFB measures the time from when the browser sends a request until it receives the first byte of the response. This metric indicates server responsiveness.
Page Size
The total size of the HTML document. Larger pages take longer to download, especially on slower connections. This doesn't include external resources like images and scripts.
Request Count
The number of external resources (scripts, stylesheets, images, fonts) referenced in your HTML. Each request adds latency, especially without HTTP/2.
Compression
Checks if your server uses gzip or Brotli compression to reduce transfer size. Compression can reduce HTML, CSS, and JavaScript file sizes by 60-80%, dramatically improving load times.
Browser Caching
Verifies the presence of Cache-Control, Expires, ETag, or Last-Modified headers. Proper caching allows browsers to store resources locally, making repeat visits significantly faster.
Core Web Vitals Explained
While this tool provides basic performance metrics, Google uses Core Web Vitals as official ranking signals. These metrics require real browser measurement and are more comprehensive:
Largest Contentful Paint (LCP)
Measures when the largest content element becomes visible. Good LCP is under 2.5 seconds. Affected by server response time, resource load time, and client-side rendering.
Interaction to Next Paint (INP)
Replaced First Input Delay (FID) in 2024. Measures responsiveness to all user interactions throughout the page lifecycle. Good INP is under 200 milliseconds.
Cumulative Layout Shift (CLS)
Measures visual stability - how much the page content shifts unexpectedly during loading. Good CLS is under 0.1. Caused by images without dimensions, ads, and dynamically injected content.
Note: For complete Core Web Vitals analysis, use Google PageSpeed Insights or Chrome DevTools, which measure these metrics in a real browser environment with actual rendering.
Best Practices for Page Speed Optimization
Follow these proven techniques to improve your website's loading speed and Core Web Vitals scores:
Enable Compression
Configure your server to use gzip or Brotli compression for text-based resources (HTML, CSS, JavaScript). This can reduce transfer sizes by 60-80%.
Optimize Images
Use modern formats like WebP or AVIF, compress images, serve responsive images with srcset, and lazy load images below the fold.
Minify Resources
Remove unnecessary characters from HTML, CSS, and JavaScript files. Use build tools like webpack, Vite, or similar to automate minification.
Leverage Browser Caching
Set appropriate Cache-Control headers for static assets. Use long cache times (1 year) for versioned assets and shorter times for HTML.
Use a CDN
Serve your content from edge servers close to your users. CDNs like Cloudflare, Fastly, or CloudFront can dramatically reduce latency worldwide.
Reduce JavaScript Execution
Defer non-critical JavaScript, use async loading, code-split your bundles, and remove unused JavaScript. Heavy JS is a major cause of slow INP scores.
Optimize Critical Rendering Path
Inline critical CSS, preload key resources, and eliminate render-blocking resources to improve First Contentful Paint and LCP.
Reduce Server Response Time
Optimize database queries, use server-side caching (Redis, Memcached), upgrade to faster hosting, and consider static site generation where possible.
Use Resource Hints
Implement preconnect for third-party domains, dns-prefetch for DNS lookups, and preload for critical assets to speed up resource loading.
Enable HTTP/2 or HTTP/3
Modern protocols allow parallel loading of multiple resources over a single connection, significantly improving load times for pages with many requests.
Common Page Speed Issues
Here are the most common performance problems we see and how to fix them:
Unoptimized Images
Problem: Large, uncompressed images are the #1 cause of slow pages. A single 5MB image can add seconds to load time.
Fix: Compress images (use TinyPNG, Squoosh), convert to WebP/AVIF, implement lazy loading, use responsive images with srcset, and always specify width/height attributes.
Render-Blocking JavaScript
Problem: Scripts in the <head> without async/defer block page rendering until they're downloaded and executed.
Fix: Add defer or async attributes to non-critical scripts, move scripts to the bottom of <body>, or use dynamic import() for code splitting.
Slow Server Response (High TTFB)
Problem: Server takes too long to respond due to slow database queries, unoptimized backend code, or distant hosting.
Fix: Implement server-side caching, optimize database queries, use a CDN, upgrade hosting, or consider static generation for content that doesn't change frequently.
No Compression Enabled
Problem: Text resources sent uncompressed, wasting bandwidth and increasing load times by 3-4x.
Fix: Enable gzip or Brotli compression in your web server configuration (nginx, Apache) or through your CDN settings.
Missing Cache Headers
Problem: Without caching headers, browsers re-download all resources on every page visit, wasting bandwidth.
Fix: Set Cache-Control: max-age=31536000 for static assets with versioned filenames. For HTML, use shorter cache times or ETag validation.
Frequently Asked Questions About Page Speed
What is a good page speed score?▼
A page speed score of 90-100 is considered fast and excellent for both user experience and SEO. Scores between 50-89 indicate room for improvement, while scores below 50 suggest significant performance issues. For Core Web Vitals specifically, aim for LCP under 2.5s, INP under 200ms, and CLS under 0.1.
How does page speed affect SEO rankings?▼
Page speed is a confirmed Google ranking factor for both desktop and mobile searches. Since 2021, Core Web Vitals have been part of Google's page experience signals. Faster sites tend to rank higher, especially in competitive markets. Additionally, slow sites have higher bounce rates, which indirectly impacts rankings through user engagement signals.
What is TTFB and why does it matter?▼
Time to First Byte (TTFB) measures how long it takes for the browser to receive the first byte of data from the server after sending a request. It indicates server responsiveness and affects all other performance metrics. A good TTFB is under 200ms. High TTFB usually indicates server-side issues like slow database queries, lack of caching, or distant hosting.
What is the ideal page size for fast loading?▼
Aim for total page weight under 2MB, with HTML under 100KB. The HTTP Archive reports the median page size is about 2.5MB, but faster sites are typically much lighter. For mobile users on 3G connections, smaller is better. Focus on optimizing images (often 50%+ of page weight) and minimizing JavaScript.
How many HTTP requests should a page have?▼
Aim for under 50 HTTP requests for optimal performance. With HTTP/2, the impact of multiple requests is reduced due to multiplexing, but each request still adds some overhead. Combine CSS files, bundle JavaScript, use CSS sprites for icons, and inline small resources to reduce request count.
Should I use gzip or Brotli compression?▼
Use Brotli when possible, as it typically achieves 15-20% better compression than gzip for text files. Brotli is supported by all modern browsers. However, gzip is still excellent and universally supported. Most servers can be configured to serve Brotli to supporting browsers and fall back to gzip for others.
What are Core Web Vitals?▼
Core Web Vitals are Google's metrics for user experience: Largest Contentful Paint (LCP) measures loading performance, Interaction to Next Paint (INP) measures interactivity, and Cumulative Layout Shift (CLS) measures visual stability. These are official ranking signals and should be optimized alongside traditional speed metrics.
How do I check my Core Web Vitals?▼
Use Google PageSpeed Insights (pagespeed.web.dev) for lab and field data, Google Search Console for site-wide Core Web Vitals reports, Chrome DevTools (Lighthouse tab) for detailed analysis, or the web-vitals JavaScript library to measure real user metrics.
Why is my page slow on mobile but fast on desktop?▼
Mobile devices have less processing power and often slower network connections. JavaScript execution takes longer on mobile CPUs, large images consume more bandwidth on mobile networks, and touch interactions can be blocked by heavy JavaScript. Test with throttled conditions (Chrome DevTools > Network tab) to simulate mobile performance.
Does using a CDN improve page speed?▼
Yes, significantly. A Content Delivery Network serves your content from servers geographically close to your users, reducing latency by 100-500ms or more. CDNs also handle compression, caching, HTTP/2, and DDoS protection. Popular options include Cloudflare, AWS CloudFront, Fastly, and Bunny CDN.
Can I check multiple URLs at once?▼
Yes! Switch to the "Bulk Check" tab to analyze up to 10 URLs simultaneously. Enter one URL per line, and our tool will test all pages in parallel. You can export all results as a CSV file for further analysis or reporting.
Tool Limitations
This page speed checker provides basic server-side metrics. While useful for quick analysis, it has some limitations compared to full browser-based tools:
Does Not Measure Core Web Vitals
LCP, INP, and CLS require real browser rendering and JavaScript execution, which this tool cannot perform.
Does Not Execute JavaScript
Client-side rendered content (React, Vue, Angular) and dynamically loaded resources are not analyzed.
Resource Sizes Not Measured
We count resources but don't fetch each one to measure actual file sizes. Use browser DevTools for detailed breakdowns.
What This Tool DOES Provide
TTFB measurement, HTML document size, resource counts from HTML parsing, compression detection, caching header analysis, and overall performance scoring. Great for quick checks and bulk comparisons.
For comprehensive analysis: Use Google PageSpeed Insights for detailed Core Web Vitals and Lighthouse audits, or Chrome DevTools for real-time debugging.
Related Tools
Technical SEO Audit
Comprehensive technical SEO analysis of any webpage
HTTP Header Checker
Analyze HTTP headers for security, SEO, and caching configuration
Complete SEO Report
Get a full website SEO analysis and action items
Redirect Checker
Check redirect chains, HTTP status codes, and identify redirect issues for any URL