Redis<\/a> is the standard choice. On Ubuntu:<\/p>\n\n\n\nsudo apt install redis-server php-redis\nsudo systemctl enable --now redis-server\nsudo systemctl restart php8.3-fpm # match your PHP version\n<\/code><\/pre>\n\n\n\nThen install the Redis Object Cache plugin and click Enable Object Cache<\/strong>. WooCommerce stores, membership sites and busy blogs see the biggest benefit.<\/p>\n\n\n\nFix 7: Put a CDN in front of your site<\/h3>\n\n\n\n
A content delivery network keeps copies of your images, CSS and JavaScript on servers around the world, so each visitor downloads them from somewhere nearby. If your audience is spread across countries, a CDN noticeably improves WordPress speed for distant visitors. Many CDNs can also cache full HTML pages at the edge, which takes even more load off your server. Set long browser cache lifetimes for static files while you’re at it, so returning visitors don’t download them again.<\/p>\n\n\n\n
Image Optimization for Faster Pages<\/h2>\n\n\n\n
Images are usually the heaviest part of a WordPress page, and the main image is often the LCP element. Good image optimization is one of the cheapest ways to improve WordPress speed.<\/p>\n\n\n\n
Fix 8: Compress images and serve WebP or AVIF<\/h3>\n\n\n\n
A photo straight from a phone can be 4 MB or more. Most web pages need it at under 200 KB. Image optimization has two parts:<\/p>\n\n\n\n
\n- Compress before or during upload.<\/strong> Plugins such as EWWW Image Optimizer, ShortPixel, Imagify or Smush compress new uploads automatically and can bulk-process your existing media library.<\/li>\n\n\n\n
- Use modern formats.<\/strong> WebP files are typically 25\u201335% smaller than JPEG at the same visual quality, and AVIF is smaller still. WordPress supports both formats, and most optimization plugins can create and serve them automatically.<\/li>\n<\/ul>\n\n\n\n
Run a bulk optimization once, then let the plugin handle new uploads.<\/p>\n\n\n\n
Fix 9: Size images correctly and lazy-load the rest<\/h3>\n\n\n\n
Uploading a 4000-pixel image to show it at 800 pixels wastes bandwidth on every visit. WordPress creates several sizes of each upload and uses srcset<\/code> so the browser picks a suitable one, but that only works if your theme uses those sizes. Resize huge originals before uploading, and don’t stretch small thumbnails into large slots.<\/p>\n\n\n\nWordPress lazy-loads images below the fold by default, so they load only when a visitor scrolls near them. One important exception: don’t lazy-load your LCP image<\/strong>. The hero image at the top of the page should load immediately, ideally with fetchpriority=\"high\"<\/code>. Lazy-loading it is one of the most common causes of a poor LCP score. Always set width and height on images too, so the browser reserves space and the layout doesn’t jump, which keeps CLS low.<\/p>\n\n\n\nFront-End Fixes for Render-Blocking Files<\/h2>\n\n\n\n
Even with a fast server and light images, WordPress speed can still suffer while the browser sits waiting on CSS and JavaScript before it shows anything. These fixes clear that path.<\/p>\n\n\n\n
Fix 10: Remove render-blocking CSS and JavaScript<\/h3>\n\n\n\n
When the browser meets a script or stylesheet in the page head, it usually stops rendering until that file downloads and runs. Too many of them delay everything the visitor sees.<\/p>\n\n\n\n
\n- Defer non-critical JavaScript<\/strong> so it runs after the page renders. Analytics, chat widgets and social embeds rarely need to load first.<\/li>\n\n\n\n
- Delay third-party scripts<\/strong> until the visitor interacts with the page. This also improves INP, because less JavaScript competes for the main thread.<\/li>\n\n\n\n
- Remove unused CSS.<\/strong> Page builders and big themes load styles for features you never use.<\/li>\n\n\n\n
- Minify<\/strong> CSS and JavaScript to strip whitespace and comments.<\/li>\n<\/ul>\n\n\n\n
Plugins such as Autoptimize, Perfmatters, or the optimization features in your caching plugin handle most of this. Change one setting at a time and check the site afterwards, because aggressive deferring can break sliders, menus or forms.<\/p>\n\n\n\n
Fix 11: Host fonts locally and load fewer of them<\/h3>\n\n\n\n
Web fonts are easy to overdo. Each family, weight and style is a separate download, and loading them from an external service adds extra connections. Pick one or two families and only the weights you actually use, often regular and bold. Host the font files on your own server, preload the main one, and use font-display: swap<\/code> so text appears immediately in a fallback font instead of staying invisible.<\/p>\n\n\n\nBack-End Cleanup: Plugins, Database and WP-Cron<\/h2>\n\n\n\n
The last three fixes protect your WordPress speed by reducing the work WordPress does on every uncached request and in the background.<\/p>\n\n\n\n
Fix 12: Audit your plugins and theme<\/h3>\n\n\n\n
The number of plugins matters less than what each one does. One badly built plugin can add more load than twenty well-built ones. Use the Query Monitor plugin to see which plugins add the most database queries and PHP time on a page. Then ask, for each plugin, whether you still need it, and whether a lighter plugin or a few lines of code could do the same job. Deactivate and delete what you don’t use.<\/p>\n\n\n\n
Your theme matters just as much. Multipurpose themes that load sliders, animations and dozens of scripts on every page are a common cause of poor WordPress speed. A lightweight theme, or a block theme built for the Site Editor, starts from a much faster base.<\/p>\n\n\n\n
Fix 13: Clean up the database<\/h3>\n\n\n\n
Over time, the WordPress database collects post revisions, trashed items, spam comments and expired transients. The biggest hidden problem is usually autoloaded options<\/strong>: settings that WordPress loads on every single request. Abandoned plugins often leave large autoloaded data behind.<\/p>\n\n\n\nWith WP-CLI, you can clean up safely from the command line:<\/p>\n\n\n\n
wp post delete $(wp post list --post_type=revision --format=ids) --force\nwp transient delete --expired\nwp db optimize\n<\/code><\/pre>\n\n\n\nYou can also limit future revisions by adding define( 'WP_POST_REVISIONS', 5 );<\/code> to wp-config.php<\/code>. Always take a backup before cleaning the database. Plugins such as WP-Optimize do the same job from the dashboard.<\/p>\n\n\n\nFix 14: Replace WP-Cron with a real cron job<\/h3>\n\n\n\n
WP-Cron runs scheduled tasks, such as publishing scheduled posts, sending emails and running backups, by checking on page loads. On a busy site, that adds overhead to visitor requests. On a quiet site, tasks run late. Disable it in wp-config.php<\/code>:<\/p>\n\n\n\ndefine( 'DISABLE_WP_CRON', true );\n<\/code><\/pre>\n\n\n\nThen add a real system cron job that runs every five minutes:<\/p>\n\n\n\n
*\/5 * * * * cd \/var\/www\/example.com && wp cron event run --due-now >\/dev\/null 2>&1\n<\/code><\/pre>\n\n\n\nIf your site uses a page builder or WooCommerce, also consider reducing the WordPress Heartbeat frequency in the admin, which polls the server every 15 to 60 seconds while editors are open.<\/p>\n\n\n\n
Common WordPress Speed Mistakes to Avoid<\/h2>\n\n\n\n
A few habits undo good optimization work. Watch out for these:<\/p>\n\n\n\n
\n- Stacking optimization plugins.<\/strong> Two caching plugins, or a caching plugin plus a separate minifier with the same features, often conflict. Pick one tool per job.<\/li>\n\n\n\n
- Chasing a perfect 100 score.<\/strong> A score of 90 with good Core Web Vitals and a fast real-world experience is a great result. The last few points rarely change anything for visitors.<\/li>\n\n\n\n
- Testing only the homepage.<\/strong> Your blog posts, product pages and checkout often load completely different scripts.<\/li>\n\n\n\n
- Optimizing without a backup.<\/strong> Database cleanups and script deferring can break things. Take a backup or test on staging first.<\/li>\n\n\n\n
- Ignoring mobile.<\/strong> PageSpeed Insights reports mobile and desktop separately, and Google mainly uses the mobile version of your site.<\/li>\n<\/ul>\n\n\n\n
Frequently Asked Questions<\/h2>\n\n\n\nHow do I check my WordPress speed?<\/h3>\n\n\n\n
Run your homepage and a typical inner page through PageSpeed Insights and note the Core Web Vitals, TTFB and total page weight. Repeat each test three times and use the middle result, then test again after each change.<\/p>\n\n\n\n
Which single fix improves WordPress speed the most?<\/h3>\n\n\n\n
For most sites, page caching. It turns every repeat visit into a ready-made page instead of a full PHP and database run, often cutting server response time by 80% or more. If your hosting is overloaded, though, moving to faster hosting comes first.<\/p>\n\n\n\n
Do I need a plugin for image optimization?<\/h3>\n\n\n\n
You don’t strictly need one, because you can compress and convert images before uploading them. A plugin is easier, though, because it handles every new upload automatically and can convert your existing media library to WebP or AVIF in one pass.<\/p>\n\n\n\n
Will page caching break my WooCommerce store?<\/h3>\n\n\n\n
Not if it’s configured correctly. Good caching plugins exclude the cart, checkout and account pages automatically. With server-level page caching, you add those exclusions yourself, along with a rule to skip the cache for logged-in users.<\/p>\n\n\n\n
How often should I repeat this process?<\/h3>\n\n\n\n
Re-test your WordPress speed after installing a new plugin, changing themes or making big design changes, and do a quick check once a quarter. Speed tends to drift downwards as a site grows, so small regular checks beat one big cleanup a year.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Learning how to speed up a WordPress website is mostly about doing the right things in the right order. Measure first, so you know your baseline and your Core Web Vitals. Fix the server, so TTFB is low. Add page caching and an object cache, so most requests never touch PHP or the database. Then trim the weight with image optimization, clear render-blocking files, and clean up plugins, the database and WP-Cron.<\/p>\n\n\n\n
You don’t need all 14 fixes to see a difference. The first five alone often turn a sluggish site into a fast one. Work through the list, re-test after each change, and keep the changes that move your numbers.<\/p>\n\n\n\n
If you’re running WordPress on your own server, start with our guide to installing WordPress on an Ubuntu VPS with Nginx<\/a>, then apply these fixes on top. For a deeper look at server tuning, the WordPress performance documentation<\/a> is a useful next step. And if your current host is what’s holding you back, a NodeGuard Cloud VPS<\/a> gives you NVMe storage and full control to apply every fix in this guide.<\/p>\n\n\n\n
\n","protected":false},"excerpt":{"rendered":"A slow site costs you visitors, sales and search rankings, and most of the time the cause is fixable in an afternoon.\u2026<\/p>\n","protected":false},"author":2,"featured_media":200,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[105,106,90,103,107,104,100,102],"class_list":["post-198","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-core-web-vitals","tag-image-optimization","tag-nginx","tag-page-caching","tag-performance","tag-redis","tag-wordpress","tag-wordpress-speed"],"_links":{"self":[{"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/posts\/198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/comments?post=198"}],"version-history":[{"count":4,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/posts\/198\/revisions"}],"predecessor-version":[{"id":207,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/posts\/198\/revisions\/207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/media\/200"}],"wp:attachment":[{"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/media?parent=198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/categories?post=198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nodeguard.io\/blog\/wp-json\/wp\/v2\/tags?post=198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"How](\"https:\/\/nodeguard.io\/blog\/wp-content\/uploads\/2026\/10\/speed-up-wordpress-load-time-1024x576.webp\")
![\"WordPress](\"https:\/\/nodeguard.io\/blog\/wp-content\/uploads\/2026\/10\/speed-up-wordpress-caching-layers-1024x576.webp\")