Title: Arvexa Performance Overlay
Author: balloodn
Published: <strong>2026 年 7 月 20 日</strong>
Last modified: 2026 年 8 月 13 日

---

搜尋外掛

![](https://ps.w.org/arvexa-performance-overlay/assets/banner-772x250.png?rev=3616223)

![](https://ps.w.org/arvexa-performance-overlay/assets/icon-256x256.png?rev=3616223)

# Arvexa Performance Overlay

 由 [balloodn](https://profiles.wordpress.org/balloodn/) 開發

[下載](https://downloads.wordpress.org/plugin/arvexa-performance-overlay.1.0.2.zip)

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

 [技術支援](https://wordpress.org/support/plugin/arvexa-performance-overlay/)

## 外掛說明

Arvexa Performance Overlay shows a small pill in the corner of every page — for 
administrators only. Click it and you get a live panel with everything that matters
about the page you are looking at:

 * **Server** — PHP generation time, SQL query count and total time, peak memory,
   number of enqueued scripts and styles, total size of autoloaded options, and 
   the lifecycle phase that ate the biggest share of PHP time.
 * **Components** — the cost of every plugin and theme on this page: SQL queries
   and time on the server side, requests and transferred bytes on the asset side.
   The answer to “which plugin slowed us down” in one glance.
 * **Network** — TTFB, request count, transferred bytes.
 * **Rendering** — LCP (and _which element_ it is), CLS, INP, DOM node count, long
   tasks. Official Web Vitals thresholds, color-coded.
 * **AJAX / REST** — every same-origin admin-ajax, wc-ajax and REST call timed as
   it happens.
 * **Slowest queries** — the top queries with timings.

#### How it works

 * Per-query plugin attribution uses the `log_query_custom_data` filter and a backtrace
   scan — no core hacks, no db.php drop-in.
 * The plugin never enables or changes `SAVEQUERIES`. To collect query timings, 
   a site administrator may explicitly add `define( 'SAVEQUERIES', true );` to `
   wp-config.php` before the “That’s all, stop editing!” line.
 * Visitors are never affected: for anyone without the capability the plugin adds
   no assets, no queries and no output.
 * Add-ons can extend the panel via the `arvexa_performance_overlay_data` PHP filter
   and the `window.ArvexaPerformanceOverlay` JS API.

#### Arvexa Performance Pro

Deep diagnostics live in the Arvexa Performance Pro add-on: full hook timeline, 
server cost of every AJAX/REST call (X-Arvexa-Performance header), remote HTTP tracking(
see what your shipping/payment APIs cost), WP_Query explorer with SQL and EXPLAIN,
per-plugin drill-down cards, layout-shift attribution per element, and performance
history with before/after comparison when a plugin is installed or updated.

## 螢幕擷圖

[⌊The overlay panel: Server, Network, Rendering and Components at a glance.⌉⌊The
overlay panel: Server, Network, Rendering and Components at a glance.⌉[

The overlay panel: Server, Network, Rendering and Components at a glance.

[⌊Components — per-plugin SQL and asset cost.⌉⌊Components — per-plugin SQL and asset
cost.⌉[

Components — per-plugin SQL and asset cost.

[⌊Slowest queries with timings.⌉⌊Slowest queries with timings.⌉[

Slowest queries with timings.

[⌊The pill — the only thing visible until you need more.⌉⌊The pill — the only thing
visible until you need more.⌉[

The pill — the only thing visible until you need more.

## 安裝方式

 1. Upload the `arvexa-performance-overlay` folder to `/wp-content/plugins/`, or install
    through the WordPress plugin screen.
 2. Activate the plugin.
 3. Open any page of your site while logged in as an administrator — the Arvexa Performance
    Overlay pill appears bottom right. Click it to expand the panel.
 4. Reload once more to get SQL timings and the per-plugin breakdown (see FAQ).

## 常見問題集

### Why is the per-plugin SQL breakdown empty on the first load?

The plugin never enables `SAVEQUERIES`. To collect per-plugin query timings, add`
define( 'SAVEQUERIES', true );` to `wp-config.php` before the “That’s all, stop 
editing!” line, then reload the page.

### Does it slow down my site?

For visitors — no: without the capability nothing is collected, enqueued or printed.
For the logged-in admin the plugin adds one fast SQL aggregate. Query logging is
active only when the site administrator has explicitly enabled `SAVEQUERIES`.

### Who can see the overlay?

Users with the `manage_options` capability. Change it with the `arvexa_performance_overlay_capability`
filter.

### Does it work in the admin area?

Yes — the panel is available on both frontend and admin pages. Browser metrics like
LCP are most meaningful on the frontend.

### Is any data sent anywhere?

No. Everything is measured and displayed in your browser on your own site. Arvexa
Performance Overlay makes no external requests.

## 使用者評論

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

## 參與者及開發者

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

參與者

 *   [ balloodn ](https://profiles.wordpress.org/balloodn/)

[將〈Arvexa Performance Overlay〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/arvexa-performance-overlay)

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

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

## 變更記錄

#### 1.0.2

 * Compatibility release for WordPress 7.1.

#### 1.0.1

 * Compatibility release for WordPress 7.0. Updated the required PHP version metadata
   to match WordPress core.

#### 1.0.0

 * Initial public release.
 * Server metrics: PHP time, SQL count/time, memory, enqueued assets, autoload size,
   longest lifecycle phase.
 * Per-plugin/theme cost attribution (SQL via backtrace, assets via Resource Timing).
 * Web Vitals: LCP + LCP element, CLS, INP, TTFB, DOM nodes, long tasks.
 * Client-side AJAX/REST timing.
 * Slowest queries list.
 * Extension API for add-ons (`arvexa_performance_overlay_data` filter, `window.
   ArvexaPerformanceOverlay` JS API).

## 中繼資料

 *  版本 **1.0.2**
 *  最後更新 **7 小時前**
 *  啟用安裝數 **少於 10 次**
 *  WordPress 版本需求 ** 5.3 或更新版本 **
 *  已測試相容的 WordPress 版本 **7.1**
 *  PHP 版本需求 ** 7.4 或更新版本 **
 *  語言
 * [English (US)](https://wordpress.org/plugins/arvexa-performance-overlay/)
 * 標籤:
 * [debug](https://tw.wordpress.org/plugins/tags/debug/)[performance](https://tw.wordpress.org/plugins/tags/performance/)
   [profiler](https://tw.wordpress.org/plugins/tags/profiler/)[web vitals](https://tw.wordpress.org/plugins/tags/web-vitals/)
 *  [進階檢視](https://tw.wordpress.org/plugins/arvexa-performance-overlay/advanced/)

## 評分

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

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

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

## 參與者

 *   [ balloodn ](https://profiles.wordpress.org/balloodn/)

## 技術支援

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

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