FastLayer

By kanhajatthap

★ 5.0/5 (2 ratings)0+ active installationsVersion 1.6.0

FastLayer speeds up WordPress with page caching, CSS/JS optimization, WebP images, lazy loading, optional ImageKit CDN and database cleanup.

Description

FastLayer is a performance plugin that brings page caching, code optimization, image delivery and database cleanup together under one FastLayer menu in the WordPress admin. Instead of installing and tuning several single-purpose plugins, you enable only the tools you need from one place.

It is built for typical WordPress sites, such as blogs, business sites and WooCommerce stores. Every feature is off by default and can be switched on independently, and FastLayer only writes to files it created itself, so it will not overwrite another plugin’s cache drop-in or configuration line.

Everything is off by default. Turn on one feature at a time and check the front end after each change, so you always know what made the difference.

Highlights

  • Page caching that serves static HTML to anonymous visitors, with optional background preloading.
  • Asset optimization for HTML, CSS and JavaScript: minify, combine, defer and delay.
  • Image optimization with WebP conversion and responsive delivery.
  • Lazy loading for images, iframes and videos, with low-quality image placeholders.
  • Optional ImageKit CDN for image delivery, using an endpoint you control.
  • Database cleanup for revisions, transients and orphaned metadata.

Features

Every tool has its own settings screen and can be enabled independently.

Page caching and cache preloading

Caches anonymous page views as static HTML and refills the cache automatically after a clear.

  • Cache lifetime: cached pages are kept for a set time (1 to 720 hours) and cleared automatically after that.
  • Automatic preloading: after a cache clear, pages are warmed in background batches so visitors are less likely to hit a cold cache.
  • Page discovery: preloading reads your XML sitemap (the WordPress core sitemap, Yoast SEO or All in One SEO), with built-in limits so a large or slow sitemap cannot stall the job. It can also be started manually at any time.
  • Manual control: clear everything from the FastLayer admin-bar menu or the Dashboard.
  • Never cached: logged-in users, the admin area, AJAX and REST requests, previews, 404 pages, search results, and POST or HEAD requests.

HTML, CSS and JavaScript optimization

Reduces page weight and render-blocking requests. Each option can be enabled separately.

  • HTML: minifies markup by removing comments and collapsing extra whitespace, with an option to keep Gutenberg block comments so block markup stays intact.
  • Minify: shrinks CSS and JavaScript files and can remove comments.
  • Combine: merges stylesheets and scripts to reduce requests while preserving media-specific styles.
  • CSS delivery: loads styles without blocking rendering, with a custom critical CSS box, a one-click sample generator, Smart Gutenberg CSS optimization and display=swap for Google Fonts.
  • JavaScript loading: defers and/or async-loads eligible scripts.
  • Smart JS Delay: waits for the first user interaction before running eligible non-critical scripts, then restores them after a configurable timeout so nothing is left unloaded.
  • Safety controls: Safe Mode and exclusion lists (by handle, keyword or pattern) keep chosen scripts untouched.

Image optimization, WebP and lazy loading

Generates lighter image files and defers media that is off screen.

  • WebP conversion: converts JPEG and PNG attachments to WebP, either automatically on upload or in resumable batches for images that already exist.
  • Responsive delivery: serves optimized responsive sizes and WebP variants.
  • Lazy loading: defers images, iframes (YouTube, Vimeo and others) and HTML5 videos.
  • LQIP: progressive loading with low-quality image placeholders, including placeholder width, quality, blur strength and fade duration controls.
  • Smart LCP: prioritizes one above-the-fold hero image or background without disabling lazy loading everywhere, with optional preload hints, hero background support and debug logging.

CDN and optional ImageKit integration

Serves assets and images from a host outside your server, or keeps everything on your own domain.

  • Custom CDN: rewrites internal asset URLs to a CDN hostname you configure.
  • ImageKit: optionally delivers images through ImageKit. Only your ImageKit endpoint is stored; no API keys are requested or saved. See External Services for exactly what is sent, and by whom.

