Improve Lighthouse score
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 233
- Forks
- 61
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
Follow-up of https://github.com/mdn/yari/issues/4060.
As of 2022-11-28, MDN has the following scores (in Chrome 107 on Mac OS, using Incognito mode):
Desktop
Mobile
Performance (62/100)
Opportunities
- Eliminate render-blocking resources (1.94s)
- Reduce unused JavaScript (0.3s)
- Reduce unused CSS (0.15s)
Diagnostics
- Avoid an excessive DOM size (3,312 elements)
- Serve static assets with an efficient cache policy (8 resources found)
- Minimize main-thread work (2.5s)
Accessibility (91/100)
- Buttons do not have an accessible name
- Heading elements are not in a sequentially-descending order
Best Practices (92/100)
- Browser errors were logged to the console
SEO (92/100)
- Links do not have descriptive text
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified. Start by running Lighthouse against the documented MDN page and compare the current Performance, Accessibility, Best Practices, and SEO findings with this report; done means addressing the listed findings and verifying improved scores.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend, performance, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100