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

Lighthouse audit for next.gatsbyjs.org #7378

Closed
m-allanson opened this issue Aug 16, 2018 · 1 comment
Closed

Lighthouse audit for next.gatsbyjs.org #7378

m-allanson opened this issue Aug 16, 2018 · 1 comment
Assignees
Labels
help wanted Issue with a clear description that the community can help with. type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change

Comments

@m-allanson
Copy link
Contributor

Running a lighthouse audit on next.gatsbyjs.org reveals a few issues that could be fixed:

  • Text is invisible while webfonts are loading
  • Uses inefficient cache policy on static assets - most (all?) of these are required.
    • is google tag manager and google analytics required?
    • where does woopra come from?
    • a lot of the docsearch CSS gets overridden, is it possible to reduce the size of that dependency?
  • Links do not have a discernible name
  • Background and foreground colors do not have a sufficient contrast ratio. (copy in @fk before taking this on)
  • Browser errors were logged to the console - this seems like a bug in Gatsby
  • Document does not have a meta description

These could be fixed by updating the site here: https://github.com/gatsbyjs/gatsby/tree/master/www

@m-allanson m-allanson added help wanted Issue with a clear description that the community can help with. type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change labels Aug 16, 2018
@m-allanson
Copy link
Contributor Author

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issue with a clear description that the community can help with. type: maintenance An issue or pull request describing a change that isn't a bug, feature or documentation change
Projects
None yet
Development

No branches or pull requests

1 participant