How to increase page speed
A faster WordPress website helps visitors read, browse and enquire with less waiting. Start by finding the slowest part of the experience, then make one measured improvement at a time.
Google uses Core Web Vitals within its ranking systems, but a good score does not guarantee a higher ranking. Helpful, relevant content still matters.
Measure before changing anything
Use PageSpeed Insights on important pages. Check mobile and desktop results. Real-user data, when available, describes actual visits; Lighthouse lab tests help diagnose a particular test run. Repeat tests under similar conditions rather than chasing a single score.
Look at loading speed, responsiveness and visual stability. A slow connection or older device can also affect the experience.
Check hosting and server response
Hosting resources, server configuration, caching and the distance to visitors can affect response time. An Australian server may suit a mainly Australian audience, but location or price alone does not prove that hosting is fast. Compare measured response times and the support available.
Reduce image and page weight
Resize images to suit their displayed size and compress them without visibly damaging quality. Consider WebP or AVIF where supported. Avoid downloading a large original when a smaller responsive image will do. Set image dimensions to reduce layout shifts.
Lazy-load images below the initial view, but do not lazy-load the main image responsible for Largest Contentful Paint.
Handle video embeds carefully
A video platform can handle streaming and storage, but its embedded player can still add substantial page weight. Use a poster image or click-to-load player where appropriate. Moving images to an unrelated image-sharing site is not a reliable speed strategy; optimise delivery through your own media setup or a suitable CDN.
Keep fonts and scripts lean
Load only the font families and weights you use. Remove unused features and avoid loading page-specific assets everywhere. Hosting suitable assets locally can reduce extra connections, but it is not automatically faster. Check the actual requests and loading behaviour before changing delivery.
Do not combine every file by default
Modern HTTP/2 and HTTP/3 connections can handle multiple requests efficiently. Combining all CSS or JavaScript into one large file can make visitors download code they do not need. Prioritise removing unused code and reducing render-blocking work, then test any minification or bundling change.
Investigate errors and slow requests
Slow database queries, failed requests or PHP errors can affect some pages even when others are quick. Use server logs and profiling to locate the cause. More plugins does not automatically mean a slower site: what each plugin does matters.
Test compatibility before publishing
Take a backup and test theme, plugin and supported PHP updates on staging where possible. Check the pages and interactions visitors rely on after each change. Do not apply optimisation settings indiscriminately to a live site.
Use caching where it fits
Page caching can reduce repeated WordPress work for public pages. Browser caching and, when justified, object caching or a CDN can also help. Pages containing personalised or changing information need appropriate exclusions.
Need help maintaining WordPress? Compare our care and support plans, or return to the website guides.
Further reading: Google’s page experience guidance, optimising Largest Contentful Paint and WordPress optimisation guidance.
