Arvexa Performance Overlay
| 开发者 |
arvexa
balloodn |
|---|---|
| 更新时间 | 2026年7月21日 05:19 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- 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.
- Per-query plugin attribution uses the
log_query_custom_datafilter 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 adddefine( 'SAVEQUERIES', true );towp-config.phpbefore 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_dataPHP filter and thewindow.ArvexaPerformanceOverlayJS API.
安装:
- Upload the
arvexa-performance-overlayfolder to/wp-content/plugins/, or install through the WordPress plugin screen. - Activate the plugin.
- 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.
- 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.
更新日志:
- 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_datafilter,window.ArvexaPerformanceOverlayJS API).