Free Website Performance Test - Check Your Page Speed

Time to First Byte measures how long it takes your server to send the first byte of data after a request. We test your TTFB and flag slow responses. A TTFB under 200ms is considered good. Slow server response is often caused by overloaded hosting, unoptimized databases, or missing server-side caching. This metric directly impacts every other performance measurement.

We measure the total weight of your page including HTML, CSS, JavaScript, images, and fonts. Pages over 3MB take significantly longer to load, especially on mobile connections. The average web page is now over 2MB, but the fastest sites keep their pages under 1MB. We break down your page weight by resource type so you can see exactly what's contributing to bloat.

Text-based resources like HTML, CSS, and JavaScript can be compressed by 60-80% before being sent to the browser. We check whether your server enables gzip or Brotli compression for these resources. Enabling compression is one of the highest-impact, lowest-effort performance optimizations you can make - most web servers support it with a single configuration change.

Images typically account for 50% or more of a page's total weight. We check for oversized images, missing width/height attributes (which cause layout shift), and opportunities to use modern formats like WebP and AVIF. Properly optimized images can reduce page weight by 30-50% with no visible quality loss, dramatically improving load times on mobile devices.

Large inline CSS and JavaScript blocks bloat your HTML document and prevent browser caching. We detect excessive inline resources and recommend extracting them into external files. External resources can be cached by the browser, loaded in parallel, and shared across pages - reducing load times for returning visitors by up to 80%.

Resource hints like dns-prefetch, preconnect, preload, and prefetch tell the browser to start loading critical resources earlier. We check whether your page uses these hints for important third-party domains and critical assets. Proper resource hints can reduce perceived load time by hundreds of milliseconds by eliminating connection setup delays.

Every HTTP request adds latency. We count the total number of requests your page makes and identify opportunities to reduce them through bundling, spriting, or eliminating unnecessary resources. While HTTP/2 mitigates some of the per-request overhead, excessive requests still impact performance, especially on high-latency mobile connections.

CSS and JavaScript files in the document head block the browser from rendering any content until they're downloaded and processed. We identify render-blocking resources and suggest techniques like deferring non-critical scripts, inlining critical CSS, and using async loading. Reducing render-blocking resources improves First Contentful Paint and perceived load speed.