{"id":293392,"date":"2026-05-19T09:12:20","date_gmt":"2026-05-19T09:12:20","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/lazy-asset-blocker\/"},"modified":"2026-05-19T09:09:42","modified_gmt":"2026-05-19T09:09:42","slug":"lm-page-assets-control","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/lm-page-assets-control\/","author":23099193,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"trunk","tested":"6.9.4","requires":"5.0","requires_php":"7.4","requires_plugins":null,"header_name":"LM Page Assets Control","header_author":"LM Designers","header_description":"Block specific CSS and JS files from loading on pages where they are not needed. Improves page speed by preventing unnecessary assets from loading. Use with caution - incorrect rules may break your site's appearance or functionality.","assets_banners_color":"f3afb1","last_updated":"2026-05-19 09:09:42","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/lmwebdesigners.com\/plugin\/lm-page-assets-control\/","header_author_uri":"https:\/\/lmwebdesigners.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":30,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0":{"tag":"1.0","author":"lmdesigners","date":"2026-05-19 09:11:50"}},"upgrade_notice":{"1.0.0":"

Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3536930,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3536930,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3536930,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.jpg":{"filename":"banner-772x250.jpg","revision":3536930,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3536930,"resolution":"1","location":"assets","locale":"","width":825,"height":963},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3536930,"resolution":"2","location":"assets","locale":"","width":1137,"height":672}},"screenshots":{"1":"The main admin panel showing the rule list with the warning notice.","2":"An expanded rule card showing the asset URL field and page condition selector.","3":"WooCommerce-specific conditions available in the condition picker.","4":"Empty state when no rules have been created yet."}},"plugin_section":[],"plugin_tags":[8847,263490,5896,247,794],"plugin_category":[52,54],"plugin_contributors":[263491],"plugin_business_model":[],"class_list":["post-293392","plugin","type-plugin","status-publish","hentry","plugin_tags-asset-management","plugin_tags-css-javascript","plugin_tags-page-speed","plugin_tags-performance","plugin_tags-speed","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-lmdesigners","plugin_committers-lmdesigners"],"banners":{"banner":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/banner-772x250.jpg?rev=3536930","banner_2x":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/banner-1544x500.png?rev=3536930","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/icon-128x128.png?rev=3536930","icon_2x":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/icon-256x256.png?rev=3536930","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/screenshot-1.png?rev=3536930","caption":"The main admin panel showing the rule list with the warning notice."},{"src":"https:\/\/ps.w.org\/lm-page-assets-control\/assets\/screenshot-2.png?rev=3536930","caption":"An expanded rule card showing the asset URL field and page condition selector."}],"raw_content":"\n

LM Page Assets Control<\/strong> gives you full control over which CSS and JavaScript files load on each page of your WordPress site. Plugins often load their assets globally \u2014 on every single page \u2014 even when they are only needed on one or two. This causes unnecessary bloat, slower load times, and lower PageSpeed scores.<\/p>\n\n

With LM Page Assets Control, you can create simple rules to block any CSS or JS file from loading on specific pages, page types, or even everywhere except where it is needed.<\/p>\n\n

How It Works<\/h4>\n\n

You provide a partial URL of the asset you want to block (for example woocommerce.css<\/code> or elementor\/assets\/css<\/code>) and choose where to block it \u2014 on the homepage, a specific page, all single posts, and more. The plugin then dequeues and deregisters the matching assets on the frontend, preventing them from loading entirely.<\/p>\n\n