Database cleanup

Removes unused rows and optimizes tables, showing counts before anything is deleted.

  • Tables: optimizes database tables.
  • Posts: removes post revisions, trashed posts, spam comments and auto-drafts.
  • Transients and cache: removes expired or all transients, and oEmbed cache rows.
  • Orphaned data: removes duplicate or orphaned post, comment, user and term metadata.
  • Safety: item counts are shown before cleaning, and a Clean All control selects every option at once.

Exclusions and diagnostics

Keeps FastLayer away from anything that must stay untouched, and explains cache decisions when something looks wrong.

  • Cache exclusions: exclude URLs, cookies and user agents from caching.
  • Asset exclusions: exclude individual CSS and JS files by path, pattern or external domain.
  • Debug Mode: records cache decisions (hit, miss and the exact skip reason) for the Dashboard debug panel, plus Smart LCP and Smart JS Delay activity. Off by default so it never costs a database write per page view.
  • Admin-bar actions: Clear All Cache, Clear CSS/JS Cache and Preload Cache.

Compatibility

FastLayer is built to sit alongside the plugins and themes you already run.

Run one page-cache engine and one minify engine per site. Two plugins doing the same job can produce conflicting output.

  • Page builders and e-commerce: Smart JS Delay keeps critical dependencies, Elementor and WooCommerce checkout/cart, and navigation scripts running immediately; exclusions and Safe Mode cover anything left over.
  • Servers: Apache and LiteSpeed apply the .htaccess rules directly, while nginx needs a manual server-level WebP rule. Page caching and asset optimization work on nginx, and FastLayer shows an admin notice with guidance when it detects nginx.
  • Multisite: not currently supported.

Troubleshooting

Start here when something does not look right, and change one option at a time.

My changes are not showing on the front end

FastLayer clears its cache automatically when posts, comments, terms or the active theme change. If you are also running a server, CDN or second caching layer, that layer may still be serving an older copy. Clear the FastLayer cache from the admin bar, then clear your CDN or server cache as well.

Styles or scripts break after I enable optimization

Turn the feature off, then re-enable options one at a time to find the cause. Add the affected files to the exclude list on the CSS or JavaScript screen. For JavaScript, enable Safe Mode or use Smart JS Delay instead of plain defer, so fragile scripts keep working.

WebP conversion is unavailable on my server

WebP conversion needs GD with WebP support or Imagick with WebP support. The Media screen reports exactly what your server has. Ask your host to enable GD WebP or Imagick WebP, then reload the screen.

Some images were not converted to WebP

WebP conversion only processes images the server can read and write to. The bulk screen reports how many images converted, how many failed and how many remain, and View Detailed Logs shows which files were skipped.

My host does not allow .htaccess changes

On nginx and on hosting that blocks .htaccess edits, add the WebP rule at the server level instead. Page caching does not depend on .htaccess and continues to work normally.

Some pages are never cached. Why?

FastLayer only stores a response that is safe to hand to every visitor. These are the usual reasons a page is skipped (enable Debug Mode on the Advanced Rules screen, then reload this page to see the exact reason in the Dashboard debug panel):

  • The visitor is logged in, or the request is a POST/HEAD, AJAX, REST, cron, preview, search or 404 request.
  • The page URL matches one of your cache exclusions, or the request carries an excluded cookie or user agent.
  • The URL has a query parameter FastLayer does not recognise. Standard WordPress parameters (page, paged, p, page_id, cat, tag, author, m, orderby, lang and the other archive/pagination parameters) are cached; anything else is not, so a crawler cannot fill the disk with ?random=1, ?random=2, … entries. Campaign parameters (utm_*, fbclid, gclid, msclkid and similar) are ignored when the cache key is built, so the same page reached from two campaigns shares one cache entry.
  • The response was not a 200, or another plugin marked it private / no-store, or it set a login/session cookie (wordpress_logged_in_*, wp_woocommerce_session_*, comment_author_*, PHPSESSID, …). Those responses are per-visitor and must never be replayed from cache.

