Question 1

How to test a localhost site with psi?

Accepted Answer

Use tunneling services like ngrok to expose your local server, as recommended in the README for local projects with tools like psi-ngrok. This allows psi to access the site as if it were deployed.

Question 2

psi vs Lighthouse CLI: which is better for automation?

Accepted Answer

psi is a wrapper around the PageSpeed Insights API, ideal for remote testing and integration into build processes. Lighthouse CLI runs locally and offers more control, but psi is simpler for automated workflows with deployed sites.

Question 3

Can I integrate psi into a GitHub Actions workflow?

Accepted Answer

Yes, you can add psi as a Node.js dependency and run it in a workflow step to fetch performance scores. Use the threshold option to fail the workflow if scores drop below a set level.

Question 4

How to get filmstrips from psi reports?

Accepted Answer

The CLI doesn't output filmstrips directly; you need to use the Node.js API to access the audits object, as shown in the README code snippet that logs data from lighthouseResult.audits.

Question 5

What's the difference between psi and using the PageSpeed Insights API directly?

Accepted Answer

psi simplifies the API calls with a clean Node.js interface and adds features like terminal reporting and threshold enforcement. It abstracts away raw API handling but still relies on the same backend.

Question 6

How to set up a performance budget with psi?

Accepted Answer

Use the threshold option in the API or CLI to define a minimum score (e.g., 70). If the score falls below, the test fails, making it easy to enforce budgets in CI/CD pipelines.

PSI

What is PSI?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions