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:
- Dominant Color: Adds support to store dominant color for an image and create a placeholder background with that color.
- WebP Support Health Check: Adds a WebP support check in Site Health status.
- WebP Uploads: Creates WebP versions for new JPEG image uploads if supported by the server.
- Fetchpriority: Adds a fetchpriority hint for the primary content image on the page to load faster.
- Enqueued Assets Health Check: Adds a CSS and JS resource check in Site Health status.
- Autoloaded Options Health Check: Adds a check for autoloaded options in Site Health status.
- SQLite Integration: Use an SQLite database instead of MySQL.
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?
Feedback is encouraged and much appreciated, especially since this plugin is a collection of future WordPress core features. If you have suggestions or requests for new features, you can submit them as an issue in the Performance Lab GitHub repository. If you need help with troubleshooting or have a question about the plugin, please create a new topic on our support forum.
Where can I report security bugs?
The Performance team and WordPress community take security bugs seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
To report a security issue, please visit the WordPress HackerOne program.
How can I contribute to the plugin?
Contributions are always welcome! Learn more about how to get involved in the Core Performance Team Handbook.
I’ve activated the WebP Uploads module, but WebP images are not always generated when I upload a JPEG image. Why?
There are two primary reasons that a WebP image may not be generated:
- Performance Lab has identified that the WebP version of the uploaded JPEG image would have a larger file size than the original JPEG image, so it does not generate the WebP version.
- The JPEG image was not uploaded to the Media Library. At this time, WebP versions are only generated for images to the Media Library. WebP versions are not generated for JPEG images that are added to your site in other ways, such as in a template file or the Customizer.
With the WebP Uploads module activated, will the plugin generate JPEG and WebP versions of every image that I upload?
By default, the WebP Uploads module will only generate WebP versions of the images that you upload. If you wish to have both WebP and JPEG versions generated, you can navigate to Settings > Media and enable the Generate JPEG files in addition to WebP option.
Autori un izstrādātāji
“Performance Lab” ir atvērtā pirmkoda programmatūra. Šo spraudni ir veidojuši šādi cilvēki.Līdzdalībnieki
“Performance Lab” ir tulkots lokalizācijās 17. Paldies tulkotājiem par ieguldījumu.
Tulkot “Performance Lab” savā valodā.
Vai jūs interesē attīstība?
Pārlūkojiet kodu, apmeklējiet SVN krātuvi vai abonējiet attīstības žurnālu, ko izveidojis RSS.
- Infrastructure: Add
wp-totalmetric to default Server-Timing metrics. (669)
- Infrastructure: Ensure module
load.phpfiles really only load other code to prevent conflicts in standalone plugins. (674)
- Infrastructure: Fix problems with placing
- Object Cache: Update WordPress version to 6.1 and remove Cache modules. (641)
- Measurement: Add
- Database: Add an indicator in the adminbar to show when using SQLite. (604)
- Images: Check for existing
$metadata['sizes']to fix PHP warning. (648)
- Images: Use correct number of arguments in filter callback. (634)
- Database: Fix invalid docs and return types as highlighted by static analysis. (645)
- Infrastructure: Fix incorrect usage of
- Infrastructure: Add file header to object-cache drop-in to clarify purpose. (649)
- Database: Remove warning about multi-server environment from the SQLite module description. (619)
- Infrastructure: Enhance object-cache.php drop-in interoperability with other plugins. (616)
- Measurement: Implement Server-Timing API foundation as well as basic load time metrics. (553)
- Database: Implement new experimental SQLite integration module. (547)
- Images: Implement new experimental
- Database: Fix SQLite notices related to undefined properties. (600)
- Database: Fix incorrect handling of
admin_emailand actual admin user’s email when original
admin_emailuser was deleted. (603)
- Database: Make WP filesystem setup more robust to prevent potential errors. (595)
- Images: Change WP Image editor quality for mime types. (571)
- Images: Avoid potentially adding invalid attributes or duplicates for dominant color images. (578)
- Images: Fix fatal error in REST API response when an image has no attachment metadata. (568)
- Images: Fix image focal point bug when dominant color is enabled by not overriding
- Images: Fix opt-in checkbox for generating WebP and JPEG to also show on Multisite. (565)
- Site Health: Only load Site Health checks for persistent cache and full page cache when not available in core. (543)
- Images: Add checkbox to Settings > Media to control whether to generate JPEG in addition to WebP. (537)
- Images: Generate only WebP images by default for JPEG and WebP uploads. (527)
- Infrastructure: Bump minimum WordPress requirement to 6.0. (549)
- Site Health: Improve autoloaded options check by highlighting largest autoloaded options. (353)
- Images: Enhance JS replacement mechanism for WebP to JPEG to more reliably replace full file name. (443)
- Images: Introduce
webp_uploads_get_content_image_mimes()to get content image MIME replacement rules. (420)
- Infrastructure: Add
- Infrastructure: Rename Site Health check modules for language and consistency. (423)
- Site Health: Fix incorrect usage of badge colors in all Site Health checks. (472)
- Images: Add the original image’s extension to the WebP file name to ensure it is unique. (444)
- Images: Fix REST API support for plain permalinks. (457)
- Infrastructure: Remove plugin option network-wide for Multisite during uninstall. (458)
- Images: Add replacing of images only in frontend context. (424)
- Images: Allow control for which image sizes to generate additional MIME type versions. (415)
- Images: Discard WebP image if it is larger than corresponding JPEG image. (418)
- Images: Optimize computing dominant color and transparency for images by combining the two functions. (381)
- Images: Provide fallback JPEG images in frontend when WebP is not supported by the browser. (360)
- Images: Rely on
wp_get_image_editor()methods argument to check whether it supports dominant color methods. (404)
- Images: Remove experimental label from Dominant Color module and turn on by default for new installs. (425)
- Site Health: Remove
perflab_aea_get_resource_file_size()in favor of
- Site Health: Update documentation link for autoloaded options. (408)
- Infrastructure: Implement mechanism to not load module if core version is available. (390)
- Images: Ensure incorrect usage of
webp_uploads_upload_image_mime_transformsfilter is treated correctly. (393)
- Images: Fix PHP notice and bug in logic for when
webp_uploads_prefer_smaller_image_filefilter is set to
- Images: Fix an infinite loop in the WebP fallback mechanism. (433)
- Images: Fix dominant color upload process to not override potential third-party editors. (401)
- Images: Remove additional image backup sources & sizes files when attachment deleted. (411)
- Infrastructure: Avoid including .husky directory in plugin ZIP. (421)
- Infrastructure: Do not show admin pointer in multisite Network Admin. (394)
- 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)