Skip to content

Standardize structure for Site Health reports #229

@mitogh

Description

@mitogh

Feature Description

Currently, there's no clear definition in how some things are helpful for performance and why others are being measured, setting a standard by answering a set of predetermined questions would help in making sure the metrics are meaningful for the majority of users and not just technical users.

  • Why this measure is being tracked? Answer this question in a clear way would help to understand the need to pass this test for example:

2022-03-14_18-11

The metric above does not indicate why I need to keep WordPress up to date.

  • Why I need to pass that metric? or How the metric would help improve my performance? Example:

2022-03-14_18-11

What's the benefit of passing this test or keeping up to date with WordPress as a site owner what are the risk and benefits of going down this route? Is there any tradeoff If I decided not to?

Avoid technical wording if possible

2022-03-14_18-26

This example is missing some answers for the questions above, but also includes additional wording that might not be explicit for the vast majority of users.

Metadata

Metadata

Assignees

Labels

[Type] EnhancementA suggestion for improvement of an existing feature

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions