Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize frontend resources for performance #332

Open
adamwoodnz opened this issue Oct 15, 2023 · 2 comments · May be fixed by #339
Open

Optimize frontend resources for performance #332

adamwoodnz opened this issue Oct 15, 2023 · 2 comments · May be fixed by #339
Assignees

Comments

@adamwoodnz
Copy link
Contributor

There are a lot of unused style resources being loaded on the homepage which are affecting performance, and are highlighted in the LCP metric of pagespeed/lighthouse tests:

Screenshot 2023-10-16 at 9 20 48 AM

This likely affects other pages too. Work has been done in Showcase to stop loading these resources, and we can follow this approach in this theme.

We could consider a mu-plugin solution which stops certain resources being loaded across the network, on a page-by-page basis.

@adamwoodnz adamwoodnz moved this to 📋 To do in WordPress.org Redesign Oct 15, 2023
@adamwoodnz adamwoodnz moved this from 📋 To do to 🏗 In progress in WordPress.org Redesign Oct 27, 2023
@adamwoodnz adamwoodnz self-assigned this Oct 27, 2023
@adamwoodnz adamwoodnz linked a pull request Oct 27, 2023 that will close this issue
@adamwoodnz adamwoodnz moved this from Todo to In Progress in @adamwoodnz's WIP Oct 27, 2023
@adamwoodnz
Copy link
Contributor Author

Noting that dashicons CSS is required for some pages like /about/stats, and had to be explicitly loaded with WP 6.5, see #354

@ryelle
Copy link
Contributor

ryelle commented Apr 2, 2024

I've pulled this & the corresponding draft PR out of the "redesign" board since there hasn't been activity on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

2 participants