Title: Loadwright Author: Muhammad Adnan Bashir Published: Agẹmọ 23, 2026 Last modified: Agẹmọ 23, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/loadwright/assets/banner-772x250.png?rev=3620188) ![](https://ps.w.org/loadwright/assets/icon-256x256.png?rev=3620188) # Loadwright Láti ọwọ́ [Muhammad Adnan Bashir](https://profiles.wordpress.org/muhammadnan/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/loadwright.1.0.0.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/loadwright/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/loadwright/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/loadwright/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/loadwright/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/loadwright/) ## Àpèjúwe **Loadwright** makes WordPress faster by doing something most speed plugins canÌtumọ̀ Yorùbá: ’t: it stops the plugins you donÌtumọ̀ Yorùbá: ’t need from loading at all on the pages where they arenÌtumọ̀ Yorùbá: ’t used. Their PHP never runs, their database queries never fire, and their CSS/JS is never enqueued on those requests. By default, WordPress loads **every** active plugin on **every** request — even a contact-form plugin on a blog post, a slider on the checkout, or a shop filter on your About page. That wasted work slows down your server response and bloats every page. This plugin lets you scope each plugin to exactly where it belongs, so the rest of your site stays lean. Unlike asset optimizers that only minify or defer files, this works at the **plugin level**: the whole plugin is removed from the request. It works through a tiny must- use loader that you install with one click from the settings screen, so the decision happens _before_ other plugins load — the only point at which a plugin can be kept out of a request entirely. #### How it speeds up your site Cutting unused plugins from a request reduces three things that page-speed tools measure directly: * **Server response time (TTFB)** — less PHP executes and fewer database queries run, so the page is built faster. * **Page weight (CSS/JS)** — plugins that would have enqueued scripts and styles no longer do, shrinking the HTML, CSS, and JavaScript the browser has to download and process. * **Main-thread work** — less JavaScript means faster interactivity. These are the same factors behind the scores you see in **Google PageSpeed Insights**,** GTmetrix**, and **Lighthouse**, and the page-speed metrics behind them: **LCP** ( Largest Contentful Paint), **INP** (Interaction to Next Paint), and **TTFB** (server response time). Trimming per-page plugin load is one of the most effective WordPress speed-optimization (WPO) techniques, and it pairs well with a caching plugin and a CDN for the best results. Actual improvement depends on your theme, hosting, and which plugins you scope — this plugin gives you the control; your rules decide the gain. #### What you can target * Specific pages, posts, or products (by ID) * Whole post types (posts, pages, products, or any custom type) * Categories and product categories * The site front page #### Two modes per rule * **Disable on matches** — turn the plugin off where the conditions match. * **Enable only on matches** — keep the plugin on there, off everywhere else. #### Great for * Speeding up blog posts by unloading WooCommerce/shop plugins they never use. * Keeping form, slider, popup, gallery, and social plugins scoped to the few pages that need them. * Lowering queries and payload on landing pages to lift PageSpeed and GTmetrix scores. * Resolving plugin conflicts by limiting a plugin to where it belongs. #### Good to know * The controller plugin never disables itself. * If a request canÌtumọ̀ Yorùbá: ’t be resolved to a single published object, ** no** rules are applied (it fails open — nothing is disabled when in doubt). * It does not minify, combine, or lazy-load assets; it is plugin-level load control that complements those tools rather than replacing them. * The must-use loader is only added when you click to install it, and is removed on Remove loader, deactivation, or uninstall — restoring normal loading immediately. ## Àwọn àwòrán ìbòjú [⌊The rules screen under Settings → Loadwright.⌉⌊The rules screen under Settings → Loadwright.⌉[ The rules screen under Settings Loadwright. [⌊A single rule targeting a plugin by category and post type.⌉⌊A single rule targeting a plugin by category and post type.⌉[ A single rule targeting a plugin by category and post type. ## Ìgbéwọlẹ̀ 1. Upload the `loadwright` folder to `/wp-content/plugins/`, or install through ** Plugins Add New**. 2. Activate the plugin. 3. Go to **Settings Loadwright**. Under **Must-use loader**, read the explanation and click **Install must-use loader** — this copies a small file (`loadwright-loader. php`) into `wp-content/mu-plugins/` so Loadwright can run early enough to control plugin loading. Nothing is copied without this click. 4. Add one or more rules and save. Rules only take effect while the loader is installed. 5. Purge any page/edge cache so the rules apply to already-cached pages. You can remove the loader anytime with **Remove loader**; deactivating or deleting the plugin removes it automatically. ## FAQ ### How is this different from “asset” optimizers? Asset optimizers (and dequeue tricks) remove specific CSS/JS files but the pluginÌtumọ̀ Yorùbá: ’s PHP still runs. This plugin removes the plugin from the request entirely, so its PHP, queries and hooks never execute. ### Why does it use a must-use loader, and is it optional? WordPress decides which plugins to load very early in each request, and only a must- use plugin runs early enough to influence that list. Loadwright therefore copies a small loader file into wp-content/mu-plugins/ — but only after you explicitly click Install must-use loader on the settings screen. The file is copied as-is from the plugin, does nothing but load LoadwrightÌtumọ̀ Yorùbá: ’s core, and is removed when you click Remove loader or when you deactivate or delete the plugin. Until it is installed, your rules are saved but inactive. ### Is it safe to disable WooCommerce-dependent plugins on cart/checkout? Be careful. Those pages do a lot server-side. Only disable plugins that are purely decorative on the page in question, and always test as a logged-out visitor with items in the cart. ### A rule doesnÌtumọ̀ Yorùbá: ’t seem to fire on a page. Why? A rule only applies when the request resolves to exactly one published post/page/ product. Ambiguous URLs (e.g. two items sharing a slug) are left untouched by design. Archive, search and 404 requests are not targeted in this version. ### Does it work on multisite / network-activated plugins? Rules apply to normally activated (per-site) plugins. Network-activated plugins are not affected in this version. ### Will deactivating it undo everything? Yes. Deactivation removes the loader, so every plugin loads normally again immediately. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Loadwright” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Muhammad Adnan Bashir ](https://profiles.wordpress.org/muhammadnan/) [Túmọ̀ “Loadwright” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/loadwright) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/loadwright/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/loadwright/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/loadwright/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/loadwright/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 1.0.0 * Initial public release. ## Àkójọpọ̀ Meta * Ẹ̀yà **1.0.0** * Ìgbàgbọ́hùn tó kẹ́yìn **oṣù 1 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 5.6 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.0.4** * Ẹ̀yà PHP ** 7.2 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/loadwright/) * Àwọn àmì * [Disable Plugins](https://yor.wordpress.org/plugins/tags/disable-plugins/)[optimization](https://yor.wordpress.org/plugins/tags/optimization/) [Page Speed](https://yor.wordpress.org/plugins/tags/page-speed/)[performance](https://yor.wordpress.org/plugins/tags/performance/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/loadwright/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/loadwright/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/loadwright/reviews/) ## Àwọn Olùkópa * [ Muhammad Adnan Bashir ](https://profiles.wordpress.org/muhammadnan/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/loadwright/)