Публикувано: Обновено:
With every additional second of waiting, the bounce rate rises by 32 %, and once loading time exceeds three seconds, 53 % of mobile users leave before seeing anything at all. The average desktop load time in 2026 is 2.5 seconds, but on mobile devices it reaches 8.6 seconds, far from what users expect. Only 33 % of sites meet all three Core Web Vitals metrics at the same time.
This is where a speed plugin comes in: it automates caching, minification, lazy loading and image optimisation so that you can reach the thresholds Google requires. In this article, the CreateWeb team compares the three leading solutions, WP Rocket, LiteSpeed Cache and FlyingPress, with real features, prices and specific recommendations on which plugin suits which type of hosting.
This article is the last in our series on WordPress plugins, following the guides to SEO plugins, backup plugins and security plugins. We also introduce the WordPress Speed Optimization Stack, a 5-layer framework from Page Cache to Network & Edge.
What is caching and why does every WordPress site need it?
Caching is a mechanism by which the server stores a ready-made copy of the HTML page instead of generating it afresh on every visit. Without a cache, WordPress runs dozens of PHP requests and MySQL calls for every page, a process that loads the processor and lengthens response time. With caching enabled, this cycle disappears: the user receives a static HTML file in milliseconds.
There are four main types of caching, which plugins cover to varying degrees. Page cache is the most important: it creates an HTML copy of each page and serves it without touching PHP. Browser cache instructs the visitor’s browser to store static resources (CSS, JS, images) locally, so that they are not downloaded again on a repeat visit. Object cache stores database results in RAM (Redis or Memcached) and is critical for WooCommerce and dynamic sites. CDN cache distributes copies of the content across dozens of locations around the world and reduces latency for users far from the origin server.
Without the right caching strategy, even quality web hosting cannot compensate for the load of an uncached WordPress site.
WordPress Speed Optimization Stack: a framework for layered optimisation
One of the most common mistakes with speed is treating it as a one-off task: “I installed a caching plugin, job done”. Real optimisation is layered: each layer solves a different problem, and without all five nothing works at full capacity. This framework, which we call the WordPress Speed Optimization Stack, organises optimisation into 5 layers, from Page Cache (the biggest impact, the foundation) to Network & Edge (fine-tuning for global traffic).
| Level | What it covers | Impact on CWV |
|---|---|---|
| Level 1 – Page Cache | HTML copy, preloading, server-level cache | LCP -50 to -80 % |
| Level 2 – Asset Optimization | Minification, Remove Unused CSS, defer JS | INP, render-blocking |
| Level 3 – Media Optimization | WebP/AVIF, lazy load, width/height attributes | LCP, CLS |
| Level 4 – Object & Database | Redis/Memcached, DB cleanup | TTFB, dynamic pages |
| Level 5 – Network & Edge | CDN, browser cache, edge computing | Global latency |
The principle of the stack: you work from the bottom up, and each layer builds on the previous one. Page Cache (Level 1) delivers the biggest one-off jump (usually a 50-80 % improvement in LCP). Asset Optimization (Level 2) eliminates render-blocking resources. Media Optimization (Level 3) reduces page weight by 40-80 %. Object & Database (Level 4) is critical for dynamic sites and WooCommerce. Network & Edge (Level 5) serves a global audience.
Applying the framework: assess which layer is causing you the biggest problems. Slow TTFB on dynamic pages? Level 4 (Object cache). High LCP with heavy images? Level 3 (Media Optimization). Poor INP with lots of JavaScript? Level 2 (Asset Optimization). A global audience with high latency? Level 5 (CDN). Skipping Level 1 (Page Cache), however, is a mistake: without it, everything else runs at 30 % capacity.
Core Web Vitals: what exactly you are measuring
Google assesses three metrics, defined in the official Core Web Vitals documentation on web.dev: LCP (Largest Contentful Paint) should be under 2.5 seconds and shows how quickly the main visual element loads; INP (Interaction to Next Paint) should be under 200 milliseconds and measures responsiveness to a click or input; CLS (Cumulative Layout Shift) should be under 0.1 and detects unwanted movement of elements during loading. Improving LCP by one second can increase conversions by up to 27 %. A page that loads in 3.3 seconds achieves an average conversion rate of 4.75 %, a figure that drops sharply with every additional second of delay.
A speed plugin directly affects all three metrics: page cache and preloading improve LCP, deferred JavaScript loading reduces INP, and correct lazy loading and set image dimensions keep CLS under control. Without a plugin, achieving green scores in PageSpeed Insights requires manual changes to the code, something most site owners cannot afford. We have a dedicated guide on Core Web Vitals optimisation.
WP Rocket: the easiest paid plugin
WP Rocket is a premium plugin with no free version. Prices start at $59 a year for one site, $119 for three sites and $299 for fifty. Simplicity is its main advantage: once activated, page caching works immediately without configuration.
Its features include page cache with preloading, lazy load for images and videos, minification and combining of CSS and JS files, Remove Unused CSS, Delay JavaScript Execution, database optimisation (clearing revisions, transients, spam comments), CDN integration and CNAME support. WP Rocket has no built-in image optimisation; for that you use Imagify, made by the same team, or ShortPixel.
WP Rocket works on any type of server: Apache, Nginx, LiteSpeed. Its setup follows the “80/20” rule: 20 % of the effort achieves 80 % of the possible result. The interface is intuitive, every option has an explanation, and compatibility with popular themes and plugins is high. Its weaknesses are that it is entirely paid and that Remove Unused CSS sometimes requires manual exclusions with more complex themes.
WP Rocket is the choice when the client has no technical person for maintenance. The default settings give good results, and manual settings require minimal expertise. For agencies and freelancers managing multiple client sites, the 50-site licence ($299) is a sensible investment compared with manually configuring free alternatives on each one.
LiteSpeed Cache: free power on the right server
LiteSpeed Cache is a free plugin with over 6 million active installations (WordPress.org). Its real strength shows on a LiteSpeed server, where caching works at server level, directly in memory, without going through PHP. On Apache or Nginx the plugin still works, but loses the advantage of server-level cache and relies on file caching alone.
Its features go beyond ordinary caching: built-in image optimisation (WebP and AVIF) through the free QUIC.cloud service, Critical CSS generation, Object cache (Redis, Memcached), browser cache, lazy load, minification, combining CSS/JS, DNS prefetch, HTTP/2 push, database cleanup and CDN integration through QUIC.cloud. On a LiteSpeed server, the plugin is the fastest solution you can install on WordPress: nothing else can compete with a server-level cache executed in C++ instead of PHP.
Its weaknesses are that its full potential requires a LiteSpeed server, and QUIC.cloud’s free plan has limits on image optimisation. The interface is more complex than WP Rocket’s, with dozens of options that can confuse a beginner. Nevertheless, its value for money is unbeatable: the plugin is completely free.
FlyingPress: the balance between efficiency and control
FlyingPress is a newer premium plugin priced from $49 a year for one site. It stands out for the most aggressive implementation of Remove Unused CSS: the plugin analyses each page individually and loads only the CSS actually used on it. Other plugins do this at a more general level.
Additional features include page cache, preload links (it loads the next likely page on hover), self-hosted Google Fonts (eliminating external DNS requests), lazy load, minification, defer and delay of JavaScript, and database cleanup. FlyingPress has no built-in image optimisation and is combined with ShortPixel or EWWW Image Optimizer.
FlyingPress works on Apache, Nginx and LiteSpeed. The interface is clean and well organised, and the documentation is detailed. The plugin is more effective than WP Rocket at Remove Unused CSS and preload links, but it does not have as broad a community and has fewer resources for troubleshooting compatibility issues.
Comparison table: the 3 plugins side by side
| Feature | WP Rocket | LiteSpeed Cache | FlyingPress |
|---|---|---|---|
| Page cache | Yes | Yes (server-level on LS) | Yes |
| Browser cache | Yes | Yes | Yes |
| Object cache | No (add-on) | Yes (Redis, Memcached) | No |
| Remove Unused CSS | Yes | Yes (UCSS via QUIC.cloud) | Yes (most aggressive) |
| Delay JavaScript | Yes | Yes | Yes |
| Lazy load | Yes | Yes | Yes |
| Image optimization | No (Imagify separately) | Yes (WebP/AVIF, QUIC.cloud) | No (ShortPixel separately) |
| Critical CSS | Yes | Yes | Yes |
| Preload links | No | No | Yes |
| Self-hosted fonts | No | No | Yes |
| CDN integration | Yes | Yes (QUIC.cloud) | Yes |
| DB cleanup | Yes | Yes | Yes |
| Supported servers | Apache, Nginx, LS | All (full on LS) | Apache, Nginx, LS |
| Price | $59/year (1 site) | Free | $49/year (1 site) |
| Active installations | 4 000 000+ | 6 000 000+ | ~50 000 |
Image optimisation: an integral part of speed
Images account for an average of 40-80 % of a page’s weight. The WebP format is 25-30 % smaller than JPEG, and AVIF reduces size by a further 20 %. LiteSpeed Cache has built-in conversion and optimisation, enabled from the panel and run through QUIC.cloud. WP Rocket relies on Imagify (free plan up to 20 MB a month, Premium from $9.99/month), while FlyingPress relies on ShortPixel (100 free images/month, plans from $3.99/month) or EWWW.
The right strategy includes: converting to WebP or AVIF, compressing without visible loss of quality (lossy with a high Quality setting), setting width and height attributes to prevent CLS, and lazy loading all images below the “fold” (above-the-fold elements are never lazy-loaded, because that hurts LCP).
This is Level 3 (Media Optimization) of the WordPress Speed Optimization Stack, and it often delivers the biggest one-off gain on sites with rich visual content.
Concrete figures on image weight
Real data from the audits we carry out shows a surprisingly consistent pattern. A typical unoptimised site has a hero image of 800 KB to 2.5 MB (PNG or uncompressed JPEG). The same image after proper optimisation (WebP, Quality 80, correct resolution) becomes 80-200 KB. That is a 75-90 % reduction for a single file. When this optimisation is applied to all images, the total weight of the homepage often drops from 5-8 MB to 1-2 MB.
Size directly affects LCP, because the hero image is usually the LCP element. On a 3G/4G network, the difference between an 800 KB and a 200 KB image is several seconds. This is why image optimisation (Level 3) often has a greater effect on Core Web Vitals than caching itself (Level 1), especially on media-heavy sites.
Responsive images (srcset)
A further optimisation is serving different sizes depending on the device using the srcset attribute. A desktop user gets a 1920px image, a mobile user a 480px one. WordPress 4.4+ generates srcset automatically, but plugins refine the process. On mobile devices this can save a further 60-80 % of image weight, a direct benefit for the 53 % of users who leave when mobile loading is slow.
Which plugin CreateWeb chooses and why
When carrying out website development, our team chooses the plugin according to the client’s hosting. If the site is on a LiteSpeed server, we install LiteSpeed Cache: it is free, works at server level and includes built-in image optimisation. If the server is Apache or Nginx, we choose FlyingPress for projects where speed is critical (e-commerce, high-traffic landing pages), or WP Rocket for clients who want maximum simplicity in future management.
Our process includes: installing the plugin and enabling page cache (Level 1); setting up preloading for all published URLs; enabling lazy load for images and iframes (except above the fold); minifying CSS and JS files, testing after every change (Level 2); enabling Remove Unused CSS with manual exclusions where needed; setting up image optimisation (Level 3, built in with LiteSpeed, Imagify or ShortPixel with the others); self-hosted Google Fonts (with FlyingPress) or serving fonts locally through the theme/child theme; disabling unnecessary WordPress features (emojis, embeds, XML-RPC, dashicons on the front end); and testing with PageSpeed Insights, GTmetrix and the Chrome UX Report.
As part of WordPress site maintenance, we monitor Core Web Vitals monthly and adjust settings when content changes or new features are added.
Speed and SEO: why caching is not just a technical task
Google confirms that Core Web Vitals are a ranking signal. A slow site not only loses rankings but also real money: 53 % of mobile users leave when loading takes more than 3 seconds, and every second of improvement increases conversions. A well-optimised site also supports SEO web design and conversion optimisation: speed improves bounce rate, time on site and crawl budget (Google crawls more pages per unit of time). We have a separate guide on the technical SEO structure that underpins these optimisations.
WordPress site owners wondering how much a WordPress site costs should bear in mind that $49-59 a year for a caching plugin pays for itself many times over through improved rankings and conversions.
Common mistakes when setting up a speed plugin
The first and most dangerous mistake is installing two caching plugins at the same time: WP Rocket and LiteSpeed Cache, or WP Rocket and W3 Total Cache. The plugins conflict, generate a double cache and the site becomes slower or stops working.
The second mistake is overly aggressive minification and combining of CSS/JS files. If JavaScript is combined without the right exclusions, interactive elements (menus, sliders, the WooCommerce basket) stop working. The right approach is to enable one feature at a time and test after every change.
The third mistake is lazy loading above-the-fold images: the hero image, the logo, the banner. Lazy load delays the rendering of these elements and worsens LCP. They should be excluded from lazy load and given fetchpriority=”high”.
The fourth mistake is not optimising images. A caching plugin speeds up delivery, but if each image is 3 MB, the site will still be slow. The combination of caching + image optimisation is essential.
The fifth mistake is not using a CDN for international traffic. Without a CDN, a user in Germany loads the site from a server in Sofia, and the latency is significant. This is Level 5 (Network & Edge) of the Speed Optimization Stack.
WooCommerce and caching: special requirements
Online shops have dynamic content: the basket, stock levels, the user profile. The caching plugin must exclude the cart, checkout and my-account pages from page cache. WP Rocket does this automatically. LiteSpeed Cache and FlyingPress require exclusions to be added manually.
For WooCommerce, Object cache (Redis) is critically important: product queries to the database are heavy, and Redis serves them from memory. This is Level 4 of the WordPress Speed Optimization Stack. LiteSpeed Cache has built-in support. For WP Rocket and FlyingPress, a separate Redis Object Cache plugin is installed. If you are planning an e-commerce site, choosing the right hosting with Redis is as important as choosing the caching plugin.
Besides Redis, fragment caching is critical for WooCommerce: caching individual parts of the page (such as a mini-basket in the header) while the rest of the page is served normally. This is the difference between a site that feels fast and one that “thinks” on every click. Configuring it requires technical expertise, because incorrect exclusion rules can lead to the wrong basket being shown to the wrong user, a fatal UX problem for a shop.
Free or paid: when the investment is worth it
LiteSpeed Cache is free and fully featured; on a LiteSpeed server you need nothing else. If your hosting runs on LiteSpeed and offers Redis, you get enterprise-grade optimisation at zero cost for the plugin.
WP Rocket at $59 a year and FlyingPress at $49 a year pay for themselves in the following scenarios: your hosting is not on a LiteSpeed server; you want Remove Unused CSS and Delay JavaScript without manual coding; you have no technical person for maintenance; the site generates revenue (e-commerce, lead generation, ads), where even a 1 % improvement in conversion covers the $59 in the first month.
Trends for 2026
The AVIF format is gaining momentum and is expected to replace WebP as the standard for web images, with browser support already above 90 %.
The Speculation Rules API (the successor to prerender) allows the browser to load the next page before the click; FlyingPress already supports it, and WP Rocket and LiteSpeed Cache are adding it.
Edge computing (Cloudflare Workers, QUIC.cloud CDN) moves caching logic closer to the user.
AI automation in plugins: AI-based Critical CSS detection and resource prioritisation are expected to become standard.
Frequently asked questions
What is caching and why does it matter?
Caching is a process in which ready-made copies of web pages are saved and served directly, without the server generating the content afresh for every request. This reduces loading time by 40-80 % and improves Core Web Vitals, a direct SEO ranking factor.
What is the best WordPress speed plugin in 2026?
It depends on your hosting. On a LiteSpeed server, LiteSpeed Cache is the undisputed leader: it is free and works at server level. On Apache or Nginx, FlyingPress offers the most aggressive optimisation for $49/year, while WP Rocket ($59/year) is the easiest to set up without technical knowledge.
WP Rocket or LiteSpeed Cache – which should I choose?
If your hosting runs on a LiteSpeed server, LiteSpeed Cache is faster and free. If you are on Apache or Nginx, WP Rocket is a solid paid alternative that is easy to set up. Do not combine the two plugins, as they conflict.
What is the WordPress Speed Optimization Stack and how do you apply it?
It is a 5-layer framework for layered speed optimisation: Level 1 Page Cache (HTML copy, preloading), Level 2 Asset Optimization (minification, Remove Unused CSS, defer JS), Level 3 Media Optimization (WebP/AVIF, lazy load, dimensions), Level 4 Object & Database (Redis, DB cleanup) and Level 5 Network & Edge (CDN, browser cache). The principle: you work from the bottom up, and each layer builds on the previous one. Page Cache (Level 1) delivers the biggest one-off jump, a 50-80 % improvement in LCP.
Do I need a separate image optimisation plugin?
LiteSpeed Cache has built-in optimisation (WebP/AVIF) through QUIC.cloud. WP Rocket and FlyingPress do not; for them you use Imagify, ShortPixel or EWWW Image Optimizer. Optimised images reduce a site’s weight by 40-80 %.
What are the Core Web Vitals thresholds for 2026?
LCP (Largest Contentful Paint) under 2.5 seconds, INP (Interaction to Next Paint) under 200 ms and CLS (Cumulative Layout Shift) under 0.1. Only around 33 % of sites meet all three metrics.
Does CreateWeb optimise site speed?
Yes. We install and configure a suitable caching plugin, optimise images, set up lazy loading, minification, critical CSS and self-hosted fonts, and test the results with PageSpeed Insights and GTmetrix. See our portfolio for examples.
Conclusion: speed is a baseline, not an option
Speed is not an option but a baseline. Without caching and image optimisation, WordPress cannot meet Core Web Vitals, and Google states clearly that they affect rankings.
The WordPress Speed Optimization Stack in this article provides a clear structure: Level 1 Page Cache (the foundation, the biggest impact), Level 2 Asset Optimization (minification, defer JS), Level 3 Media Optimization (WebP/AVIF, lazy load), Level 4 Object & Database (Redis for dynamic sites) and Level 5 Network & Edge (CDN, edge computing). The principle: you work from the bottom up, and each layer builds on the previous one.
Choose a plugin according to your hosting: LiteSpeed Cache for LiteSpeed servers (free, server-level), FlyingPress for maximum efficiency on Apache/Nginx ($49/year), WP Rocket for easy setup without technical knowledge ($59/year). Configure it properly, test and maintain it: speed is not a one-off task but an ongoing process.
If you want a site that is fast from day one, discuss your project with us: we will apply the WordPress Speed Optimization Stack to your specific project and choose the right plugin for your hosting.
Related in-depth resources: our main article on WordPress plugins, SEO plugins, backup plugins, security plugins, Core Web Vitals for WordPress, quality web hosting, SEO web design, conversion optimisation, WordPress site cost, technical SEO, our main article on SEO, online shop, WordPress as a platform, website development, website maintenance.
If you would like a team to handle this for you, see our technical website analysis service.
