TinySharp Performance Diagnostics
| 开发者 | tinysharp |
|---|---|
| 更新时间 | 2026年9月3日 22:52 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
TinySharp Performance Diagnostics is a read-only WordPress performance diagnostic plugin built around one simple question: what is actually taking time?
TinySharp Performance Diagnostics runs three local diagnostic requests against your homepage, WP Admin dashboard or a chosen same-site frontend URL and uses the median result. It measures server processing, database work, PHP memory, autoloaded options, outgoing HTTP requests, major WordPress lifecycle phases and directly timed callbacks on important hooks.
Measured evidence is translated into conservative plain-English next steps. Reports remain stored locally on the site.
The plugin does not create an account, send diagnostic reports to TinySharp or load remote code. During a scan, WordPress makes temporary loopback requests to the selected URL on the same website so the request can be measured.
Current features:
- Homepage, WP Admin and same-site Custom URL scan targets
- Separate local history for every target and Custom URL
- 3-run median diagnostic scan
- Performance health score
- Separate diagnostic coverage percentage
- Timed hook callback attribution
- Database caller attribution
- External HTTP caller attribution
- Top measured contributors from directly measured evidence
- Evidence-based Recommended next steps
- Request lifecycle timeline
- Memory usage relative to PHP memory_limit
- Autoloaded option size
- Last 10 scans stored locally and non-autoloaded
- Read-only normal scans; no plugin is globally disabled TinySharp Performance Diagnostics separates measured work from conclusions. It does not recommend deleting or deactivating a plugin automatically.
安装:
- Upload the plugin ZIP in Plugins > Add New > Upload Plugin.
- Activate TinySharp Performance Diagnostics.
- Open Tools > TinySharp Performance Diagnostics.
- Click Run Performance Scan.
屏幕截图:
常见问题:
Does the scan change plugin activation?
No. Scans observe the current request and do not activate, deactivate or omit plugins.
Do I have to scan every time I open the page?
No. The last 10 completed reports are saved locally. Your latest result opens automatically and you can run a new scan whenever you want.
Does scan history leave my website?
No. Scan history is stored locally in a non-autoloaded WordPress option.
What happens to saved data when I remove the plugin?
Deactivation keeps saved reports. Uninstalling and deleting TinySharp Performance Diagnostics removes its local scan history.
Does the plugin send telemetry or diagnostic data to TinySharp?
No. The plugin has no telemetry, account connection or TinySharp API request. Scan reports remain in the local WordPress database until they are cleared or the plugin is uninstalled.
Will TinySharp Performance Diagnostics tell me to delete a slow plugin?
No. A plugin may be doing important work. The action plan recommends investigation, configuration changes, retesting or alternatives where evidence supports it, but it does not automatically recommend deletion/deactivation.
更新日志:
1.0.0
- Initial public release.
- Added homepage, authenticated WP Admin and same-site Custom URL diagnostics.
- Added three-run median reports, health score and diagnostic coverage.
- Added hook, database, HTTP, memory and autoload attribution.
- Added conservative evidence-based next steps and complete local-data cleanup on uninstall.
- Added translator context for every recommendation containing placeholders.
- Added ordered placeholders where translators may need to reorder numeric values.
- Documented intentional nonce-token, database, backtrace and filesystem profiler operations for code-quality checks.
- Removed development-only Markdown files from the production package.
- Hardened loopback requests so redirects are not followed beyond the selected target.
- Added complete temporary-token cleanup for failed and incomplete scans.
- Added safer authenticated WP Admin cookie handling.
- Added complete temporary-token and local-history cleanup.
- Removed placeholder release metadata and localized additional interface messages.
- Added Homepage, WP Admin and same-site Custom URL scan targets.
- Added same-site URL validation to block external scan targets.
- Added separate last-10 history for each scan target and Custom URL.
- Added target identity and URL to saved reports and history.
- Added timing coverage for major wp-admin hooks.
- Added local history for the last 10 completed scans.
- Latest report now appears automatically without rescanning.
- Added PHP/hook callback timing on major WordPress lifecycle hooks.
- Added callback-to-component attribution with confidence levels.
- Added Top measured contributors.
- Added Diagnostic Coverage separate from the performance score.
- Added 3-run median scans, database/HTTP attribution and request timeline.
- Added initial caller evidence attribution.