Slow WordPress sites are rarely slow for exotic reasons. A handful of causes account for most of the problem. Work through them in this order and measure after each step so you know what helped.
1. Measure before you change anything
Run your homepage and one inner page through PageSpeed Insights or the Lighthouse panel in Chrome. Note three numbers from Google's Core Web Vitals:
- Largest Contentful Paint (LCP): how quickly the main content appears. Aim for 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page reacts to taps and clicks. Aim for 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the layout jumps while loading. Aim for 0.1 or less.
Test on the mobile setting. That is where most sites struggle and where most visitors are.
2. Fix the images
Images are usually the heaviest part of a page.
- Resize images to the size they are displayed at. A 4000-pixel photo shown in a 800-pixel column wastes bandwidth.
- Use modern formats such as WebP or AVIF where your setup supports them.
- Lazy-load images below the fold, but not the main image at the top, which should load first.
- Give images width and height so the layout does not jump.
3. Look at hosting
If the server takes a long time to respond, nothing else helps much. Check the "time to first byte" in your test results. Cheap shared plans that are overloaded, old PHP versions and distant servers all show up here. Make sure you run a current, supported PHP version and ask your host about server-level caching.
4. Add caching, once
A page cache stores a finished copy of each page so WordPress does not rebuild it for every visitor. Use one caching plugin or your host's built-in cache. Running two at the same time causes confusing bugs. Clear the cache after design changes.
5. Audit plugins
Each plugin can add scripts, styles and database queries. Deactivate anything you do not use and delete it. Be sceptical of plugins that load their assets on every page when they are needed on one. Replace several single-purpose plugins with one well-built option where that is sensible.
6. Tame scripts and fonts
- Limit web fonts to the weights you actually use, and host them yourself if you can.
- Remove chat widgets, trackers and embeds you no longer look at.
- Delay non-essential scripts until after the page is usable.
7. Keep the database and builder tidy
Clean old post revisions and expired transients occasionally. If you use Elementor, keep pages simple: deeply nested sections and many widgets produce more markup. Use the built-in performance and loading options for your version.
What a lean theme gives you
Starting from a lightweight, well-structured theme means less to undo later. When you compare themes, open the demo, run the same speed test on it and look at the page weight. A demo that is already heavy will not get lighter with your content on it.
If you would like someone to do the work, our performance optimization service is quoted individually. Otherwise, the steps above cost nothing but time.