by
LNDLE
5 (1 reviews)
LNDLE Speed – Page Cache, WebP, Lazy Load & Performance
Page cache, WebP, lazy load, CSS/JS optimization and local Google Fonts for WordPress and Elementor, with a setup wizard.
LNDLE Speed ranks #33,057 among WordPress.org plugins with 10+ active installations, is #671 of 1,658 in the Performance category, a 5/5 rating from 1 reviews, and was last updated Oct 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v0.11.8
Current Version v0.11.8
Updated 3 weeks ago
Last Update on 15 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#671 of 1,658 in Performance
Top 50% by installs
Actively maintained
Rank
#33,057
—
No change
Active Installs
10+
—
No change
KW Avg Position
178
1.5 worse
Downloads
374
+2 today
Support Resolved
100%
—
No change
Rating
100%
Review 5 out of 5
5
(1 reviews)
Next Milestone 20
10+
20+
9,884
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 2 more installs to reach 20+
Rank Changes
Current
#33,057
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
1 reviews
Overall
100%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.11.8
- Last Updated
- Oct 15, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- LNDLE
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 1
- Support Threads
- 1
- Resolved
- 100%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#36
Speed Optimizer – The All-In-One Performance-Boosting Plugin
1M+ installs
#44
WP Fastest Cache – WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#59
Frequently Asked Questions
Common questions about LNDLE Speed – Page Cache, WebP, Lazy Load & Performance
Yes. The cache is cleared when you save Elementor templates or when Elementor regenerates its CSS files, and the Elementor preview is never cached or optimized. If Elementor prints its CSS inline, the setup wizard suggests switching the CSS print method to "External File", which works better with a page cache.
On activation and whenever you save the settings, LNDLE Speed writes the following: wp-content/advanced-cache.php – the WordPress drop-in that loads the cache engine before WordPress itself. If a drop-in from another caching plugin already exists and that plugin is still active, the file is not replaced; you get a notice and can replace it manually. The previous drop-in is then kept in the database and written back when LNDLE Speed is deactivated. wp-content/cache/lndle-speed/config.php – a generated configuration file for the cache engine, in the plugin's own cache directory. That directory denies direct access to PHP files. define( 'WP_CACHE', true ); // LNDLE Speed in wp-config.php. If WP_CACHE is already set to true, the file is left unchanged. An existing WP_CACHE line with another value is replaced. A block between # BEGIN LNDLE Speed and # END LNDLE Speed at the top of the .htaccess file in your site root, containing the rewrite rules for the page cache and, if enabled, the browser cache rules. The folder wp-content/cache/lndle-speed/ with the cached pages, the minified and combined CSS files and a small .htaccess file that sets the response headers for cached pages. One .webp file next to each converted image in wp-content/uploads/, named after the original (for example photo.jpg.webp), as long as WebP creation is switched on. The original files are not touched. When you deactivate the plugin, it removes its .htaccess block, its own advanced-cache.php (or restores the drop-in that was there before), the WP_CACHE line it added, the folder wp-content/cache/lndle-speed/ with the configuration file, and its scheduled events. When you delete the plugin, its options are removed from the database as well. The generated .webp files are deliberately kept: deleting them would be irreversible, and you can remove the uploads folder's .webp files yourself at any time. Not removed automatically: a WP_CACHE line that was already in wp-config.php before activation. Removal requires that the files are still writable at the time of deactivation.
Usually not. The setup wizard requests your home page and looks for response headers of a server-side page cache (for example Varnish, Nginx FastCGI cache or LiteSpeed) and of the Cloudflare HTML cache. If it finds one, it switches the page cache and the preload off in its recommendations so that pages are not cached twice. The other features – lazy load, image dimensions, CSS minification and the WordPress cleanup – can be used together with a server cache. In that case, clear the cache at your hosting provider after changing settings or content.
Switch on "Serve Google Fonts from this website" under "Files". When a page requests a stylesheet from fonts.googleapis.com, the plugin notes the address and downloads it in the background, together with the font files, into wp-content/uploads/lndle-speed-fonts/. From then on the page links to that local copy, and the preconnect to Google is removed. Visitors never connect to Google. The download needs an outgoing connection from your server to Google once per font set; if your host blocks that, the page keeps using the Google copy and nothing breaks. Fonts that a theme or plugin already hosts itself are not touched, and font files cannot be converted into another format by the plugin.
No. The plugin has no tracking, does not contact a license or update server and loads no external scripts or fonts. It makes HTTP requests to your own site only: the cache preload requests your sitemap and your pages so that they are cached, and the setup wizard fetches your home page from your browser to look for cache headers. Pages are only preloaded if they belong to your own domain. Sitemaps on other domains are ignored. The settings page contains links to the LNDLE Speed Pro page on lndle.media. They are plain links; nothing is loaded from there unless you click them.
JPEG and PNG files in the media library, including the sub-sizes WordPress creates. The WebP file is written next to the original and is only kept if it is actually smaller. Images that are already WebP, AVIF, SVG or GIF are left alone, and so are the original files – nothing is overwritten.
On Apache or LiteSpeed without a CDN in front of the site, the .htaccess rules are the better choice: they also cover background images in CSS and leave the HTML unchanged. On Nginx, or behind a CDN or server cache that may ignore the Vary: Accept header, use the picture element instead. The setup wizard makes a recommendation based on what it finds on your server, and you can switch at any time.
That is what the plugin is built for. The page cache cuts the server response time, which is what Time to First Byte measures. The hero image preload and the WebP delivery shorten the Largest Contentful Paint, because the browser finds the most important image earlier and downloads a smaller file. Adding the missing width and height to images prevents the layout shifts that Cumulative Layout Shift counts. Defer JavaScript and the combined, asynchronous stylesheets reduce the work the browser has to do before the first paint, which shows up in Interaction to Next Paint. How much each of them is worth depends on the site; the plugin measures nothing and promises no score.
It is built around Apache and LiteSpeed with .htaccess, and around Elementor sites. Cached pages are served by the web server itself, without starting WordPress. The setup wizard looks at the server, the installed plugins and the response headers before it recommends anything, instead of switching everything on at once. There is no account, no external service and no tracking.
Yes. Cart, checkout and the account pages are never cached, and visitors who have something in their cart are served uncached pages. The rest of the shop is cached as usual. Be careful with aggressive JavaScript settings on a shop and test the cart, the variations and the checkout after switching them on.
