Linux 软件免费装
Banner图

Footprint - Find what slows your site

开发者 byus
更新时间 2026年7月21日 05:10
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

speed performance page speed profiler performance optimization

下载

0.23.1

详情介绍:

Footprint is a performance profiler that tells a WordPress administrator which plugins and which theme have the highest impact on the performance of a given page — and what to do about it. A lighter site is also a more sober site, both for your visitors and for the planet. Unlike profilers built for developers (Query Monitor, Code Profiler), Footprint is decision-oriented. In thirty seconds you should know: When you re-scan the same URL, the report shows what changed since the previous scan: score, server time, memory, SQL, external calls — and the components whose impact moved most. How it works Footprint runs a differential scan: it loads the target URL once with everything active (baseline) and once per plugin with that plugin disabled — for the duration of a single internal HTTP request only. The difference between the two runs gives a real measurement of that plugin's footprint, not an estimation. A small must-use plugin loader performs the per-request swap. You install it in one click the first time you scan (it lives in wp-content/mu-plugins/, outside this plugin's folder, and is removed on uninstall). Nothing is changed in your database. The whole report you see on screen is computed locally on your server: the per-component impact on time, memory, SQL and assets, the ranking of the heaviest components, and the optimization advice. The plugin is fully functional on its own. The only thing that needs the Footprint Pulse service is the A-E Footprint Score, which compares your result against the anonymized measurements of thousands of other sites and cannot be computed locally. Honesty about limits Footprint provides estimated measurements where exact attribution is impossible. WordPress loads the core, plugins and theme inside the same PHP process, which makes perfect per-plugin memory attribution unreliable. The differential scan greatly improves the signal but it is still subject to: The report flags any of these conditions when detected. Privacy Footprint includes a community ranking called Footprint Pulse. Sharing is on by default and can be turned off any time in Settings. The plugin's local report, per-component impact and recommendations work exactly the same either way. The only thing sharing adds is the community A-E Footprint Score described above. When sharing is enabled, after each scan the plugin sends to https://www.wpfootprint.com: What is not sent: the URL of your pages, your content, visitor data, IP addresses, cookies, user accounts, database content, API keys, file paths, server hostnames. On first enrollment only, your domain is sent once so Pulse can call back into your WordPress AJAX endpoint to verify a cryptographic signature that proves you own the site. The domain is kept on the server for audit and re-verification, never displayed publicly, and never attached to your scans. Third-party services This plugin transmits data to Footprint Pulse (https://www.wpfootprint.com), a service operated by ByUs for the purpose described in the Privacy section above. As stated above, sharing is enabled by default and can be turned off at any time from the in-plugin Settings panel — disabling it stops the network call entirely.

安装:

  1. Upload the plugin to your /wp-content/plugins/ directory.
  2. Activate Footprint through the Plugins menu in WordPress.
  3. Go to Tools > Footprint and click Analyse the home page, or enter an internal URL to scan.
The first time you run a scan, Footprint asks you to install a small PHP file (a must-use plugin) into wp-content/mu-plugins/ (outside the plugin folder). The file is shipped with the plugin, is added only after you click to confirm, is required for the differential scan, and is automatically removed when Footprint is deactivated.

常见问题:

Is the differential scan safe to run on a production site?

It performs only HTTP GET requests against your own URLs. No options or posts are modified. However, on a heavily used production site the burst of N+1 requests may briefly spike PHP-FPM workers and could be noticed by analytics. Running on staging is recommended.

Why does my scan say "Cache detected"?

Full-page caches (LiteSpeed Cache, Cloudflare APO, page-cache plugins of any kind, etc.) serve the response without invoking PHP, so per-request measurements are unavailable. Footprint detects this and warns you instead of presenting fake numbers.

Why isn't the per-plugin SQL count exact?

The differential subtraction is approximate when plugins share triggers (for example, hitting a page that already cached its query plan). The numbers are good enough to rank plugins but should not be read as exact figures.

更新日志:

0.23.1 0.23.0 0.22.12 0.22.9