Skip to content

Remove outdated Lighthouse references in FAQ #6035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Remove outdated Lighthouse references in FAQ #6035

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions docs/app/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1253,10 +1253,7 @@ steps, Cypress adds its own overhead. Thus, the performance numbers you get from
Cypress tests are slower than "normal" use. Still, you can access the native
`window.performance` object and grab the page time measurements, see the
[Evaluate performance metrics](https://github.com/cypress-io/cypress-example-recipes#testing-the-dom)
recipe. You can also
[run Lighthouse audit straight from Cypress](https://www.testingwithmarie.com/post/web-performance-testing-with-google-lighthouse)
via [cypress-audit](https://www.npmjs.com/package/cypress-audit) community
plugin.
recipe.

## Integrations with Other Tools/Frameworks/Libraries

Expand Down
Loading