Key Features<\/h4>\n\n
    \n
  • Partial URL matching<\/strong> \u2014 You don't need the full URL. Just enter any part of the filename or path and all matching assets will be blocked.<\/li>\n
  • 14 built-in page conditions<\/strong> \u2014 Block assets everywhere, on the front page, specific pages (by slug or ID), single posts, archive pages, blog index, and all major WooCommerce contexts (Shop, Product, Cart, Checkout).<\/li>\n
  • URL-based conditions<\/strong> \u2014 Block assets on any URL that contains or does not contain a specific string.<\/li>\n
  • Enable \/ Disable rules<\/strong> \u2014 Toggle any rule on or off without deleting it.<\/li>\n
  • Named rules<\/strong> \u2014 Give each rule a descriptive name so you can manage them easily.<\/li>\n
  • Multiple rules<\/strong> \u2014 Add as many blocking rules as you need.<\/li>\n
  • Zero configuration<\/strong> \u2014 No API keys, no external services, no bloat. Just install and use.<\/li>\n
  • Clean admin UI<\/strong> \u2014 A simple, modern interface under Plugins \u2192 LM Page Assets Control.<\/li>\n
  • WooCommerce compatible<\/strong> \u2014 Includes dedicated conditions for Shop, Product, Cart, and Checkout pages.<\/li>\n<\/ul>\n\n

    Available Page Conditions<\/h4>\n\n
      \n
    • Everywhere (all pages)<\/li>\n
    • Home \/ Front page<\/li>\n
    • Everywhere except home<\/li>\n
    • Blog index page<\/li>\n
    • Single posts<\/li>\n
    • Specific page (by slug or ID \u2014 supports multiple, comma-separated)<\/li>\n
    • Archive pages<\/li>\n
    • WooCommerce \u2014 Shop page<\/li>\n
    • WooCommerce \u2014 Everywhere except Shop<\/li>\n
    • WooCommerce \u2014 Single product page<\/li>\n
    • WooCommerce \u2014 Cart page<\/li>\n
    • WooCommerce \u2014 Checkout page<\/li>\n
    • URL contains a specific string<\/li>\n
    • URL does NOT contain a specific string<\/li>\n<\/ul>\n\n

      Common Use Cases<\/h4>\n\n
        \n
      • Block WooCommerce styles on non-shop pages<\/li>\n
      • Prevent a contact form plugin from loading its CSS\/JS on every page<\/li>\n
      • Stop a slider plugin from loading scripts on pages that have no slider<\/li>\n
      • Remove Elementor assets from pages built with a different builder<\/li>\n
      • Block any third-party plugin asset that is causing PageSpeed issues<\/li>\n<\/ul>\n\n

        \u26a0\ufe0f Important Notice<\/h4>\n\n

        This plugin directly controls which CSS and JavaScript files are loaded on your website. Blocking the wrong asset can break your site's appearance, functionality, or checkout process. Always test changes on a staging environment first and keep a backup ready.<\/strong> If you are not confident about WordPress asset management, consult a developer before making changes.<\/p>\n\n

        Who Is This For?<\/h4>\n\n

        This plugin is intended for developers, advanced WordPress users, and site owners who are familiar with browser developer tools and WordPress asset management. It is not a \"set and forget\" solution \u2014 it requires you to identify the assets you want to block and verify that blocking them does not cause issues.<\/p>\n\n\n

          \n
        1. Upload the lm-page-assets-control<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install it directly through the WordPress Plugins screen.<\/li>\n
        2. Activate the plugin through the Plugins<\/strong> screen in WordPress.<\/li>\n
        3. Go to Plugins \u2192 LM Page Assets Control<\/strong> in the WordPress admin menu.<\/li>\n
        4. Click Add New Rule<\/strong> and fill in the asset URL partial and the condition.<\/li>\n
        5. Click Save All Rules<\/strong>.<\/li>\n<\/ol>\n\n\n
          \n

          How do I find the URL of an asset I want to block?<\/h3><\/dt>\n

          Open your browser's Developer Tools (press F12), go to the Network<\/strong> tab, filter by CSS or JS, and reload the page. You will see all assets being loaded. Copy any part of the filename or path \u2014 for example slider-pro.min.css<\/code> or plugins\/slider-pro\/css<\/code> \u2014 and paste it into the Asset URL field.<\/p>\n\n

          You can also use PageSpeed Insights (https:\/\/pagespeed.web.dev\/) to identify render-blocking resources that are slowing down your site.<\/p><\/dd>\n

          Will this break my site?<\/h3><\/dt>\n

          It can, if you block the wrong asset. Always test on a staging site first. If something breaks after saving rules, you can disable the offending rule or deactivate the plugin \u2014 your site will return to normal immediately.<\/p><\/dd>\n

          Does it work with WooCommerce?<\/h3><\/dt>\n

          Yes. The plugin includes dedicated conditions for WooCommerce Shop, Product, Cart, and Checkout pages. However, be especially careful when blocking WooCommerce-related assets as this can affect the purchasing experience.<\/p><\/dd>\n

          Does it work with page builders like Elementor, Divi, or Beaver Builder?<\/h3><\/dt>\n

          Yes, you can use it to block page builder assets on pages that don't use that builder. Use the Asset URL partial from the Network tab to identify the correct file paths.<\/p><\/dd>\n

          Can I block multiple assets with one rule?<\/h3><\/dt>\n

          One rule targets one partial URL match. However, one partial match can block multiple files if they all share the same path string. For example, entering elementor\/assets<\/code> would block all assets whose URL contains that path. Add separate rules for different asset paths.<\/p><\/dd>\n

          Can I block an asset on all pages except one?<\/h3><\/dt>\n

          Yes. Use the URL does NOT contain<\/strong> condition and enter a string that uniquely identifies the page you want to keep the asset on.<\/p><\/dd>\n

          Does this affect the admin area?<\/h3><\/dt>\n

          No. The plugin only runs on the frontend (wp_enqueue_scripts<\/code> hook). Admin assets are never affected.<\/p><\/dd>\n

          Is there a premium version?<\/h3><\/dt>\n

          No. LM Page Assets Control is completely free with no premium upsell.<\/p><\/dd>\n\n<\/dl>\n\n\n

          1.0.0<\/h4>\n\n
            \n
          • Initial release.<\/li>\n
          • Support for 14 page conditions including all major WooCommerce contexts.<\/li>\n
          • Partial URL matching for CSS and JS assets.<\/li>\n
          • Enable\/disable toggle per rule.<\/li>\n
          • Named rules for easy management.<\/li>\n
          • Clean, modern admin UI.<\/li>\n<\/ul>","raw_excerpt":"Block specific CSS and JS files from loading on pages where they are not needed. Improve page speed by preventing unnecessary assets from loading.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/293392","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=293392"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lmdesigners"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=293392"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=293392"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=293392"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=293392"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=293392"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=293392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}