You open your site on your phone, and while it loads you have time to take a sip of coffee. A potential client does not take that sip: they simply close the tab and go to a competitor. Site speed is not a technical decoration, but a direct loss of enquiries. The good news is that in most cases slowness has a few predictable causes, and they can be fixed.
In short: WordPress sites are most often slowed down by heavy images, too many plugins, page builders, weak hosting, lack of caching and third-party scripts. Google’s targets: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1. Measure in PageSpeed Insights and fix by priority: images → cache → plugins → hosting.
First measure: three numbers that matter
Do not fix things “by eye”. The free Google PageSpeed Insights tool shows how the site performs for real users and in lab conditions. Look not at the overall score, but at the three Core Web Vitals metrics:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP | How long the main element of the screen takes to load | up to 2.5 s | over 4 s |
| INP | How quickly the site responds to a tap or click | up to 200 ms | over 500 ms |
| CLS | Whether the layout “jumps” while loading | up to 0.1 | over 0.25 |
A score of 100 is not needed. It guarantees neither rankings nor requests, and the “green zone” on all three metrics is more than enough. Check the mobile version: most visitors come from phones.
8 reasons why WordPress is slow and what to do about them
1. Heavy images
A 4–6 MB camera photo inserted into a banner is a classic. Compress to a reasonable size, use modern formats (WebP), set width and height, and enable lazy loading for images below the first screen. This is usually the biggest gain for the least effort.
2. Too many plugins
Each plugin is extra code that runs on every page. A site with 40 plugins is almost always slower than the same site with 15. Remove unused ones, replace “heavy all-in-one” plugins with narrow solutions, and enable features needed on only one page only on that page.
3. Page builder
Elementor, WPBakery and similar tools add a lot of auxiliary code and scripts. They are convenient to use at the start, but noticeably slow the site down. Switching to a lightweight custom theme often gives the biggest speed jump, while the look stays the same.
4. Weak or cheap hosting
If the server takes more than 600–800 ms to respond before the page even starts loading, no image optimisation will save it. Server response time (TTFB) is visible in the same PageSpeed report. Moving to a better plan or a different host may be the only way out.
5. Missing caching
Without caching, WordPress rebuilds every page from the database. With caching, the visitor gets a ready page. Set up page and browser caching, and for large sites also object caching.
6. Fonts and icons
Five font styles from a third-party server and an icon library of 3000 glyphs for ten icons is a common situation. Keep two or three styles, load fonts from your own domain, and load only the icons you need.
7. Third-party scripts
Chat widgets, pixels, counters, video embeds — each loads its own files and slows the site’s response. Defer their loading, remove the ones that bring no benefit, and embed videos “lazily”.
8. Outdated technology and a bloated database
An old PHP version runs slower than a new one, and over the years the database accumulates post revisions and temporary data. Update PHP to a current supported version and clean up the database.
What gives the biggest effect: the order of actions
| Step | Effect | Complexity |
|---|---|---|
| Compress and replace images | High | Low |
| Enable caching | High | Low |
| Remove unnecessary plugins | Medium–high | Medium |
| Switch from a page builder to a lightweight theme | Very high | High |
| Change hosting | Depends on the problem | Medium |
| Defer third-party scripts | Medium | Medium |
30-minute checklist: what to do yourself
- Run PageSpeed Insights for the home page and two key pages (mobile version).
- Look at the “Opportunities” section: it lists the heaviest files.
- Find images over 500 KB in the media library and replace them with compressed versions.
- Open the list of plugins and deactivate the ones you do not use.
- Enable a caching plugin and check that the request forms work.
- Run PageSpeed again and compare the numbers.
When doing it yourself is not enough
If the figures stay red after the basic steps, the cause is deeper: in the theme, the database or on the server. Then an audit is needed. With us, on the WordPress services page, site speed optimisation costs from 800 UAH, an audit with a PDF report and priorities — from 1000 UAH, and switching from Elementor to a fast theme — from 6000 UAH. Not sure what is slowing things down? Describe the problem in the “What is wrong with your website?” form: we will check it and tell you the likely cause and what to do about it. No obligation.
A typical story: a site that only looks normal on the surface
The owner of an online shop complains: the site takes several seconds to open, and the advertising seems to “leak”. We look at the report. The banner on the home page is an image several megabytes in size, fonts load from three different sources, three page builders and about thirty plugins run in the background, half of which nobody has opened for ages. The server responds slowly because there is no caching.
None of these problems requires rebuilding the site from scratch. Compress the images, remove the unnecessary plugins, enable caching — and the site already shows green. A separate page-builder theme can wait: replacing it gives the biggest effect, but also requires the most work. This sequence (cheap steps → medium → complex) is a healthy approach to optimisation.
Frequently asked questions about site speed
How many seconds should a site take to load?
The Google guideline is the main content of the screen (LCP) within 2.5 seconds on a mobile device. The faster the better, but already being in the “green zone” noticeably improves the experience.
Does speed affect Google rankings?
Yes, Core Web Vitals are among the page experience signals. However, relevance and text quality matter more: a fast site without the right answers will not get rankings.
Will an optimisation plugin solve the problem?
Partly. Caching and compression will give a noticeable gain, but if the cause is a page-builder theme or weak hosting, deeper changes are needed.
How long does speeding up a site take?
For a typical site it is 1–3 days, depending on the causes and whether the theme needs to be changed. We state the exact timeline after the audit.
Shall we discuss your task?
Tell us what you need and we'll name the cost and timeline. We work directly.
