The Performance Lab plugin is a collection of modules focused on enhancing performance of your site, most of which should eventually be merged into WordPress core. The plugin allows to individually enable and test the modules to get their benefits before they become available in WordPress core, and to provide feedback to further improve the solutions.
Currently the plugin includes the following performance modules:
- WebP Uploads: Creates WebP versions for new JPEG image uploads if supported by the server.
- Dominant Color: Adds support to store dominant color for an image and create a placeholder background with that color.
- Audit Full Page Cache: Adds a check for full page cache in Site Health status.
- WebP Support: Adds a WebP support check in Site Health status.
- Audit Autoloaded Options: Adds a check for autoloaded options in Site Health status.
- Audit Enqueued Assets: Adds a CSS and JS resource check in Site Health status.
- Persistent Object Cache Health Check: Adds a persistent object cache check for sites with non-trivial amounts of data in Site Health status.
Installation from within WordPress
- Visit Plugins > Add New.
- Search for Performance Lab.
- Install and activate the Performance Lab plugin.
- Upload the entire
performance-labfolder to the
- Visit Plugins.
- Activate the Performance Lab plugin.
- Visit the new Settings > Performance menu.
- Enable the individual modules you would like to use.
What is the purpose of this plugin?
The primary purpose of the Performance Lab plugin is to allow testing of various performance modules for which the goal is to eventually land in WordPress core. It is essentially a collection of “feature plugins”, which makes it different from other performance plugins that offer performance features which are not targeted at WordPress core and potentially rely on functionality that would not be feasible to use in WordPress core. The list of available modules will regularly change: Existing modules may be removed after they have been released in WordPress core, while new modules may be added in any release.
Can I use this plugin on my production site?
Per the primary purpose of the plugin (see above), it can mostly be considered a beta testing plugin for the various performance modules it includes. However, unless a module is explicitly marked as “experimental”, it has been tested and established to a degree where it should be okay to use in production. Still, as with every plugin, you are doing so at your own risk.
Where can I submit my plugin feedback?
Especially since this is a collection of WordPress core feature plugins, providing feedback is encouraged and much appreciated! You can submit your feedback either in the plugin support forum or, if you have a specific issue to report, in its GitHub repository.
How can I contribute to the plugin?
Contributions welcome! There are several ways to contribute:
Contributors & Developers
“Performance Lab” is open source software. The following people have contributed to this plugin.Contributors
- Images: Add Dominant Color module to provide color background for loading images. (282)
- Site Health: Add Site Health check for Full Page Cache usage. (263)
- Images: Update
webp_uploads_pre_generate_additional_image_sourcefilter to allow returning file size. (334)
- Infrastructure: Introduce plugin uninstaller routine. (345)
- Infrastructure: Use
filesizeif available. (376)
- Images: Avoid overwriting existing WebP files when creating WebP images. (359)
- Images: Back up edited
fullimage sources when restoring the original image. (314)
- Infrastructure: Add Performance Lab generator meta tag to
- Images: Introduce filter
webp_uploads_pre_generate_additional_image_sourceto short-circuit generating additional image sources on upload. (318)
- Images: Introduce filter
webp_uploads_pre_replace_additional_image_sourceto short-circuit replacing additional image sources in frontend content. (319)
- Images: Refine logic to select smaller image file in the frontend based on
- Images: Replace the featured image with WebP version when available. (316)
- Site Health: Update Site Health Autoloaded options documentation link. (313)
- Infrastructure: Avoid unnecessarily early escape of Site Health check labels. (332)
- Object Cache: Correct label for persistent object cache Site Health check. (329)
- Images: Only update the specified target images when an image is edited. (301)
- Images: Generate secondary image MIME types when editing original image. (235)
- Images: Introduce
webp_uploads_prefer_smaller_image_filefilter allowing to opt in to preferring the smaller image file. (287)
- Images: Select MIME type to use in frontend content based on file size. (243)
- Site Health: Update Site Health reports copy for more clarity and consistency. (272)
- Infrastructure: Define the plugin’s version support and backward compatibility policy. (240)
- Images: Change expected order of items in the
- Images: Replace images in frontend content without using an additional regular expression. (262)
- Images: Restore and backup image sizes alongside the sources properties. (242)
- Images: Select image editor based on WebP support instead of always using the default one. (259)
- Infrastructure: Ensure default modules are loaded regardless of setting registration. (248)
- Images: Create additional MIME types for the full size image. (194)
- Site Health: Add module to warn about excessive amount of autoloaded options. (124)
- Images: Adds sources information to the attachment media details of the REST response. (224)
- Images: Allow developers to select which image format to use for images in the content. (230)
- Images: Allow developers to tweak which image formats to generate on upload. (227)
- Images: Replace the full size image in
the_contentwith additional MIME type if available. (195)
- Object Cache: Include
memcachedextension in checks for object cache support. (206)
- Infrastructure: Add plugin banner and icon assets. (231)
- Infrastructure: Use
.distignoreto better support ZIP creation. (223)
- Images: Use
originalimage to generate all additional image format sub-sizes. (207)
- Infrastructure: Replace unreliable activation hook with default value for enabled modules. (222)
- Infrastructure: Update release instructions to include proper branching strategy and protect release branches. (221)
- Images: Add WebP for uploads module. (32)
- Images: Support retry mechanism for generating sub-sizes in additional MIME types on constrained environments. (188)
- Images: Update
the_contentwith the appropiate image format. (152)
- Site Health: Add WebP support in site health. (141)
- Site Health: Add module to alert about excessive JS and CSS assets. (54)
- Object Cache: Add Site Health check module for persistent object cache. (111)
- Infrastructure: Add settings screen to toggle modules. (30)
- Infrastructure: Added admin pointer. (199)
- Object Cache: Always recommend object cache on multisite. (200)
- Images: Create image sub-sizes in additional MIME types using
sourcesfor storage. (147)
- Images: Update module directories to be within their focus directory. (58)
- Site Health: Enhance detection of enqueued frontend assets. (136)
- Infrastructure: Add link to Settings screen to the plugin’s entry in plugins list table. (197)
- Infrastructure: Enable all non-experimental modules on plugin activation. (191)
- Infrastructure: Include generated module-i18n.php file in repository. (196)
- Infrastructure: Introduce
perflab_active_modulesfilter to control which modules are active. (87)
- Infrastructure: Remove unnecessary question marks from checkbox labels. (110)
- Infrastructure: Rename
- Images: Ensure the
-scaledimage remains in the original uploaded format. (143)
- Images: Fix typo to access to the correct image properties. (203)
- Infrastructure: Ensure that module header fields can be translated. (60)
- Site Health: Mark Site Health Audit Enqueued Assets module as experimental for now. (205)
- Infrastructure: Add
readme.txtand related update script. (72)
- Infrastructure: Add changelog generator script. (51)
- Infrastructure: Add contribution documentation. (47)
- Infrastructure: Add release documentation. (138)
- Infrastructure: Define module specification in documentation. (26)