Requests to /v1/vitals are blocked from web.dev lighthouse run
See original GitHub issueBug report
Describe the bug
When running lighthouse against a next.js site with analytics enabled, it seems like the request for sending web vitals metric are getting blocked.
This is not a major issue, though I couldn’t find any issue mentioning this before, so I thought I would open one up.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Go to https://web.dev
- Test a site with next.js 10 with analytics enabled, for example
https://jackyef.com
- View the lighthouse report
- We should be seeing errors for “Browser errors were logged to the console”
Expected behavior
Analytics XHR requests shouldn’t be blocked.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
PWA Problems only in Lighthouse "Request was blocked by ...
The problem is that when I load the page normally everything works correctly, but when I try to run Lighthouse it hangs and...
Read more >Core Web Vitals workflows with Google tools - web.dev
It presents a Lighthouse report along with pull requests, and tracks performance metrics over time. When to use Lighthouse #. Lighthouse is ...
Read more >Total Blocking Time (TBT) - web.dev
This post introduces the Total Blocking Time (TBT) metric and ... way to measure TBT is to run a Lighthouse performance audit on...
Read more >Performance monitoring with Lighthouse CI - web.dev
Running Lighthouse CI as part of continuous integration; Using a Lighthouse CI GitHub Action that runs and comments on every pull request ......
Read more >What's New in Lighthouse 6.0 - web.dev
New metrics. Largest Contentful Paint (LCP); Cumulative Layout Shift (CLS); Total Blocking Time (TBT) · Performance score update. Shifts in ...
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
I was annoyed with this error until I realised that it was just the ads blocker causing it… 🤦♀️ Note for future visitors: Check and disable any blocker before digging deeper into the issue.
Any solution? This issue is bringing down my lighthouse best practice score.