Pagelean FAQ
Frequently asked questions regarding Pagelean setup, condition matching, troubleshooting, and performance best practices.
General questions
Section titled “General questions”Does Pagelean combine, minify or defer files?
Section titled “Does Pagelean combine, minify or defer files?”No. Pagelean is not a file minifier or script concatenator. Its specific purpose is conditional asset loading: removing handles from pages where their code is never used. For minification, concatenation, or HTML deferment, you can continue using your preferred caching plugin or CDN (such as Cloudflare, WP Rocket, or LiteSpeed Cache).
Does Pagelean run on WordPress admin screens?
Section titled “Does Pagelean run on WordPress admin screens?”No. Pagelean rules operate exclusively on the frontend of your site (! is_admin()). Administrative dashboards, block editors, and settings pages always load all core, theme, and plugin scripts without interference.
Will Pagelean break my caching plugin or CDN?
Section titled “Will Pagelean break my caching plugin or CDN?”No. Because Pagelean dequeues assets during WordPress core’s wp_enqueue_scripts hook before the HTML page is rendered, your caching plugin or CDN will simply cache the lighter, cleaner HTML output. Remember to clear your page cache after modifying Pagelean rules so visitors receive the updated HTML immediately.
Troubleshooting and behavior
Section titled “Troubleshooting and behavior”Why is my dequeued script still loading on the page?
Section titled “Why is my dequeued script still loading on the page?”If a script handle is set to be removed but still appears in the page source:
- The script is a dependency of another active file: If Script B declares
deps = ['script-a']and Script B is enqueued on that page, WordPress automatically loads Script A to satisfy the dependency.- Solution: Check the Also deregister option on the rule. This removes the handle completely from the WordPress asset registry.
- The script was enqueued after priority 100: Pagelean processes rules at priority
100onwp_enqueue_scripts. If a plugin enqueues a script at priority101or later, or duringwp_footer, Pagelean’s hook has already run. - The page was served from an external cache: Purge your caching plugin or CDN cache for that URL and reload with
Ctrl+Shift+R(Cmd+Shift+R).
How does Test Mode protect live site visitors?
Section titled “How does Test Mode protect live site visitors?”When Test mode is turned on in the Pagelean settings:
- Rules run only for logged-in users with administrator rights (
current_user_can('manage_options')). - Regular visitors, logged-in subscribers, and search engine crawlers receive untouched pages with standard asset loading.
- This allows you to safely test dequeuing rules on staging or production sites without risking frontend disruptions for actual shoppers or readers.
Are block themes (Full Site Editing) supported?
Section titled “Are block themes (Full Site Editing) supported?”Yes. Pagelean hooks into the core WordPress asset pipeline (wp_enqueue_scripts), which functions identically across classic PHP themes and modern block themes.
How does uninstall work?
Section titled “How does uninstall work?”When you delete Pagelean through the WordPress Plugins screen, its uninstallation script (uninstall.php) removes all stored database records across single sites and all network sites in multisite installations:
plogins_assets_settings(master options and rule definitions)plogins_assets_seen_handles(handle discovery cache)plogins_assets_db_version(schema version tracker)
No orphan configuration records or hidden database rows remain behind.