WordPress / WordPress/performance

Improve Enqueued Assets report in Site Health

Open
#267 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Plugin] Performance Lab [Type] Enhancement
Dominant language
PHP
Stars
461
Forks
165
Avg merge
11h 12m
Merged PRs (30d)
28

Description

The current Site Health reports for the Enqueued Assets module, introduced in #25, do not include actionable information for users about how to address a site loading too many enqueued assets. As noted by @felixarntz here:

We also need to think about how to make this warning more actionable, e.g. at a minimum tell users which plugins or themes are responsible for enqueuing the majority of assets etc.

Suggestions for changes (in progress) are below.

Enqueued scripts

If acceptable
image

Current description: The amount of [#] enqueued scripts (size: [size]) is acceptable.

New description:

If not acceptable
image

Current description: Your website enqueues [#] scripts (size: [size]). Try to reduce the number or to concatenate them.

More info about performance optimization

Clean Test Cache

New description:

Enqueued styles

If acceptable
image

Current description: The amount of [#] enqueued styles (size: [size]) is acceptable.

New description:

If not acceptable
image

Current description: Your website enqueues [#] styles (size: [size]). Try to reduce the number or to concatenate them.

More info about performance optimization

Clean Test Cache

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Enqueued Assets module's Site Health reports for enqueued scripts and styles, then review the existing descriptions and the context from issue #25. Done means the acceptable and unacceptable reports provide actionable guidance, including which plugins or themes contribute most assets, with updated tests for both scripts and styles.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.