Title: Loadwright
Author: Muhammad Adnan Bashir
Published: <strong>2026 年 7 月 23 日</strong>
Last modified: 2026 年 7 月 23 日

---

搜尋外掛

![](https://ps.w.org/loadwright/assets/banner-772x250.png?rev=3620188)

![](https://ps.w.org/loadwright/assets/icon-256x256.png?rev=3620188)

# Loadwright

 由 [Muhammad Adnan Bashir](https://profiles.wordpress.org/muhammadnan/) 開發

[下載](https://downloads.wordpress.org/plugin/loadwright.1.0.0.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/loadwright/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/loadwright/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/loadwright/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/loadwright/#developers)

 [技術支援](https://wordpress.org/support/plugin/loadwright/)

## 外掛說明

**Loadwright** makes WordPress faster by doing something most speed plugins can’t:
it stops the plugins you don’t need from loading at all on the pages where they 
aren’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’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.

## 螢幕擷圖

[⌊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.

## 安裝方式

 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.

## 常見問題集

### How is this different from “asset” optimizers?

Asset optimizers (and dequeue tricks) remove specific CSS/JS files but the plugin’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’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’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.

## 使用者評論

這個外掛目前沒有任何使用者評論。

## 參與者及開發者

以下人員參與了開源軟體〈Loadwright〉的開發相關工作。

參與者

 *   [ Muhammad Adnan Bashir ](https://profiles.wordpress.org/muhammadnan/)

[將〈Loadwright〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/loadwright)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/loadwright/)、
查看 [SVN 存放庫](https://plugins.svn.wordpress.org/loadwright/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/loadwright/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/loadwright/)。

## 變更記錄

#### 1.0.0

 * Initial public release.

## 中繼資料

 *  版本 **1.0.0**
 *  最後更新 **3 週前**
 *  啟用安裝數 **少於 10 次**
 *  WordPress 版本需求 ** 5.6 或更新版本 **
 *  已測試相容的 WordPress 版本 **7.0.4**
 *  PHP 版本需求 ** 7.2 或更新版本 **
 *  語言
 * [English (US)](https://wordpress.org/plugins/loadwright/)
 * 標籤:
 * [Disable Plugins](https://tw.wordpress.org/plugins/tags/disable-plugins/)[optimization](https://tw.wordpress.org/plugins/tags/optimization/)
   [Page Speed](https://tw.wordpress.org/plugins/tags/page-speed/)[performance](https://tw.wordpress.org/plugins/tags/performance/)
 *  [進階檢視](https://tw.wordpress.org/plugins/loadwright/advanced/)

## 評分

這個項目尚無任何評論記錄。

[撰寫評分](https://wordpress.org/support/plugin/loadwright/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/loadwright/reviews/)

## 參與者

 *   [ Muhammad Adnan Bashir ](https://profiles.wordpress.org/muhammadnan/)

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/loadwright/)