LNDLE Speed – Page Cache, WebP, Lazy Load & Performance

FAQ

Does it work with Elementor?

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.

What does the plugin write to my server?

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.

My host already has a server cache. Do I still need the page cache?

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.

How does serving Google Fonts locally work?

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.

Does the plugin send data anywhere?

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.

Which images are converted to WebP?

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.

Which WebP delivery method should I choose?

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.

Does it improve the Core Web Vitals?

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.

How is this different from the other caching plugins?

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.

Does it work with WooCommerce?

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.

Can I use it together with Cloudflare or another CDN?

Yes. The setup wizard detects Cloudflare and other proxy caches and adapts its recommendations, for example by suggesting the picture element for WebP instead of the .htaccess rules, because a CDN in front of the site may ignore the Vary: Accept header. After changing settings or content, the cache at the CDN has to be cleared separately; the plugin cannot do that for you.

Does it support Multisite?

No. Multisite networks are not supported, and the setup wizard shows a warning when it detects one.

Does it work on Nginx?

Partly. Without .htaccess, cached pages are served through PHP instead of directly by the web server, which is slower than on Apache or LiteSpeed, and the browser cache rules have no effect. The setup wizard tells you which web server it found.

My staging site is password protected. Why does the preload not work?

With HTTP basic authentication in front of the site, the preload receives a 401 response. Add define( 'LNDLE_SPEED_HTTP_AUTH', 'user:password' ); to wp-config.php so that the preload and WP-Cron requests can authenticate.

How do I check a page without the cache?

Append ?nolndlespeed to the URL to bypass cache and optimization for a single request. Append ?lndle-speed-guest to see the page as a visitor would, with all optimizations, while you are logged in.

How do I exclude an image from lazy load?

Add the class skip-lazy or the attribute data-no-lazy to the image, or enter part of the file name or class under “Lazy load exclusions”.

Is the database cleanup reversible?

No. Revisions, auto-drafts, trashed items and spam are deleted permanently. Create a backup first.