How to Use Free Tools to Improve Website Performance
Slow sites lose visitors and rankings. These free tools help you diagnose and fix performance issues — from Core Web Vitals to image optimisation — without paying for expensive software.
Website performance is both a user experience issue and a search engine ranking issue. Google Core Web Vitals are confirmed ranking signals, and slow pages consistently show higher bounce rates and lower conversion rates. The good news is that diagnosing and fixing most performance problems does not require paid software — the most effective tools are free.
Understanding Core Web Vitals
Google measures three main performance signals for ranking purposes:
- Largest Contentful Paint (LCP) — How quickly the main content of the page loads. Target: under 2.5 seconds. Poor: over 4 seconds.
- Cumulative Layout Shift (CLS) — How much the page layout moves unexpectedly during loading. Target: under 0.1. Poor: over 0.25.
- Interaction to Next Paint (INP) — How quickly the page responds to user input. Target: under 200 milliseconds. Poor: over 500 milliseconds.
All three are measurable with free tools and fixable with targeted optimisation work.
Google PageSpeed Insights
PageSpeed Insights (free, by Google) gives you a real-world performance score based on Chrome user field data and a prioritised list of improvements. Run it on your most important pages: homepage, key tool or product pages, and your highest-traffic blog post.
Focus on the Opportunities and Diagnostics sections — these contain the actionable fixes. Common high-impact improvements: properly size images, eliminate render-blocking resources that delay the initial paint, and reduce unused JavaScript that loads on every page but is only needed on some pages.
WebPageTest
WebPageTest (free, webpagetest.org) provides deeper performance analysis: a waterfall chart showing every resource load in sequence, a filmstrip view of the page loading frame by frame, and the ability to test from multiple geographic locations and connection speeds. Use WebPageTest when PageSpeed Insights gives you a score but you need to understand the specific sequence of what is causing the slowdown.
Image Optimisation
Images are typically the single largest contributor to page weight. Practical steps to reduce their impact:
- Convert JPEG and PNG files to WebP or AVIF format. Squoosh (free, by Google) converts images in the browser with adjustable quality. WebP files are typically 25 to 35 percent smaller than equivalent JPEGs.
- Set explicit width and height attributes on all images. This tells the browser how much space to reserve before the image loads, preventing layout shift.
- Use the loading="lazy" attribute on below-the-fold images. This defers loading until the user scrolls toward them, reducing initial page weight.
- Use a CDN with automatic format negotiation if available. Cloudflare serves WebP automatically to browsers that support it at no cost on the free tier.
JavaScript and CSS Optimisation
Unused JavaScript and CSS slow down page rendering by forcing the browser to parse and compile code it will never execute on that page. Use the Coverage tab in Chrome DevTools — built into Chrome, no installation required — to identify which scripts and stylesheets contain dead code. Third-party scripts (chat widgets, social embeds, analytics tools) are common culprits. Load them with defer or async attributes, or replace heavy third-party scripts with lighter self-hosted alternatives.
Browser Caching and CDN
Appropriate cache headers on static assets mean repeat visitors load cached resources instead of re-downloading them. For most static assets, a max-age of one year with content hash fingerprinting in the filename is ideal — the hash changes when the file changes, so the cache is always valid. Cloudflare free tier adds a CDN layer with automatic asset caching and basic performance optimisations at no cost.
A Systematic Approach
Run PageSpeed Insights on your five most important pages. Fix the three highest-impact issues it identifies before moving to other optimisations. Measure again after each fix. Repeat. Chasing a perfect 100 score is less productive than systematically addressing the issues that matter most for real users on real connections.