---
title: "Speed Up WordPress: 15 Practical Actions That Work"
description: "Speed up your WordPress site with 15 practical actions: server cache, PHP, images, CSS/JS, fonts, third-party scripts, database and Core Web Vitals."
url: https://hosterwise.com/en/blog/speed-up-wordpress/
language: en
updated: 2026-10-15
source: Hosterwise
translations:
fr: https://hosterwise.com/blog/accelerer-site-wordpress.md
---
Canonical page:
[Performance](https://hosterwise.com/en/category/performance-en/) 11 min read
# Speed Up WordPress: 15 Practical Actions That Work
Speed up your WordPress site with 15 practical actions: server cache, PHP, images, CSS/JS, fonts, third-party scripts, database and Core Web Vitals.
By L’équipe Hosterwise · Hosterwise technical and support team
Published October 8, 2026 Updated October 15, 2026
## In this article
Share
- [Share on LinkedIn (new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
- [Share on X (new tab)](https://x.com/intent/post?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F&text=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work)
- [Send by e-mail](mailto:?subject=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work&body=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
To speed up a WordPress site, start with the server (fast hosting, [page caching](https://hosterwise.com/en/glossary/#page-cache), a current PHP version), then tackle what the browser downloads (images, CSS, JavaScript, fonts, third-party scripts), and finish with maintenance (plugins, database, scheduled tasks). Measure before and after every change: it is the only way to know what actually worked.
*Guide current as of 8 October 2026. Thresholds quoted are those published by Google on web.dev.*
**Key takeaways**
- **Measure first** with [PageSpeed Insights](https://pagespeed.web.dev/): Google calls a page fast when [LCP](https://hosterwise.com/en/glossary/#lcp) ≤ 2.5 s, [INP](https://hosterwise.com/en/glossary/#inp) ≤ 200 ms and [CLS](https://hosterwise.com/en/glossary/#cls) ≤ 0.1 for 75% of visits.
- The best-value trio: **server-side page caching, optimised images, a trimmed plugin list**.
- **Never [lazy-load](https://hosterwise.com/en/glossary/#lazy-loading) the main above-the-fold image**: it is often the one that sets your LCP.
- **Third-party scripts** (chat, ad pixels, embedded videos) often weigh more than WordPress itself.
- One change at a time, one test after each: some optimisations break layouts.
## How do you measure a WordPress site’s speed?
Run PageSpeed Insights on your most visited pages: it shows field data from real visitors (Chrome UX Report) alongside a lab diagnosis. The three [Core Web Vitals](https://hosterwise.com/en/glossary/#core-web-vitals) are LCP (main content display), INP (responsiveness to interactions) and CLS (layout stability).
Google rates a page as good when these thresholds are met for 75% of visits:
| Metric | What it measures | Good | Needs improvement | Poor |
| --- | --- | --- | --- | --- |
| [LCP](https://web.dev/articles/lcp) | Time to render the largest visible element | ≤ 2.5 s | 2.5–4 s | > 4 s |
| [INP](https://web.dev/articles/inp) | Delay before responding to clicks and typing | ≤ 200 ms | 200–500 ms | > 500 ms |
| [CLS](https://web.dev/articles/cls) | Unexpected layout shifts | ≤ 0.1 | 0.1–0.25 | > 0.25 |
| [TTFB](https://web.dev/articles/ttfb) (guide) | Server response time | ≤ 0.8 s | 0.8–1.8 s | > 1.8 s |
*Thresholds published by Google on web.dev, as of 8 October 2026. TTFB is not a Core Web Vital, but it drives LCP.*
Write down your starting values for the home page and one typical page (post, product page), on mobile. Field data takes about four weeks to reflect a change because it covers a rolling 28-day window; to judge right away, compare lab measurements.
## Server side: which actions speed up WordPress the most?
The biggest gains nearly always come from the server: a page cache stops WordPress rebuilding every page, a recent PHP version runs code faster, and an object cache takes load off the database. All three cut TTFB, which everything else depends on.
### 1. Choose hosting built for WordPress
Overloaded or poorly configured hosting caps every other optimisation. Check the web server (LiteSpeed, or Nginx or Apache with an efficient cache), the PHP versions available, the resources allocated to your account and HTTP/2 or HTTP/3 support. Measure your TTFB: above 0.8 seconds on a cached page, the server is the likely bottleneck. Our [honest WordPress hosting comparison](https://hosterwise.com/en/blog/best-wordpress-hosting/) covers these criteria.
### 2. Turn on page caching
Without a cache, each visit runs PHP and dozens of SQL queries. With page caching, the server returns a ready-made HTML copy. On a LiteSpeed server, the free LiteSpeed Cache plugin drives the server’s built-in cache: follow our [step-by-step LiteSpeed Cache setup](https://hosterwise.com/en/blog/litespeed-cache-setup/). On other servers, use one well-established caching plugin, and only one.
### 3. Move to a recent PHP version
Every major PHP release brings performance improvements, and older versions stop receiving security fixes (see the [official PHP supported versions](https://www.php.net/supported-versions.php)). WordPress recommends [PHP 8.3 or later](https://wordpress.org/about/requirements/). Test on a staging copy first: old plugins may be incompatible. Your active version is shown under **Tools > Site Health > Info > Server**.
### 4. Add an object cache for dynamic sites
WooCommerce stores, membership sites and busy admin areas run many queries that page caching does not cover. A persistent object cache (Redis or Memcached), when your host provides one, keeps the results of those queries in memory. For a fully cached brochure site, the gain is small: it is not a priority. At Hosterwise, Redis is available on every plan: turn it on under **LiteSpeed Cache > Cache > Object**, as explained in our [LiteSpeed Cache guide](https://hosterwise.com/en/blog/litespeed-cache-setup/).
## How do you optimise images on a WordPress site?
Compress your images, serve them as WebP or AVIF at the right size with their dimensions declared, and lazy-load only those below the fold. Images are often the heaviest part of a page and frequently determine LCP.
### 5. Compress and convert images
Resize photos before uploading (a 4,000-pixel-wide image has no place in a blog post) and convert them to WebP, or even AVIF. WordPress automatically generates several sizes plus a `srcset` attribute so the browser can pick the best one. An optimisation plugin, such as LiteSpeed Cache’s image module, automates compression and conversion.
### 6. Prioritise the main image instead of lazy-loading it
Lazy loading helps for images further down the page but is [counterproductive for the LCP image](https://web.dev/articles/lcp-lazy-loading). Since WordPress 6.3, core automatically adds `fetchpriority="high"` to the image it considers most likely to be the LCP element, as explained in the [official announcement](https://make.wordpress.org/core/2023/07/13/image-performance-enhancements-in-wordpress-6-3/). Make sure your theme or caching plugin does not undo this by adding `loading="lazy"` to that image:
```
```
### 7. Reserve space for images and blocks
CLS measures elements that “jump” while the page loads. The usual culprits: images without `width` and `height` attributes, cookie banners or ads injected above content, and web fonts that change text size. Always declare image and iframe dimensions and reserve ad slot height in CSS. The [Optimize CLS](https://web.dev/articles/optimize-cls) guide covers each case.
## Theme, plugins, CSS and JavaScript: how do you slim down the code?
A lightweight theme, a sensible number of plugins and CSS and JavaScript that are minified and loaded without blocking rendering improve both LCP and INP. The goal is not zero plugins, but running only the code each page actually needs.
### 8. Pick a lightweight theme
Some all-in-one themes load sliders, icon sets and animations on every page whether you use them or not. A block theme, or a theme known for being lean, cuts CSS and JavaScript from the outset. If you use a page builder, switch off unused modules in its settings.
### 9. Audit your plugins
The number of plugins matters less than what they do. A single badly coded plugin can slow the whole site. Temporarily install [Query Monitor](https://wordpress.org/plugins/query-monitor/) to spot slow queries and plugins that load files on every page. Delete (not just deactivate) plugins you no longer use, and replace ones that overlap.
### 10. Minify and defer CSS and JavaScript
Minification strips whitespace and comments; deferring (`defer`) stops scripts from blocking rendering. In LiteSpeed Cache, turn on “CSS Minify”, “JS Minify” and “Load JS Deferred”; leave file combining off, as it adds little over HTTP/2 and HTTP/3. More aggressive options (unused CSS removal, JS delayed until interaction) score well but must be tested page by page.
### 11. Self-host your fonts
Every font loaded from an external service adds another connection. Host fonts on your own server in WOFF2, limit the number of weights and use `font-display: swap` so text shows immediately. Preload the main font if it styles the heading visible on load ([best practices on web.dev](https://web.dev/articles/font-best-practices)):
```
```
### 12. Rein in third-party scripts
Chat tools, ad pixels, maps, embedded videos and social widgets come from other servers, bypass your cache and often hurt INP. Take an inventory, remove what you no longer need, load the rest after consent or after interaction, and replace embedded videos with a clickable thumbnail that loads the player on demand. See web.dev’s guide to [third-party JavaScript](https://web.dev/articles/third-party-javascript).
Read also
- [LiteSpeed vs Nginx vs Apache: Which Web Server for WordPress?](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/)
- [How Much Does WordPress Hosting Cost in 2026? Real Prices and Hidden Costs](https://hosterwise.com/en/blog/wordpress-hosting-cost/)
## Database and scheduled tasks: how do you keep WordPress in shape?
Clean the database regularly, cap revisions, keep an eye on autoloaded options and hand scheduled tasks to a real server cron job instead of page visits. These steps lighten server load and steady response times, especially in the admin.
### 13. Clean up the database
Post revisions, auto drafts, spam comments and expired transients pile up over time. Take a backup, then clean them with your performance plugin’s database tool (LiteSpeed Cache has one). Then cap the number of stored revisions in `wp-config.php`. Also watch **Site Health**, which flags an excessive amount of options autoloaded on every page.
```
// wp-config.php: above the "That's all, stop editing!" line
define( 'WP_POST_REVISIONS', 10 );
```
### 14. Replace WP-Cron with a real cron job
By default, WordPress triggers scheduled tasks (scheduled posts, e-mails, backups) on page visits. On a busy site that adds needless requests; on a quiet one, tasks run late. The fix, described in the [WordPress developer documentation](https://developer.wordpress.org/plugins/cron/hooking-wp-cron-into-the-system-task-scheduler/), is to stop visits triggering cron and call `wp-cron.php` on a schedule from the server’s task scheduler (at Hosterwise, the Cron Jobs section of CyberPanel).
```
// wp-config.php
define( 'DISABLE_WP_CRON', true );
```
```
# Server cron job (control panel): every 5 minutes
*/5 * * * * wget -q -O - "https://www.example.com/wp-cron.php?doing_wp_cron" >/dev/null 2>&1
```
### 15. Use HTTP/3, compression and, if needed, a CDN
HTTP/2 and HTTP/3 load many files in parallel over a single connection; HTTP/3, built on QUIC, copes better with flaky mobile networks. Also check that the server compresses text files (Brotli or gzip). Finally, if a large share of visitors are far from your server, a CDN brings static files closer to them. For an audience mostly in the same region as your server, it is rarely the top priority.
```
# Check the compression and protocols advertised
curl -sI -H "Accept-Encoding: br, gzip" https://www.example.com/ | grep -i -E "content-encoding|alt-svc"
```
## Where should you start? The 15 actions ranked
Start with what gives the most for the least effort: page caching, images, plugins. Keep fine-tuning (critical CSS, delayed JavaScript) for last, once the basics are in place and measured.
| # | Action | Main metric improved | Effort |
| --- | --- | --- | --- |
| 1 | Hosting built for WordPress | TTFB, LCP | Switching hosts |
| 2 | Page caching | TTFB, LCP | Low |
| 3 | Recent PHP | TTFB | Low (test first) |
| 4 | Object cache | TTFB (dynamic pages) | Low if provided |
| 5 | Images compressed as WebP/AVIF | LCP | Low |
| 6 | LCP image prioritised, not lazy-loaded | LCP | Low |
| 7 | Image dimensions and reserved slots | CLS | Low to medium |
| 8 | Lightweight theme | LCP, INP | High (redesign) |
| 9 | Plugin audit | TTFB, INP | Medium |
| 10 | Minified, deferred CSS/JS | LCP, INP | Low to medium |
| 11 | Self-hosted fonts, font-display: swap | LCP, CLS | Medium |
| 12 | Fewer third-party scripts | INP, LCP | Medium |
| 13 | Clean database | TTFB (admin) | Low |
| 14 | Real cron job | Server load | Low |
| 15 | HTTP/3, compression, CDN if needed | LCP | Low to medium |
*The 15 actions and their main effect. How much you gain depends on your site: measure before and after.*
## How do you know your optimisations worked?
Repeat your baseline measurements on the same pages under the same conditions (mobile, private window, warm cache) and compare. For field data, wait four weeks and follow the Core Web Vitals report in Search Console, which groups your URLs by status.
Log every change with its date: if a metric gets worse, you will know what to roll back. To go further, WordPress’s official documentation on [performance optimisation](https://developer.wordpress.org/advanced-administration/performance/optimization/) and the [Chrome UX Report](https://developer.chrome.com/docs/crux) explain where the numbers come from.
## Hosting built for WordPress speed
Actions 1 to 4 and 15 depend largely on your host. At [Hosterwise](https://hosterwise.com/en/), every plan runs on LiteSpeed Enterprise servers with LSCache, a Redis object cache, HTTP/3 and free SSL certificates, which covers most of the server-side work. The Premium and Boost plans add CPU and memory for dynamic sites such as WooCommerce: compare them on our [pricing](https://hosterwise.com/en/pricing/) page or explore our [LiteSpeed WordPress hosting](https://hosterwise.com/en/litespeed-hosting/).
Is your site hosted elsewhere? We move it for you with our [free migration](https://hosterwise.com/en/free-migration/), using the method described in our guide to [migrating a WordPress site with zero downtime](https://hosterwise.com/en/blog/migrate-wordpress-site/).
## WordPress speed FAQ
### Why is my WordPress site slow?
The usual causes are overloaded hosting or no caching, heavy images, a theme or plugins that load lots of code, and third-party scripts. Start by measuring TTFB: above 0.8 seconds, look at the server and caching; below that, look at what the browser downloads.
### Which plugin should I use to speed up WordPress?
On a LiteSpeed server, LiteSpeed Cache is the logical choice, because it drives the server’s own cache and bundles most optimisations. On Apache or Nginx, choose one well-established caching plugin. Only run one: two active caching plugins get in each other’s way.
### Is a good PageSpeed score enough?
No. The lab score is a one-off diagnosis; Google mainly relies on field data (real visitors’ Core Web Vitals). A score of 100 achieved by delaying all JavaScript can hide poor real-world responsiveness. Aim for good Core Web Vitals rather than a number.
### Does the number of plugins slow WordPress down?
Not directly: a few badly built plugins weigh more than many lightweight ones. What matters is the code loaded on each page and the queries it runs. Query Monitor helps you spot the costly ones before deciding what to keep.
### Do I need a CDN for my WordPress site?
Not necessarily. If most visitors are in the same region as your server, a good server cache and optimised images do more than a CDN. A CDN becomes useful for an international audience or to absorb big traffic spikes.
### Can switching hosts really speed up a site?
Yes, when the server is the bottleneck: high TTFB even on cached pages, outdated PHP, no server-side cache. If TTFB is already good, gains will come from images, theme and scripts instead. Measure before you decide.
Share
- [Share on LinkedIn (new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
- [Share on X (new tab)](https://x.com/intent/post?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F&text=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work)
- [Send by e-mail](mailto:?subject=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work&body=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
## LiteSpeed WordPress hosting from 6,99 €/month
Starter, Premium or Boost: free SSL, automatic backups, free migration and a 30-day guarantee.
[Compare plans](https://hosterwise.com/en/pricing/)
About the author
## L’équipe Hosterwise
Hosterwise technical and support team
Written and reviewed by the Hosterwise technical team, who run LiteSpeed servers with CyberPanel every day and help customers migrate, secure and speed up their WordPress sites.
## Keep reading
[All articles](https://hosterwise.com/en/blog/)
[Performance](https://hosterwise.com/en/category/performance-en/)
### [LiteSpeed Cache Setup: Step-by-Step Settings for 2026](https://hosterwise.com/en/blog/litespeed-cache-setup/)
Set up LiteSpeed Cache for WordPress step by step: presets, caching, CSS/JS, images and WooCommerce. Settings checked against plugin version 7.9.
October 8, 202613 min read
[Performance](https://hosterwise.com/en/category/performance-en/)
### [LiteSpeed vs Nginx vs Apache: Which Web Server for WordPress?](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/)
LiteSpeed vs Nginx vs Apache for WordPress: architecture, .htaccess, caching, HTTP/3 and market share compared, plus which one to pick for your site.
October 13, 202611 min read
[Guides](https://hosterwise.com/en/category/guides-en/)
### [How Much Does WordPress Hosting Cost in 2026? Real Prices and Hidden Costs](https://hosterwise.com/en/blog/wordpress-hosting-cost/)
How much does WordPress hosting cost in 2026? Prices by hosting type, intro versus renewal pricing, four-year totals, hidden costs and budgets by project, based on public prices checked on 16 October 2026.
October 16, 202614 min read
---
Markdown version of , generated by Hosterwise. Site index for AI assistants:
```
### 7. Reserve space for images and blocks
CLS measures elements that “jump” while the page loads. The usual culprits: images without `width` and `height` attributes, cookie banners or ads injected above content, and web fonts that change text size. Always declare image and iframe dimensions and reserve ad slot height in CSS. The [Optimize CLS](https://web.dev/articles/optimize-cls) guide covers each case.
## Theme, plugins, CSS and JavaScript: how do you slim down the code?
A lightweight theme, a sensible number of plugins and CSS and JavaScript that are minified and loaded without blocking rendering improve both LCP and INP. The goal is not zero plugins, but running only the code each page actually needs.
### 8. Pick a lightweight theme
Some all-in-one themes load sliders, icon sets and animations on every page whether you use them or not. A block theme, or a theme known for being lean, cuts CSS and JavaScript from the outset. If you use a page builder, switch off unused modules in its settings.
### 9. Audit your plugins
The number of plugins matters less than what they do. A single badly coded plugin can slow the whole site. Temporarily install [Query Monitor](https://wordpress.org/plugins/query-monitor/) to spot slow queries and plugins that load files on every page. Delete (not just deactivate) plugins you no longer use, and replace ones that overlap.
### 10. Minify and defer CSS and JavaScript
Minification strips whitespace and comments; deferring (`defer`) stops scripts from blocking rendering. In LiteSpeed Cache, turn on “CSS Minify”, “JS Minify” and “Load JS Deferred”; leave file combining off, as it adds little over HTTP/2 and HTTP/3. More aggressive options (unused CSS removal, JS delayed until interaction) score well but must be tested page by page.
### 11. Self-host your fonts
Every font loaded from an external service adds another connection. Host fonts on your own server in WOFF2, limit the number of weights and use `font-display: swap` so text shows immediately. Preload the main font if it styles the heading visible on load ([best practices on web.dev](https://web.dev/articles/font-best-practices)):
```
```
### 12. Rein in third-party scripts
Chat tools, ad pixels, maps, embedded videos and social widgets come from other servers, bypass your cache and often hurt INP. Take an inventory, remove what you no longer need, load the rest after consent or after interaction, and replace embedded videos with a clickable thumbnail that loads the player on demand. See web.dev’s guide to [third-party JavaScript](https://web.dev/articles/third-party-javascript).
Read also
- [LiteSpeed vs Nginx vs Apache: Which Web Server for WordPress?](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/)
- [How Much Does WordPress Hosting Cost in 2026? Real Prices and Hidden Costs](https://hosterwise.com/en/blog/wordpress-hosting-cost/)
## Database and scheduled tasks: how do you keep WordPress in shape?
Clean the database regularly, cap revisions, keep an eye on autoloaded options and hand scheduled tasks to a real server cron job instead of page visits. These steps lighten server load and steady response times, especially in the admin.
### 13. Clean up the database
Post revisions, auto drafts, spam comments and expired transients pile up over time. Take a backup, then clean them with your performance plugin’s database tool (LiteSpeed Cache has one). Then cap the number of stored revisions in `wp-config.php`. Also watch **Site Health**, which flags an excessive amount of options autoloaded on every page.
```
// wp-config.php: above the "That's all, stop editing!" line
define( 'WP_POST_REVISIONS', 10 );
```
### 14. Replace WP-Cron with a real cron job
By default, WordPress triggers scheduled tasks (scheduled posts, e-mails, backups) on page visits. On a busy site that adds needless requests; on a quiet one, tasks run late. The fix, described in the [WordPress developer documentation](https://developer.wordpress.org/plugins/cron/hooking-wp-cron-into-the-system-task-scheduler/), is to stop visits triggering cron and call `wp-cron.php` on a schedule from the server’s task scheduler (at Hosterwise, the Cron Jobs section of CyberPanel).
```
// wp-config.php
define( 'DISABLE_WP_CRON', true );
```
```
# Server cron job (control panel): every 5 minutes
*/5 * * * * wget -q -O - "https://www.example.com/wp-cron.php?doing_wp_cron" >/dev/null 2>&1
```
### 15. Use HTTP/3, compression and, if needed, a CDN
HTTP/2 and HTTP/3 load many files in parallel over a single connection; HTTP/3, built on QUIC, copes better with flaky mobile networks. Also check that the server compresses text files (Brotli or gzip). Finally, if a large share of visitors are far from your server, a CDN brings static files closer to them. For an audience mostly in the same region as your server, it is rarely the top priority.
```
# Check the compression and protocols advertised
curl -sI -H "Accept-Encoding: br, gzip" https://www.example.com/ | grep -i -E "content-encoding|alt-svc"
```
## Where should you start? The 15 actions ranked
Start with what gives the most for the least effort: page caching, images, plugins. Keep fine-tuning (critical CSS, delayed JavaScript) for last, once the basics are in place and measured.
| # | Action | Main metric improved | Effort |
| --- | --- | --- | --- |
| 1 | Hosting built for WordPress | TTFB, LCP | Switching hosts |
| 2 | Page caching | TTFB, LCP | Low |
| 3 | Recent PHP | TTFB | Low (test first) |
| 4 | Object cache | TTFB (dynamic pages) | Low if provided |
| 5 | Images compressed as WebP/AVIF | LCP | Low |
| 6 | LCP image prioritised, not lazy-loaded | LCP | Low |
| 7 | Image dimensions and reserved slots | CLS | Low to medium |
| 8 | Lightweight theme | LCP, INP | High (redesign) |
| 9 | Plugin audit | TTFB, INP | Medium |
| 10 | Minified, deferred CSS/JS | LCP, INP | Low to medium |
| 11 | Self-hosted fonts, font-display: swap | LCP, CLS | Medium |
| 12 | Fewer third-party scripts | INP, LCP | Medium |
| 13 | Clean database | TTFB (admin) | Low |
| 14 | Real cron job | Server load | Low |
| 15 | HTTP/3, compression, CDN if needed | LCP | Low to medium |
*The 15 actions and their main effect. How much you gain depends on your site: measure before and after.*
## How do you know your optimisations worked?
Repeat your baseline measurements on the same pages under the same conditions (mobile, private window, warm cache) and compare. For field data, wait four weeks and follow the Core Web Vitals report in Search Console, which groups your URLs by status.
Log every change with its date: if a metric gets worse, you will know what to roll back. To go further, WordPress’s official documentation on [performance optimisation](https://developer.wordpress.org/advanced-administration/performance/optimization/) and the [Chrome UX Report](https://developer.chrome.com/docs/crux) explain where the numbers come from.
## Hosting built for WordPress speed
Actions 1 to 4 and 15 depend largely on your host. At [Hosterwise](https://hosterwise.com/en/), every plan runs on LiteSpeed Enterprise servers with LSCache, a Redis object cache, HTTP/3 and free SSL certificates, which covers most of the server-side work. The Premium and Boost plans add CPU and memory for dynamic sites such as WooCommerce: compare them on our [pricing](https://hosterwise.com/en/pricing/) page or explore our [LiteSpeed WordPress hosting](https://hosterwise.com/en/litespeed-hosting/).
Is your site hosted elsewhere? We move it for you with our [free migration](https://hosterwise.com/en/free-migration/), using the method described in our guide to [migrating a WordPress site with zero downtime](https://hosterwise.com/en/blog/migrate-wordpress-site/).
## WordPress speed FAQ
### Why is my WordPress site slow?
The usual causes are overloaded hosting or no caching, heavy images, a theme or plugins that load lots of code, and third-party scripts. Start by measuring TTFB: above 0.8 seconds, look at the server and caching; below that, look at what the browser downloads.
### Which plugin should I use to speed up WordPress?
On a LiteSpeed server, LiteSpeed Cache is the logical choice, because it drives the server’s own cache and bundles most optimisations. On Apache or Nginx, choose one well-established caching plugin. Only run one: two active caching plugins get in each other’s way.
### Is a good PageSpeed score enough?
No. The lab score is a one-off diagnosis; Google mainly relies on field data (real visitors’ Core Web Vitals). A score of 100 achieved by delaying all JavaScript can hide poor real-world responsiveness. Aim for good Core Web Vitals rather than a number.
### Does the number of plugins slow WordPress down?
Not directly: a few badly built plugins weigh more than many lightweight ones. What matters is the code loaded on each page and the queries it runs. Query Monitor helps you spot the costly ones before deciding what to keep.
### Do I need a CDN for my WordPress site?
Not necessarily. If most visitors are in the same region as your server, a good server cache and optimised images do more than a CDN. A CDN becomes useful for an international audience or to absorb big traffic spikes.
### Can switching hosts really speed up a site?
Yes, when the server is the bottleneck: high TTFB even on cached pages, outdated PHP, no server-side cache. If TTFB is already good, gains will come from images, theme and scripts instead. Measure before you decide.
Share
- [Share on LinkedIn (new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
- [Share on X (new tab)](https://x.com/intent/post?url=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F&text=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work)
- [Send by e-mail](mailto:?subject=Speed%20Up%20WordPress%3A%2015%20Practical%20Actions%20That%20Work&body=https%3A%2F%2Fhosterwise.com%2Fen%2Fblog%2Fspeed-up-wordpress%2F)
## LiteSpeed WordPress hosting from 6,99 €/month
Starter, Premium or Boost: free SSL, automatic backups, free migration and a 30-day guarantee.
[Compare plans](https://hosterwise.com/en/pricing/)
About the author
## L’équipe Hosterwise
Hosterwise technical and support team
Written and reviewed by the Hosterwise technical team, who run LiteSpeed servers with CyberPanel every day and help customers migrate, secure and speed up their WordPress sites.
## Keep reading
[All articles](https://hosterwise.com/en/blog/)
[Performance](https://hosterwise.com/en/category/performance-en/)
### [LiteSpeed Cache Setup: Step-by-Step Settings for 2026](https://hosterwise.com/en/blog/litespeed-cache-setup/)
Set up LiteSpeed Cache for WordPress step by step: presets, caching, CSS/JS, images and WooCommerce. Settings checked against plugin version 7.9.
October 8, 202613 min read
[Performance](https://hosterwise.com/en/category/performance-en/)
### [LiteSpeed vs Nginx vs Apache: Which Web Server for WordPress?](https://hosterwise.com/en/blog/litespeed-vs-nginx-vs-apache-wordpress/)
LiteSpeed vs Nginx vs Apache for WordPress: architecture, .htaccess, caching, HTTP/3 and market share compared, plus which one to pick for your site.
October 13, 202611 min read
[Guides](https://hosterwise.com/en/category/guides-en/)
### [How Much Does WordPress Hosting Cost in 2026? Real Prices and Hidden Costs](https://hosterwise.com/en/blog/wordpress-hosting-cost/)
How much does WordPress hosting cost in 2026? Prices by hosting type, intro versus renewal pricing, four-year totals, hidden costs and budgets by project, based on public prices checked on 16 October 2026.
October 16, 202614 min read
---
Markdown version of