A faster site keeps visitors from leaving and gets more customers through checkout. Measure first with PageSpeed Insights and Core Web Vitals, then fix things in the order that matters most: images, caching, scripts, PHP and a CDN.
You don't need a developer for the first steps. On small sites, most speed problems come from the same few causes: oversized images, too many plugins, no caching and an old PHP version. Below is a practical guide, in the order worth working through.
1. Measure before you change anything
Open PageSpeed Insights, enter your site's address and run the test. Look at the mobile and desktop results separately, because the gap is usually bigger on phones. Don't test only the home page: also test a product page or an article, since those are the pages people land on from Google.
The report has two parts. The top shows real data from your visitors (if your site has enough traffic), and the bottom is a lab test with specific recommendations. Google looks at the real data; you work on the recommendations.
What Core Web Vitals mean
Google uses three metrics called Core Web Vitals. The thresholds below are the ones published on web.dev at the time of writing, measured at the 75th percentile of visits (at least three visits out of four should be "good").
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | how long until the main element appears (usually the big image or the heading) | up to 2.5 s | over 4 s |
| INP (Interaction to Next Paint) | how quickly the page reacts when you click or type | up to 200 ms | over 500 ms |
| CLS (Cumulative Layout Shift) | how much content "jumps" while the page loads | up to 0.1 | over 0.25 |
Write down today's numbers. Test again after each change so you know what actually helped.
2. Images: the biggest win for the least effort
On almost any brochure site or small shop, images make up most of the page weight. A few simple rules:
- Use modern formats. WebP and AVIF are usually much smaller than JPEG or PNG at the same visual quality. WordPress has plugins that convert uploads automatically.
- Resize before uploading. A 4000 px photo shown in an 800 px box is pure waste. For most sites, 1600–2000 px on the long side is enough even for large images.
- Lazy loading. Images further down the page load only when the visitor scrolls to them. WordPress does this by default for most images. But the main image at the top should not be lazy-loaded, or your LCP gets worse.
- Set dimensions. Images with a declared width and height stop text from jumping around, so CLS goes down.
3. Caching: don't build the page from scratch on every visit
A WordPress site builds each page from PHP and the database. A caching plugin saves the finished page and serves it straight to the next visitors, which cuts server response time a lot.
What to check:
- only one caching plugin is active (two caching plugins get in each other's way);
- browser caching is on for static files (images, CSS, JavaScript);
- compression (gzip or Brotli) is on; PageSpeed shows it under "text compression".
For online shops, make sure the cart, checkout and customer account pages are excluded from the cache. Good plugins do this automatically for WooCommerce, but check anyway.
4. Fewer plugins and scripts
Every plugin, slider, chat widget, ad pixel or external font adds code that the browser has to download and run. This hits INP especially, which is how fast the page reacts to a click.
- List all active plugins and ask yourself about each one: do I really use it?
- Deactivate and delete what you don't use. A deactivated plugin left lying around is still a security risk.
- Replace do-everything plugins with one that does a single job well.
- Review external scripts (chat, analytics, ads) and keep only what adds value.
- Limit fonts to one or two families and a few weights.
Make these changes on a copy of the site first or, at the very least, right after a fresh backup.
5. An up-to-date PHP version
Newer PHP versions are generally faster and still receive security patches. At the time of writing, WordPress recommends PHP 8.3 or newer, and php.net shows that 8.1 and older no longer get security updates.
You usually change the PHP version in your hosting control panel (for example, in cPanel: "Select PHP Version" or "MultiPHP Manager"). Before switching, update WordPress, your theme and plugins, take a backup, then check the site page by page. Available versions differ between plans, so check what your plan includes.
6. A CDN for far-away visitors
A CDN (content delivery network) keeps copies of your static files on servers in many cities and serves each visitor from the nearest one. If your audience is mostly in Romania and the server is in Europe, there is a gain, but it is smaller than from images and caching. If you have visitors from several countries, a CDN helps noticeably. Many CDNs have a free plan. Setup usually means changing your nameservers or a few DNS records.
Checklist in order of priority
| Priority | Action | Helps with |
|---|---|---|
| 1 | Test in PageSpeed Insights (mobile + desktop) and note the numbers | baseline |
| 2 | Compress, resize and convert images to WebP/AVIF | LCP, page weight |
| 3 | Enable one caching plugin and compression | response time, LCP |
| 4 | Remove plugins and external scripts you don't need | INP, LCP |
| 5 | Declare sizes for images and banners | CLS |
| 6 | Move to a supported PHP version (after a backup and a test) | speed, security |
| 7 | Add a CDN, especially if you have visitors abroad | LCP far away |
| 8 | Retest after every step | knowing what worked |
If you've done all of this and the server is still slow to respond, your site may have outgrown its plan. Compare our WordPress hosting and cloud hosting options, or write to us at [email protected] and we'll take a look together.
In short
Measure with PageSpeed Insights, then work in order: optimised images, caching, fewer plugins and scripts, current PHP and, if needed, a CDN. Retest after every change, and don't touch anything without a fresh backup.
