Unused json and js files after gatsby build (Google pagespeed)

[Jornve]

Hi guys!

When validating our new Gatsby website with PageSpeed Insights our score dropped significantly due to unused json and js files. Anyone had this issue before and/or know how to solve this?

[sidharthachatterjee]

@Jornve These warnings are displayed when some assets that are preloaded in the browser are not eventually used.

Gatsby preloads assets for pages that are linked to in the viewport — so the page loads practically instantly when the user clicks on the link. In this case, the PageSpeed Insights test is likely not navigating through to multiple pages and therefore this warning is being thrown.

I would say that it's okay to ignore these warnings but keeping this open to hear what others have to say on this issue.

[pgilad]

According to @addyosmani answer here (GoogleChromeLabs/preload-webpack-plugin#8 (comment)) it seems the correct method of loading assets from another page is prefetch and not preload

[KyleAMathews]

What site is this? Gatsby adds preload links to SSRed HTML for the initial critical resources. We do use prefetch for prefetching subsequent resources.

I haven't seen this error before. How much JS are you loading initially?

[Jornve]

@KyleAMathews Here is a preview link: https://5c6a83cd7cf4c1000bf91a3f--amazing-pare-38b4d5.netlify.com/

I do have to mention that we don't have a score drop when testing with Lighthouse. For some reason these tools are not fully in sync.

[rshackleton]

Seeing the same preload warnings on PSI for my own website: https://rshackleton.co.uk/

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!

[jackyef]

Bump! Seeing this issue as well on my site powered by gatsby.

[ghassanmas]

+1 for having this issue as well

[lnikell]

Same for me