question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lighthouse: preload key requests warning

See original GitHub issue

Bug report

Describe the bug

I’m getting warnings when running LH tests with regards to preload keys and can’t seem to figure out how to troubleshoot.

There’s an closed ticket in #16932 that has asked to create new issues for Next ^10.

Lighthouse report: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fhome-point-financial.vercel.app%2F

Screenshots

A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.
A preload <link> was found for "***" but was not used by the browser. Check that you are using the `crossorigin` attribute properly.

System information

  • Version of Next.js: 10.0.1
  • CSS: Chakra 1.0.1
  • Deployment: Vercel

Additional context

I’m using Chakra as my UI library, so not sure if this is an issue related to that project.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:7
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
jacobarriolacommented, Dec 6, 2020

Sorry that I didn’t respond in time. I can’t create a reproduction, so there’s probably something unique about my project that’s causing the issue. If I nail something down, I’ll report it here with a full reproduction. Thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to correct "preload key requests" performance problem ...
When I use lighthouse, I see big opportunities of performance: "Preload Key requests" with these warnings: A preload was found for ".../js/chunk ...
Read more >
Preload key requests - Chrome Developers
The Opportunities section of your Lighthouse report flags the third level of requests in your critical request chain as preload candidates:.
Read more >
Try to fix Preload Key Requests now big troublw - WordPress.org
Check that you are using the crossorigin attribute properly. Ensure text remains visible during webfont load. Warnings: Lighthouse was unable to automatically ...
Read more >
Preload critical assets to improve loading speed - web.dev
Lighthouse's preload key requests audit. ... Unused preloads trigger a Console warning in Chrome, approximately 3 seconds after the load ...
Read more >
[FIXED] Preload Key Requests WordPress Plugin - 3 Easy ...
It is pretty easy to fix the preload key requests WordPress warning with a plugin. This will take away the need of writing...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found