01 / Guides
Why is my WordPress website slow? Measure before you change anything
Before installing a plugin that promises to make everything faster, measure where you are. Open Google's PageSpeed Insights and test a typical inner page, not just the home page. At the top you see real user data from the last 28 days (if your site has enough visitors), and below that a lab test. For Google and for your visitors, the real data is what counts.
Also ask what is slow: the site for visitors, the admin area while editing, or both? And did it happen gradually or suddenly? A sudden slowdown almost always has a specific cause: an update, a new plugin, bot traffic or even a hack.
02 / Guides
The targets: Core Web Vitals
Google measures loading experience with three metrics, the Core Web Vitals. Since March 2024 INP has been the metric for responsiveness. Server response time is a useful early warning on top:
| Metric | What it measures | Good |
|---|---|---|
| LCP (Largest Contentful Paint) | When the largest visible element has loaded, often the hero image | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds to clicks and typing | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much content jumps around while loading | 0.1 or less |
| TTFB (Time to First Byte) | How long the server takes to send its first response | 0.8 seconds or less |
03 / Guides
Symptom, cause, fix
| Symptom | Likely cause | First fix |
|---|---|---|
| High TTFB, every page starts sluggishly | Weak shared hosting, old PHP version, no page cache | Turn on page caching, check the PHP version, check the hosting plan |
| Poor LCP, especially on mobile | Huge hero image or slider, render-blocking CSS and JavaScript, external fonts | Resize the hero image and serve it as WebP or AVIF, drop the slider |
| Poor INP | Lots of JavaScript from the page builder, chat widgets, tracking and pop-ups | Cut external scripts, delay the rest |
| Only the admin area is slow | Plugins running database queries in the admin, Heartbeat, WP-Cron, WooCommerce reports | Measure with Query Monitor, disable the culprit |
| Suddenly very slow | Plugin update, bot attack on wp-login.php, full disk, a problem at the host, a hack | Undo the last change, check server logs and resource usage with your host |
04 / Guides
How to speed up WordPress: the order that pays off
Work through the steps one by one and measure again after each. That way you know what helped and you do not introduce new problems.
- 01
Backup and staging
Take a full backup. Many hosts offer a one-click staging copy. Test there, not on the live site.
- 02
Check PHP and hosting
Tools, Site Health shows your PHP version. If you are still on PHP 7, switch to a current, supported PHP 8 version in your hosting panel. That alone is often a clear speed gain. Check first that your theme and plugins are compatible.
- 03
Set up page caching
A page cache serves ready-made HTML instead of building every page for every visit. On LiteSpeed servers (Hostinger, for example) LiteSpeed Cache is the first choice; otherwise WP Rocket or your host's own cache. Use only one caching plugin.
- 04
Optimise images
Upload images at the size they are displayed and serve them as WebP or AVIF. WordPress has lazy loading built in, but the hero image at the top of the page should load straight away, not lazily.
- 05
Clean up plugins
Delete deactivated plugins and remove duplicate features. The free Query Monitor plugin shows which plugins cause the most and slowest database queries.
- 06
Cut external scripts
Chat widgets, several tracking tools, embedded maps and videos, and fonts loaded from Google's servers all slow a page down. Load only what you really need, and host fonts yourself.
- 07
Slim down the database
Old revisions, expired transients and leftovers from deleted plugins bloat the database. Site Health warns when autoloaded options get too large. The WP_POST_REVISIONS constant in wp-config.php limits future revisions.
- 08
Object cache and CDN
For shops and large sites, an object cache such as Redis helps a lot if your host offers it. A CDN mainly helps when your visitors come from several countries.
05 / Guides
Elementor and other page builders
Slow Elementor sites are among the most common complaints in this area, and for good reason. Page builders produce a lot of nested HTML, load their own scripts and styles, and tempt you into effects, sliders and animations that make every page heavier.
Elementor has performance features in its settings that load scripts and styles only where they are needed. Switch them on and test afterwards. Skip sliders in the header, use containers instead of nested sections, and keep Elementor add-ons to a minimum. If a page still sits at 4 or 5 seconds LCP, the limit is usually in how it is built, not in a setting.
06 / Guides
WordPress site slow when logged in: the admin area
Logged-in users do not get pages from the page cache, which is why the public site can be fast while the admin area crawls. Common causes are plugins that call external servers on every admin page, for licence checks or upsell banners, large WooCommerce reports, the Heartbeat API sending requests every minute while you edit, and WP-Cron starting scheduled tasks on page loads.
Query Monitor shows the slow queries and the plugins behind them on every admin page. On busier sites it helps to switch off WP-Cron with DISABLE_WP_CRON in wp-config.php and set up a real cron job at your host that runs every five to fifteen minutes instead.
07 / Guides
Cheap shared hosting: when the plan is the limit
Budget shared hosting plans share processing power with many other customers and cap memory and concurrent PHP processes. Beyond a certain point, no amount of optimisation helps.
If your TTFB stays above one second even with caching active, a better plan or a new host is usually the cheapest fix. How to move without breaking email, DNS and redirects is covered in our overview of server setup for small businesses. We are a verified Hostinger partner and say so openly whenever we recommend Hostinger.
08 / Guides
When a rebuild beats optimisation
A theme with a page builder, 40 plugins and five years of leftovers can be optimised to acceptable, but rarely to fast. If you are thinking about a new design anyway, a lean rebuild often pays back sooner than a third round of tuning. Our article on signs you need a website redesign helps you decide.
We do not use WordPress ourselves. We write our sites by hand, without page builders or plugins, with modern image formats and self-hosted fonts. That is web design and web development at Tanomedia, and a website migration brings the content and URLs of your WordPress site with you. Speed also feeds into rankings, as our guide to SEO for small businesses explains.
FAQ
Common questions
01Why is my WordPress site suddenly so slow?
Almost always something changed: a plugin or theme update, a new plugin, bot traffic on the login page, a full disk or a problem at your host. Undo the last change and ask your host about resource usage and logs. A hack can also show up this way.
02Which caching plugin is best for WordPress?
The one that matches your server. On LiteSpeed servers, LiteSpeed Cache is usually the most effective; otherwise WP Rocket or your host's own cache are good choices. The key is to run only one caching plugin at a time.
03How many plugins are too many?
The number alone says little. A well-built plugin costs almost nothing, a badly built one can slow the whole site on its own. Measure with Query Monitor which plugins cost time, and remove anything you do not really use.
04Does Elementor slow down WordPress?
Elementor produces more code than a lean theme, and add-ons, sliders and animations make that worse. With Elementor's performance features, few add-ons and optimised images, decent scores are possible; top scores rarely.
05Which PHP version should WordPress use?
A current PHP 8 version that still receives security updates. The current recommendation is listed in the requirements on wordpress.org. Test the switch on a staging copy first, because old plugins can throw errors on newer PHP versions.
06Why is WordPress only slow when I am logged in?
Logged-in users are not served cached pages, and extra plugins, Heartbeat and reports run in the admin area. Visitors usually notice nothing. Query Monitor shows which plugin slows the admin down.