Improving page speed positively affects both the visitor's willingness to stay on your site and the way search engines evaluate your page. A slow page drives users away, and Google considers user experience as a small signal through Core Web Vitals. The good news is that slowness on most sites comes from a few recurring causes, and these can be fixed one at a time. This guide describes directly applicable steps in order of greatest impact, without going into the definitions of metrics.
Measure first: know what to fix
Optimizing blindly wastes time. The first task is to see where your site is genuinely slow:
- PageSpeed Insights: Test your home page and the 2–3 pages that receive the most traffic. The result has two sections: real user data (if available) and laboratory testing. Base your decisions on real user data.
- Search Console → Core Web Vitals: Shows problematic page groups in bulk.
- Browser developer tools (Network tab): Lets you find the largest and slowest-loading files by sorting them.
We explained what the LCP, INP, and CLS metrics mean and their threshold values in our Core Web Vitals guide; we will not repeat them here. Since slowness is more pronounced on mobile devices, be sure to evaluate the tests on the mobile tab too (for details, see our mobile SEO guide).
1. Server and caching
If the page starts loading late, before even the first byte arrives, image and code optimization will not solve the problem. Server response time (TTFB) generally depends on hosting quality, database queries, and cache configuration.
- Page caching: Serve pages that do not change often as ready-made HTML instead of regenerating them on every request. In CMSs such as WordPress, reliable caching plugins exist for this; in your own software, add full-page or fragment caching.
- Compression: Compress text files (HTML, CSS, JS) with Brotli or gzip; it takes only a few lines in the server configuration.
- HTTP/2 or HTTP/3: Allows multiple files to load in parallel over a single connection. Most modern hosting providers offer it out of the box.
- CDN: Serving static files from servers closer to the visitor shortens load times, especially for sites with visitors from different regions.
- Database and plugins: Clean up slow queries and unused plugins; every plugin can add extra workload to the server.
- Current PHP version: Moving PHP-based sites to the latest supported version (after testing compatibility first) brings gains in both speed and security.
For browser caching, you can give long-term cache headers to static files that contain a version number or a hash:
Cache-Control: public, max-age=31536000, immutable
As long as the file name changes (for example site.a1b2c3.css), this header ensures the browser does not re-download the file for a year.
If the file name stays the same, do not give such a long period; updates will not reach users.
2. Reduce image sizes
Images make up the largest share of the data downloaded on most pages, so the biggest gain is usually here.
- Use modern formats. WebP or AVIF usually delivers the same visual quality as JPEG/PNG in a noticeably smaller file.
- Upload at the size it is displayed. Showing a 3000-pixel-wide photo in a 600-pixel area is unnecessary data. Use
srcsetto serve different sizes to different screens. - Define width and height. The
widthandheightattributes prevent the page from shifting while it loads. - Lazy-load below-the-fold images. Add
loading="lazy"; but do not use it on the main image at the top of the page, load that one with priority (fetchpriority="high"). - Avoid video and animated GIFs. Converting short animations to a video format is much lighter.
Image visibility in search results is a separate topic; for file names, alt text, and image sitemaps, see our image SEO guide.
3. Reduce the CSS and JavaScript load
- Minification and bundling: Remove whitespace and comments. Bundling is not as critical under HTTP/2 as it once was; the real goal is to reduce the total size.
- Remove unused code. The "Coverage" panel in developer tools shows the proportion of CSS/JS that never runs on the page. If a large framework or library is loaded for only a few functions, keep only the part you need.
- Defer blocking scripts. Add
deferorasyncto non-critical scripts so the page does not wait for them before rendering. - Critical CSS: Placing the styles needed for the first visible part of the page inside the HTML and loading the rest later speeds up the first paint. This makes a difference especially with large theme files, but it requires careful implementation.
- Review JavaScript-generated content. Heavy JavaScript can cause both slowness and crawling problems; to check how Google sees this content, see the relevant section of our technical SEO checklist.
Too many plugin warnings: In WordPress and similar systems, a frequent cause of page speed problems is dozens of plugins, each loading its own CSS and JS files. Deleting plugins you do not use is often more effective than any speed plugin.
4. Fonts
- Few fonts and weights. Each additional weight means a separate download; load only the ones you actually use.
- Modern format (WOFF2). It is smaller than older formats.
- Serve from your own server. This removes the cost of connecting to a third-party domain.
font-display: swap: Shows the text with a system font until the web font arrives, so the page does not stay blank.
5. Third-party scripts
Analytics, live support, advertising, maps, social media, and cookie tools each download additional files from outside and occupy the main thread. They can slow down outside your control. What to do:
- List all the third-party scripts you use; looking at the domains in the Network tab is enough.
- Remove the ones that are no longer used (for example, an old analytics code nobody looks at anymore).
- Defer the necessary ones so they run after the page loads; loading a live support window only after user interaction is a typical example.
- Replace embedded maps and videos with a lightweight preview image until the user clicks.
In what order should you do it?
Do not try to do everything at once. The order below is based on the effort-to-impact balance for most sites:
| Order | Step | Usual impact | Difficulty |
|---|---|---|---|
| 1 | Compressing the main image and large images and converting them to WebP | High (especially LCP) | Low |
| 2 | Page caching and compression | High | Low–medium |
| 3 | Removing unnecessary plugins and scripts | Medium–high | Low |
| 4 | Setting image dimensions, adjusting the font | Medium (especially CLS) | Low |
| 5 | Deferring JS/CSS, critical CSS | Medium | Medium–high |
| 6 | CDN, server upgrade | Varies by site | Medium |
After each step, measure again with PageSpeed Insights and note the change. Because field data (real users) is updated over a window of roughly 28 days, it can take weeks for an improvement to appear in Search Console; do not rush and pile new changes on top of each other.
How quickly a page is abandoned also matters alongside speed; for this, you can read our guide to reducing bounce rate. Once your site is fast and technically sound, you may also consider the organic hit approach to support your visibility work in search results; a tool such as HitBot does not determine rankings, that decision is made by Google's algorithms. A fast site, however, increases the value of every visit it receives.
Keeping speed over time: regular checks
After a site has been sped up, new content, new plugins, and new scripts can bring slowness back. To keep the results, set up a simple maintenance routine:
- Pre-publication rule: Every image added to a page should be compressed and at the correct size. Give this to your content team as a written rule.
- New script approval: If a new tracking code, marketing tool, or plugin is to be added, test its speed impact first.
- Monthly measurement: Measure the home page and the most-trafficked pages in PageSpeed Insights every month and record them in a table; you will notice sudden deterioration right away.
- Search Console alerts: If the number of pages classed as "poor" in the Core Web Vitals report increases, review the latest changes.
- After major changes: After a theme, hosting, or CMS update, re-verify all speed-related settings.
Frequently asked questions
Is page speed a direct ranking factor?
Google says it uses page experience (including Core Web Vitals) in ranking, but it also states that this is a weaker signal than content relevance. The real damage of slowness appears as lost users.
Does the PageSpeed score have to be 100?
No. The score is a laboratory simulation and it varies. The goal is for the metrics in real user data to fall within the "good" range; chasing a score of 100 is often not worth the effort.
Is installing a speed plugin enough?
Plugins make tasks such as caching, compression, and deferring easier; however, they cannot fix on their own large unoptimized images, a heavy theme, or unnecessary scripts. Address the root causes.
Why are mobile and desktop speeds different?
Mobile tests simulate slower network and processor conditions. That is why mobile results are usually lower and should be your priority.
Conclusion
Page speed is not a one-time task but a habit that requires regular maintenance. Start by measuring, work through the largest items (images, caching, unnecessary scripts), and verify the result after each step. To check the technical foundation covering your whole site, you can use our technical SEO checklist.