Lighthouse audit problem with Gatsby image.
See original GitHub issueSummary
I get performance score of 84-89 for my home page using Lighthouse audits. It is showing a problem saying: “Properly size images: Serve images that are appropriately-sized to save cellular data and improve load time.”
Relevant information
Gatsby Image fluid is used with both minWidth and maxWidth provided to maintain aspect ratio.
Environment (if relevant)
Not relevant
File contents (if changed)
gatsby-config.js
: N/A
package.json
: N/A
gatsby-node.js
: N/A
gatsby-browser.js
: N/A
gatsby-ssr.js
: N/A
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:24 (8 by maintainers)
Top Results From Across the Web
Image Optimization in Gatsby after bad Lighthouse audit
Lighthouse audit. Now, one of the main reason is large images. All of the images(more then 2k) inside blogs comes from, two powerful...
Read more >Image Optimization in Gatsby after bad Lighthouse audit
I will soon load small size files from them. Culprit images. But the real issue, as from above screenshot are the book image...
Read more >How to Improve Website Lighthouse Scores - Gatsby
Using gatsby-plugin-image can increase Lighthouse scores by 10-15 points for pages with large images. Trim Bloated Bundles: Gatsby breaks your ...
Read more >How I got perfect Google Lighthouse score with Gatsby
If the background uses an image or animated css, lighthouse may not decide contrast ratio. In this case, the audit will be failed...
Read more >How I Got a Perfect Google Lighthouse Score Using GatsbyJS
You can kick off a Lighthouse audit directly from the Chrome developer ... Image of the Google Lighthouse Score Results For This Page....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Regarding comment above by @JordanHoffman and @benbehringer - I’m also still getting blur-up effect with GatsbyImageSharpFluid_withWebp_noBase64. On the upside, the LCP hit is apparently something that’s being worked on in Lighthouse so I’m not going to fuss about it too much.
See: Kyle Mathews comment: https://github.com/gatsbyjs/gatsby/issues/24332#issuecomment-650799066 Twitter exchange between KM and Lighthouse dev: https://twitter.com/addyosmani/status/1277293541878673411 Issue tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1045640
Closing this for now. I will open a new one when I encounter this issue again.