The PageSpeed Insights API provides free access to performance monitoring for web pages and returns data with suggestions for how to improve. The V...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks Addy, this is super cool! After reading, I was motivated enough to make this into a GitHub Action so I could integrate Page Speed Insights into my CI/CD pipeline 🎉 😃
github.com/JakePartusch/psi-action
Thanks for mentioning the different detailed ways we could use the PSI data and different tools to view the performance data.
I tested the crux.run data and real google big query data, on comparing both seeing some significant difference. Is crux.run is not the crux data?...
Is there a way to find out , for which urls we have the PSI field data, as in crux big query we have only domain based data not particular URL specific data available
Hi there! crux.run is exactly the data from the BigQuery database . If you are seeing a difference it might be a result of aggregating across all connection types and https vs. http aggregation? But yes .. the underlying data is 100% the same
Addy, I was at last Chrome Dev Summit and your talk about Adaptive Loading really inspired my work. I was eager to test this kind of monitoring tool with the site I work on (a news media outlet in Brazil). But the PSI API gives me results far from the the ones I get on Lighthouse through Audit on Chrome. Per example, now, our performance is scoring 78 but when I use PSI I get 0.03!
Our webapp is a React SSR, using code-splitting, and with the Front Page with several areas on lazy loading. I think this is messing with our scores through PSI API, what approach do you advise us to in order o better automate our performance?
Thanks in advance!
Hey Addy, any updates on PSI API getting the latest updates for Core Web Vitals? It also seems that the API returns an older Lighthouse report (6.3.0 vs latest 6.4.1). Thanks in advance!