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.

Sign up for GitHub

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

Jump to bottom

[CHORE] - Investigate Lighthouse Reports & SEO #50

Open
jaspermayone opened this issue Apr 15, 2024 · 0 comments
Open

[CHORE] - Investigate Lighthouse Reports & SEO #50

jaspermayone opened this issue Apr 15, 2024 · 0 comments
Labels
💻 aspect: code Related to code implementation or modification. ✨ goal: improvement Related to general improvements or enhancements. 🏁 status: ready for dev Ready for development work.

Comments

@jaspermayone
Copy link
Member

What work needs to be performed?

Please investigate SEO & Chrome Lighthouse scores for purplebubble.org. (See attached photos)

CleanShot 2024-04-15 at 11 26 34@2x
CleanShot 2024-04-15 at 11 27 16@2x
CleanShot 2024-04-15 at 11 27 34@2x
CleanShot 2024-04-15 at 11 28 01@2x

Lighthouse full report also attached in additional information field.

Additional information

Would also be good to install some sort of workflow/action for these scores, to get results for each PR as to be able to prevent things making it into production.

Full Lighthouse Report for Purple Bubble.pdf
@jaspermayone jaspermayone added ✨ goal: improvement Related to general improvements or enhancements. 🏁 status: ready for dev Ready for development work. 💻 aspect: code Related to code implementation or modification. labels Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💻 aspect: code Related to code implementation or modification. ✨ goal: improvement Related to general improvements or enhancements. 🏁 status: ready for dev Ready for development work.
Projects
Purple Bubble
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jaspermayone @kcoderhtml