Export PageSpeed Insights (by Google) results

Export PageSpeed Insights (by Google) results

Problem Description:

Is there any way to export PageSpeed (the Google Chrome extension) results into a file?
I’m looking for a way to export the results from web-site testing using PageSpeed tab in the browser console.

Solution – 1

I am not sure if this is what you are looking for, but I feel you can build the data you need using the JSON response

curl https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=http://www.google.com > response.json

If you don’t have access to cli you can enter the same url with your website of interest in your browser and hit return key.

I lately started using Postman if you are trying to optimize your website performance I personally feel this would help because it does save the responses and the time of request.

Thank you it was helpful

Solution – 2

If you open up and run Google PageSpeed Insights through the Audit tab (Lighthouse tab after Chrome 83) in Chrome Developer Tools, there is a button in the left part of the panel that will allow you to download the report as a JSON file.

Google PageSpeed Insights Audit Report

Solution – 3

From my understanding, Tom’s answer is missing some context and depending on your use case, can give the wrong impression.

Chrome’s performance throttling is RELATIVE to the machine running the
audit. So that means running an audit on a weaker machine is going to
give an artificially lower score than what it may actually be on another machine.

PageSpeed Insights (PSI) runs a lighthouse audit on a simulated Moto 4.

What device and network conditions does Lighthouse use to simulate a page load?

Currently, Lighthouse simulates a page load on a mid-tier device (Moto G4) on a mobile network.

So if you run an audit through the Chrome tab on a 2018 Macbook Pro and your client runs it on a 2010 HP laptop, you will get vastly different results. So using PSI should give a more "objective" audit as it’s using the same hardware for each test.

If you only ever use your development machine to run tests for yourself, then it may not matter as much. But if you are sharing and cross examining reports with a client or team (across different machines), then this is something to keep in mind.


Throttling is relative to your computer’s capabilities. For example,
the 2x slowdown option makes your CPU operate 2 times slower than its
usual ability. DevTools can’t truly simulate the CPUs of mobile
devices, because the architecture of mobile devices is very different
from that of desktops and laptops.

Rate this post
We use cookies in order to give you the best possible experience on our website. By continuing to use this site, you agree to our use of cookies.