The Dashboard “Temporary Cache Debug” panel is empty

Cache decision tracing is off by default, because recording it writes to the database on every page view. Enable Debug Mode on the Advanced Rules screen (or set WP_DEBUG to true) and load the front end once to populate the panel.

Does the cached HTML include headers set by other plugins?

No. A cache hit is served by the advanced-cache.php drop-in before WordPress loads, so headers other plugins add through WordPress (CSP, X-Frame-Options, X-Robots-Tag, Link preload hints) are not sent with a cached page, and the response status is 200. If your site depends on such headers, add those rules at the server level, where they also apply to cached pages.

External Services

This plugin can optionally integrate with one external, third-party service. It is off by default, and FastLayer only contacts that service once you configure it. The per-service notes below explain exactly when a request is made and what it contains.

ImageKit

ImageKit is a third-party image optimization and delivery service operated by ImageKit (https://imagekit.io/). It is not operated by, affiliated with, or endorsed by FastLayer. By enabling it you are choosing to have your site contact a service outside of your own hosting, so you should review ImageKit’s terms of service and privacy policy on their own website before enabling it.

  • Is it on by default? No. Image delivery stays off until you turn on the “Enable ImageKit for image delivery” toggle under FastLayer > CDN. FastLayer only rewrites your image URLs to ImageKit while that toggle is on and an endpoint is saved. Be aware that FastLayer still contacts your endpoint from the admin screen even when the toggle is off: once an endpoint is saved, opening the CDN settings screen, or clicking the connection test, sends the server-side request described below before you enable the toggle.
  • What does FastLayer ask you for? Only your ImageKit URL endpoint. FastLayer does not ask for, store, or transmit an ImageKit public key, private key, auth key, or any other account credential. Authentication and billing remain entirely between you and ImageKit.
  • What does FastLayer itself send, and when? Only from your admin screen, and only when you act: when you click the plugin’s ImageKit connection test, and when an administrator opens the FastLayer > CDN settings screen. On each of those actions your WordPress server requests one image URL at the endpoint you configured. That request contains:
    • the uploads path of one of your own images (with your site’s scheme and domain removed);
    • an image transformation string in the tr query parameter that asks ImageKit to choose the output format and quality automatically and to return a specific display width.
      FastLayer never uploads the contents of your image files to ImageKit, and these server-side requests carry no visitor or user data: no IP addresses, user agents, cookies, referrer data, WordPress user names, or e-mail addresses.
  • What happens once the toggle is on (visitors’ browsers)? When the toggle is on and an endpoint is saved, FastLayer rewrites the image URLs in your front-end pages to that endpoint. The images are then loaded by each visitor’s own browser directly from ImageKit, not through your WordPress server. ImageKit therefore receives those requests straight from the browser, including the requested image path and transformation and standard request data such as the visitor’s IP address and user agent (and the referring page). FastLayer does not send that data; the browser does, and ImageKit handles it under ImageKit’s own privacy policy. This affects front-end page views only, never admin, AJAX, cron or REST requests.
  • How is it protected? For the requests FastLayer itself makes, FastLayer restricts the host to ImageKit’s own hosts (imagekit.io and its subdomains) and rejects requests to any other host, to IP addresses, and to URLs containing embedded credentials. If you enter an endpoint without a scheme, FastLayer adds https://. If you enter one that explicitly begins with http://, FastLayer will use it as written, so enter your https:// endpoint to keep that connection encrypted. Front-end image URLs are built from whichever endpoint you save, so the same advice applies there.
  • What is stored locally? The endpoint you enter is saved in your WordPress options and is also written into a JSON configuration file FastLayer generates at wp-content/cache/wp-fastlayer/config.json (or sites/{blog_id}.json on multisite networks). This value is deleted when you uninstall the plugin.

Uninstall and data removal

  • Deactivate: removes the advanced-cache.php drop-in, the define( 'WP_CACHE', true ); line in wp-config.php, and the marked WebP block in .htaccess. Your settings and cached files are kept.
  • Delete: removes the plugin’s options, transients, cron jobs and generated cache files, including the saved ImageKit endpoint, which is stored in your options and in the generated wp-content/cache/wp-fastlayer/config.json (or per-site JSON files).
  • Not removed: WebP image files created next to your uploads are left in place.

Installation

FastLayer installs like any other WordPress plugin.

On activation, FastLayer installs its advanced-cache.php drop-in and adds define( 'WP_CACHE', true ); to wp-config.php so page caching can work. Both changes are undone automatically when you deactivate the plugin.

  1. In your WordPress admin, open Plugins > Add New, search for “FastLayer”, then click Install Now and Activate.
  2. To install manually, upload the fastlayer folder to /wp-content/plugins/ and activate the plugin from the Plugins screen.
  3. Open FastLayer in the admin menu. The Dashboard shows cache status, a cached-pages count and quick actions.

Recommended configuration

Every feature is off by default. Turn on one group at a time and check the
front end after each change, so you always know what made the difference.

Least effort, most gain (works on most sites):

  1. Page caching is the single biggest win: HTML is served without running PHP or querying the database. Enable Page Caching, leave the cache lifetime at 24 hours, and turn on Cache Preloading so pages are warmed again after a clear.
  2. Minification. Enable HTML minification, then CSS and JavaScript minification. Same pages, fewer bytes.
  3. Images. Run Bulk WebP Generation once for existing images, keep WebP delivery on, then enable Lazy Loading. Images are usually the largest part of a page.
  4. Critical CSS. Generate it from the CSS tab, review the result once, then enable it. This removes the stylesheet that blocks the first paint.
  5. Unused CSS (RUCSS). Drops the rules no element on the page uses. Try it on a staging copy first; any stylesheet FastLayer cannot parse is returned unchanged, but a custom theme may still need an exclusion.

Enable only after checking the front end:

  • Combine CSS/JS reduces requests, but it conflicts with some page builders, and on HTTP/2 many small requests are already cheap.
  • Smart JS Delay is a large win on third-party scripts, but it changes when scripts run. Keep the cart, checkout and navigation exclusions in place.
  • CDN / ImageKit moves assets to another host. Nothing is sent to ImageKit until you enter your own endpoint; see External Services for exactly what is requested.

Order matters. Get a cache HIT first, then add asset optimization. If a page breaks, switch on Safe Mode (it stops FastLayer changing the output without touching your saved settings) and check the debug panel before changing anything else.

Verify it is working

  1. Page cache: open a front-end page in a private or logged-out browser window. A cached response includes the X-Cache-Status: HIT response header.
  2. Dashboard: the FastLayer Dashboard reports a cached-pages count and cache status, and offers quick actions to clear or preload the cache.
  3. Media: the Media screen reports whether the server supports WebP, and bulk generation reports how many images converted, failed or remain.
  4. Assets: with combination enabled, check that combined CSS and JS files are served from wp-content/uploads/wp-fastlayer-min/.

Requirements

  • WordPress 6.0 or newer and PHP 7.4 or newer.
  • WebP conversion needs the GD library with WebP support, or Imagick with WebP support. The Media screen reports what your server supports.
  • FastLayer writes to wp-config.php and, when WebP is enabled, to the site root .htaccess. Both files must be writable by WordPress for FastLayer to add its rules automatically.

FAQ

Answers to the questions that come up most often.

Does FastLayer change WordPress core files?

No. FastLayer never edits files in wp-includes/ or wp-admin/. Like most caching plugins, it creates and manages its own files outside the plugin folder:

  • On activation it installs wp-content/advanced-cache.php.
  • On activation it adds define( 'WP_CACHE', true ); to wp-config.php, above the “That’s all, stop editing!” line. wp-config.php is backed up outside the web root first, and the line is removed again only when it carries FastLayer’s own ownership marker.
  • When WebP is enabled it adds a marked WP FastLayer WebP block to the .htaccess file in your WordPress root.

See Uninstall and data removal for what happens when you deactivate or delete the plugin.

How do I clear the cache?

Use the FastLayer menu in the admin bar to Clear All Cache, Clear CSS/JS Cache or Preload Cache. The same actions are on the plugin Dashboard.

How do I exclude a URL, cookie or script?

Cache exclusions for URLs, cookies and user agents are on the Advanced Rules screen. Individual CSS and JS files can be excluded by path, pattern or external domain on their own screens, and Safe Mode disables script delaying entirely. See Exclusions and diagnostics.

Do I need an ImageKit account?

No. ImageKit is optional and off by default, and FastLayer works fully without it. See External Services for exactly what is sent if you enable it.

Which files and folders does FastLayer create?

  • Page cache, configuration and the cache .htaccess: wp-content/cache/wp-fastlayer/
  • Combined and minified CSS/JS: wp-content/uploads/wp-fastlayer-min/
  • WebP files are generated next to the original images in your uploads folder.

What happens when I deactivate or delete FastLayer?

Deactivating removes the drop-in, the wp-config.php line and the WebP .htaccess directives, and leaves your settings and cached files in place. Deleting removes the plugin’s options, transients, cron jobs and cache files. See Uninstall and data removal for the full details.

Is any data sent to a third party?

No data leaves your site by default. The only external service is the optional ImageKit integration, and it does nothing until you configure it. See External Services for exactly what is sent, and by whom.

Does FastLayer add any public URLs or endpoints?

No. Every setting, cache action, bulk job and debug endpoint requires the manage_options capability plus a per-action nonce, and there is no unauthenticated AJAX action, no REST route and no public form. The only thing a visitor can trigger is the WebP fallback, and that one only ever serves a WebP file that already exists next to a real image inside your uploads folder.

What happens if a database cleanup is already running?

FastLayer takes a per-user lock before it deletes anything. A second click, a double-submitted form or a reloaded page reports that a cleanup is already running instead of starting a second one.

Where can I report a bug or ask for help?

Please open an issue on the plugin’s GitHub repository: https://github.com/kanhajatthap/WP-FastLayer

Screenshots

Changelog

1.6.0

  • UI/UX: completely redesigned Nginx WebP delivery notice into a clean, collapsible card restricted exclusively to the Media settings screen, eliminating intrusive raw configuration code blocks across admin pages.
  • Reliability: added dual-layer dismissal support (AJAX + fallback admin-post action) ensuring Nginx notices remain permanently dismissed once closed.
  • Enhancement: enabled full-page HTML WebP rewriting for header logos, navbar icons, and template images outside the main post content.
  • Reliability: added fail-safe deactivation cleanup — automatically purges page caches, purges host edge caches (WP Engine, SiteGround, Kinsta, LiteSpeed), removes static JSON configs, cleans minified bundles, and unlinks advanced-cache.php so deactivating never leaves a site with broken layout.
  • Compatibility: built-in safe exclusions for CSS and JS combine, defer, and async optimizations — automatically protects core jQuery, Elementor frontend/page CSS, and WooCommerce checkout assets from script timing and styling breakage.

1.5.9

  • Fix: restored Dark Mode / Light Mode theme switcher in admin header — resolves issue where clicking the colour scheme button failed to switch to the white/light theme.
  • Enhancement: one-click instant theme toggle between Dark and Light schemes with immediate DOM synchronization and browser localStorage persistence.

1.5.8

  • Fix: eliminated 504 Gateway Time-out caused by recursive asynchronous preload loopbacks exhausting PHP-FPM workers on shared hosting (e.g. SiteGround Nginx/PHP-FPM pools).
  • Reliability: converted background cache warming to rely solely on safe WP-Cron scheduling and user-driven dashboard updates, preventing server worker deadlocks and ensuring administrative settings remain fast and accessible.
  • Performance: reset default preload batch size to 2 URLs with a 20-second wall clock budget to prevent server load spikes and memory contention.

1.5.7

  • Enhancement: Multi-Builder Auto Critical CSS Engine — expanded automatic above-the-fold critical CSS extraction to natively support all major page builders and layout frameworks: Gutenberg / Block Editor (FSE), Elementor (including Flexbox/Grid containers .e-con), Divi (.et_pb_), WPBakery / Visual Composer (.vc_row, .vc_column, .vc_custom_), Beaver Builder (.fl-), Bricks (.brx-), Oxygen (.ct-), Spectra (.uagb-), Kadence (.kt-), GenerateBlocks (.gb-), and Astra/theme layouts.
  • Performance: Increased critical CSS rule extraction cap to 120 rules (up to 35 KB) to preserve full layout integrity and ensure 0 CLS and 0ms First Contentful Paint (FCP) across any active page builder.
  • Enhancement: Multi-Builder LCP Hero Background image preloading — detects background images in hero sections built with Divi, Elementor containers, Beaver Builder, Bricks, Oxygen, Spectra, Kadence, and WPBakery, injecting high-priority preload hints into .

1.5.6

  • Enhancement: Auto-linked “Remove Unused CSS” and “Smart Unused CSS Engine (RUCSS)” directly with Non-Blocking CSS Delivery and Auto Critical CSS generation, eliminating render-blocking CSS delays and reducing unused CSS warnings in Google PageSpeed Insights.
  • Performance: Enhanced Auto Critical CSS generator with WPBakery Page Builder (.vc_row, .vc_column, .vc_custom_*) and primary layout containers for instant above-the-fold paints without FOUC.
  • Enhancement: Activated Non-Blocking CSS Delivery by default in the Recommended (Aggressive) performance preset.
  • Reliability: Automatically invalidates and refreshes the cached critical CSS transient whenever minification or page cache is purged.

1.5.5

  • Fix: Comprehensive settings JSON export and import synchronization — resolved an issue where preloaded font URLs (preload_fonts_list), RUCSS exclusion rules (rucss_exclusions), asset cleanup script/style handles (disabled_scripts_list, disabled_styles_list), typography toggles, and WordPress Heartbeat configurations were not restored during a JSON snapshot import.
  • Fix: Corrected float precision handling for imagekit_max_oversize_ratio during settings import to prevent decimal ratio truncation.
  • Enhancement: Standardized import response redirects and status notifications directly on the Import / Export hub page.

1.5.4

  • Performance: overhauled CSS combine engine to safely bundle theme and builder stylesheets containing pseudo-elements and inline extras into unified cached bundles, eliminating up to 15+ render-blocking HTTP requests.
  • New: Smart LCP Hero Background detector for WPBakery Page Builder and top hero containers, automatically injecting high-priority preload hints (<link rel="preload" as="image" fetchpriority="high">) directly into the document <head>.
  • Enhancement: automatic font-display: swap enforcement on all external minified and combined stylesheets to eliminate webfont render-blocking delays.
  • Enhancement: updated autonomous cache preloader with modern Accept: image/webp headers to ensure WebP variants are warmed for upstream CDN and reverse-proxy caches.
  • New: automatic cache warming restart on cache purge/clear — whenever cache is cleared from the admin bar, settings, or dashboard, the background preloader immediately resumes warming all discovered public pages.

1.5.3

  • Fix: enforce HTTPS scheme resolution on reverse-proxy and Cloudflare environments to eliminate browser Mixed Content security blocking.
  • Fix: repair unquoted relative url() and @import rebasing in minified and combined stylesheets so font icons and background images load reliably.
  • New: automatic background cache warming starts immediately whenever page caching or a performance preset is enabled.
  • New: interactive pagination (10, 25, 50, 100 per page) and real-time search filter synchronization in the Discovered URLs inspection table.
  • Enhancement: gated debug trace script output to debug mode only.
  • i18n: updated translation catalog covering all current UI strings.

1.5.2

  • New: dedicated Cache Analytics & Real-Time Warming dashboard (NitroPack style) with real-time coverage progress bar, KPI metrics, and live discovered URLs inspection table.
  • New: real-time sequential AJAX background queue advancement so warming completes to 100% reliably without depending on WP-Cron loopback.
  • New: dynamic taxonomy (categories/tags) and WooCommerce products discovery in preloader queue.
  • New: fast-path for already-cached pages preventing local server loopback deadlocks.
  • New: command-line control for sites that prefer the terminal. wp fastlayer status reports the cache, preload and WebP state; wp fastlayer cache flush clears the cache, the minified assets and the preload queue; wp fastlayer cache preload queues a warm-up; and wp fastlayer webp convert converts existing images in batches. The commands reuse the same code paths as the admin screens, so they cannot drift from them.
  • New: a single-command regression runner (php tests/run-all.php) for the plugin’s test suite, with WordPress-dependent tests skipped – not failed – when no WordPress install is available.
  • New: a reproducible release build (php bin/build.php) that assembles the production archive from an explicit file list, refuses to build when the three version numbers disagree, and can verify that an archive matches the working copy byte for byte.
  • Developer: page caching, cache purging, preload and WebP generation are unchanged in this release and were re-verified end to end on WordPress 7.2 with the plugin installed from the built archive.

1.5.1

  • Fixed WebP images served through the PHP fallback arriving empty on PHP-FPM: the request was finished before the image body was written.
  • Fixed the Smart Unused CSS (RUCSS) engine so it actually runs, and rewrote its pruning to be conservative. Stylesheets are no longer damaged: rules inside @media/@supports/@keyframes are kept intact, and element, attribute and combinator selectors are never dropped.
  • Fixed combined stylesheets losing their images and fonts when “Combine CSS” was enabled without “Minify CSS”: relative url() references are now always rebased for the bundle.
  • Fixed cache files being written non-atomically, which could serve a half-written page to a visitor during a cache miss.
  • Cache entries are only created for a fully successful 200 response that does not send private/no-store headers or a login/session cookie. Ordinary cookies such as WooCommerce’s woocommerce_recently_viewed do not stop a page from being cached.
  • The cache decision trace is no longer written to the database on every page view. It is recorded only while Debug Mode (or WP_DEBUG) is on.
  • URLs carrying query parameters FastLayer does not recognise are no longer cached, which stops unbounded cache growth from crawlers appending arbitrary parameters. Campaign parameters (utm_*, fbclid, gclid, …) are ignored when the cache key is built, so they now share one cache entry.
  • HTML minification no longer removes the whitespace between two adjacent tags, which could join inline elements together.
  • Minification no longer blanks a page when a processor returns an error (for example on invalid UTF-8).
  • Fixed the plugin’s WP_CACHE line never being removed on delete, and a commented-out define( 'WP_CACHE', ... ) in wp-config.php now raises an admin notice instead of silently disabling page caching.
  • Hardened the cache, minified-asset and WebP path checks so a sibling directory cannot match the base directory.
  • The advanced-cache.php drop-in is now refreshed automatically after an update instead of staying on the version that was installed at activation. It is staged and renamed into place, so a concurrent request never includes a half-written file.
  • Admin interface: dark mode now works. It follows your operating-system setting, changes live when the system theme changes, and can be cycled (auto / dark / light) with the new button in the plugin header.
  • Admin interface: text and controls meet the WCAG AA contrast minimum. White text on the success, warning, danger and primary colours was between 2.15:1 and 4.47:1 and is now above 4.5:1, and form-field borders are visible instead of near-white on white.
  • Admin interface: every custom control (toggle switches, buttons, the page list, preset cards) shows a keyboard focus ring, and heading order is correct for screen readers.
  • Admin interface: the plugin screens are usable on a phone or tablet — the page list becomes a scrolling strip and wide tables scroll instead of overflowing.
  • Admin interface: tab switches and buttons respect “reduce motion”, and the stylesheet no longer needs hundreds of !important overrides to win the cascade.

1.5.0

  • Added Smart Unused CSS (RUCSS) Engine: real-time HTML analysis that prunes up to 80% of unused styles for lightning-fast paints.
  • Added WordPress Heartbeat Control: manage Heartbeat API frequency (60s interval or complete frontend deregistration) to reduce server CPU spikes.
  • Added Asset CleanUp & Script Manager: selectively dequeue bloated scripts and styles by handle on public pages.
  • Added WooCommerce Turbo Engine: eliminates cart fragments AJAX requests on non-shop pages and defers eCommerce assets.
  • Enhanced Live In-Dashboard Google PageSpeed Insights Audit widget with instantaneous official REST API checks.

1.4.0

  • Added Speculative Loading / Instant Click Engine with 0ms internal page navigation on pointer hover and mobile touchstart.
  • Added Instant Click toggle in Cache Settings with built-in exclusion safety for admin, cart, checkout, logout, and media links.
  • Added Auto Critical CSS Generator for Lighthouse 100/100, automatically isolating above-the-fold layout styles and rendering non-blocking CSS.
  • Enhanced homepage critical CSS extractor with intelligent selector isolation for core headers, navigation, hero banners, and Gutenberg/Elementor blocks.

1.3.0

  • Added a dedicated Fonts & Typography optimization hub for custom webfonts.
  • Added Critical Webfonts Preload Hub (<link rel="preload" as="font">) to eliminate Lighthouse 1,100ms+ webfont delays on mobile and desktop.
  • Added automatic font-display: swap injection for Elementor Font Awesome icons (Solid, Brands, Regular) and eicons (fa-solid-900.woff2, fa-brands-400.woff2).
  • Added global font-display: swap enforcement across all custom @font-face blocks in themes and plugins.
  • Added preconnect resource hints for Google Fonts (fonts.googleapis.com and fonts.gstatic.com).
  • Added 1-click quick preset buttons to instantly preload Elementor Font Awesome and Eicons.
  • Added optional Dashicons cleanup for non-logged-in public visitors.

1.2.0

  • Added interactive visual feedback for cache actions: animated trash chomp and dynamic vacuum suction progress for Purge Cache, and turbo-charge electric energy pulse for Warm Cache (Preload).
  • Added dedicated parallel AJAX endpoints for cache purging and background cache warming with real-time status updates.
  • Completely redesigned all sub-pages (Cache, HTML, CSS, JS, Media, CDN, Database, and Advanced) with modern SaaS card-row layouts and iOS-style toggle controls.
  • Fully overhauled CDN & ImageKit integration with step-by-step setup guide, live interactive URL preview transformer, and diagnostic cards.
  • Added compact floating sticky save toolbar with frosted backdrop blur and 15px bottom margin for seamless editing across tall settings screens.
  • Redesigned One-Click Performance Presets modal dialog with FastLayer-themed interactive buttons, success indicators, and direct close control.
  • Modernized standalone Import/Export settings view and streamlined dashboard navigation.
  • Improved accessibility with larger typography, crisp icons, and enhanced high-contrast Dark Mode across all interactive widgets.

1.1.0

  • Renamed all plugin-prefixed identifiers (options, cron hooks, transients, asset handles, constants and classes) to the fastlayer_* naming scheme required by the WordPress.org plugin directory.
  • Added automatic migration for existing installs: settings, scheduled preload jobs, transient keys and cache drop-in ownership are carried over safely, with no manual steps required.
  • Combined CSS and JavaScript files are now registered through the WordPress core style and script printing APIs.
  • Added extra safety checks for cache and minified-asset file writes.
  • WebP rewrite directives are now cleared from the root .htaccess when the plugin is deactivated or uninstalled.
  • Uninstall now fully removes plugin options, transients, cron jobs and cache files.

1.0.0

  • Initial release.
  • Added page cache, cache preload, minify options, lazy load, WebP conversion, and database optimization.