Shane Exterkamp

@mfriesenhahn should #9537 close this? Does web.dev have full coverage of all the bullet points above?

> I've noticed this past week, the PSI API (including pagespeed.web.dev) will now return cached results for subsequent requests for insights of the same URL. We moved our cacher to...

Hey, thanks for reaching out! To help with diagnosing this we'll need to have the URL you're testing, and the context that you are running Lighthouse in. How did you...

So I ran that URL against all channels and I am finding things to be a consistently in the high 50's low 60's for performance. I would say within expected...

Hmmm checking out https://www.omgubuntu.co.uk/ I get: ~80 from cli on v4.0.0-alpha.1 ~40 from pagespeed insights (running v4.0.0-alpha.1) So this is solidly reproducible for that site. I am force running pagespeed...

@patrickhulce I remember that, but I can't find that issue/discussion, you have a link to it/can you bump it to mention this thread?

Oops this got buried! Missed that bump. I will definitely be looking into these URLs again soon. So far we have: - https://www.omgubuntu.co.uk/ - @wardpeet other url? Taking a guess,...

PSI did just suffer a [bug](https://groups.google.com/d/msg/pagespeed-insights-discuss/by9-TbqdlBM/AoAh70JBGgAJ) that lowered scores unexpectedly @duartegarin & @j-bacal, so it seems like your sites may have stabilized back to more reasonable numbers. @vertic4l, no major...

I'll put this in the _bad psi errors_ category :wink: since it seems to be an opaque error.

> Followups: > >Build tracker supports budgets (and some nice reporting options), however we can add that on later after the data collection has begun. Remove bundlesize From #10550