See #1031 (comment): We should revisit our current standalone plugins' names and descriptions for how accurate and useful they are. In particular, we should consider the following:

• Plugin names and descriptions are used to describe features within Performance Lab.
• Our plugins are not products. They are features for WordPress core. As such, we should avoid plugin names that sound too much like a product / brand name, and instead simply find a good name that clarifies the feature. Example: "Optimization Detective" doesn't clarify what it does.
• Additionally, we should avoid technicalities in the name, to make them intuitive. Example: "WebP Uploads" would probably be better as something like "WebP Images" (the term "Uploads" is only used because of Media Library jargon). "Speculation Rules" should probably be something like "Speculative preloading" because the Speculation Rules API is a technical detail.
• Plugin descriptions should not mention the word "plugin". They can just start with a third-person verb (e.g. "Adds xyz" or similar).

For reference, here are our current plugin names and descriptions to review:

• Auto-sizes for Lazy-loaded Images
  • This plugin implements the HTML spec for adding sizes="auto" to lazy-loaded images.
• Dominant Color Images
  • Adds support to store the dominant color of newly uploaded images and create a placeholder background of that color.
• Optimization Detective
  • Improves accuracy of optimizing the loading of the LCP image by leveraging client-side detection with real user metrics. Also enables output buffering of template rendering which can be filtered.
• Performant Translations
  • Making internationalization/localization in WordPress faster than ever before.
• Speculation Rules
  • Uses the Speculation Rules API to prerender linked URLs upon hover by default.
• WebP Uploads
  • Creates WebP versions for new JPEG image uploads if supported by the server.

Let's brainstorm.

cc @adamsilverstein @joemcgill @mukeshpanchal27 @swissspidy @westonruter