WordPress.org

Make WordPress Core

Opened 4 months ago

Last modified 4 months ago

#53186 new feature request

Site Health plugin extension for the performance score

Reported by: oglekler Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Site Health Keywords:
Focuses: performance Cc:

Description

To make users able to check the impact of plugins and themes and see if their usage is worth it or not we need an additional plugin with a connection to the repo, like an extension for Site Health (Jeff Paul suggested that it looks like a Site Health related).

The "message" of the Site Health extension can be:

  1. Check your site performance
  2. Get results (and act)
  3. Share information (purely related to plugins execution without any personal or domain-related data) with the repository to give plugins you are using a performance score.

Why we need to check performance:

Plugins (and themes) can be heavy and make a huge impact on site performance for small enhancement site owner wants.

I proposed to add a performance index to plugins and themes on the repo:

https://meta.trac.wordpress.org/ticket/5731

But there is no way to get actual data, especially for plugins, without real websites, so, it looks like the only way to get real information about plugins' performance is from sites owners and their own free will.

Change History (2)

#1 @tomjdevisser
4 months ago

I love this idea, mainly because every optimization actually helps with a more sustainable future (https://www.youtube.com/watch?v=lFpxE59YU1Q&t=19s). Maybe it's possible to add a step when reviewing plugins that get committed to the repo, where we check:

  • If it enqueues auto generated minified files;
  • How many files get enqueued;
  • Do a quick speedtest on an empty WordPress install;
  • etc.

They have to be checks that can be automated though, otherwise we'd have to check all plugins after every update they release.

This ticket was mentioned in Slack in #core by oglekler. View the logs.


4 months ago

Note: See TracTickets for help on using tickets.