unlighthouse
lighthouse-ci
Our great sponsors
unlighthouse | lighthouse-ci | |
---|---|---|
15 | 18 | |
3,540 | 6,272 | |
- | 1.5% | |
9.2 | 7.1 | |
5 days ago | 3 days ago | |
JavaScript | JavaScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unlighthouse
-
Audit your sites 10X faster with Unlighthouse
I encourage you to experiment with the Unlighthouse CLI to see how it can meet your specific needs. Here is the link to official docs.
-
Unlighthouse - easily run Lighthouse test on all website pages
Recently found that, super fast and easy to use: https://unlighthouse.dev
-
Good Website Checker/Crawler
I use a combination of unlighthouse (https://unlighthouse.dev/) and Total Validator (https://www.totalvalidator.com/)
-
Unlighthouse - scan you entire website
unlighthouse
- A PageSpeed insight report, but for every page in your domain
- Unlighthouse: Like Lighthouse, but it scans every single page
-
How to improve the PageSpeed score of your Nuxt.js website in 6 steps
After deploying all these changes on our website, the PageSpeed score jumped from 23 to 97. To ensure that the numbers won't drop over time, I'd recommend setting up the https://unlighthouse.dev checks for your CI/CD.
-
Where and how to learn SEO?
I also found this gem https://unlighthouse.dev scan your whole website from the cli. Absolute gold!!
lighthouse-ci
-
help needed with lighthouse ci for angular, github actions, PROTOCOL_TIMEOUT: (Method: Debugger.disable)
- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,
-
Continuous performance audits in Nuxt with Lighthouse CI and Github Actions
This approach would suit most of the cases however to achieve more accurate performance audits you should be conducting Lighthouse tests on a dedicated server to avoid results being affected by the machine capabilities. In other words, if you are running Lighthouse audits on a repository where there are several pull requests/workflows/pushes going on, the result of this audit may not be accurate and this is what we want to avoid. For that you would need a separate machine with Lighthouse Server installed on it. So on a pull request you would trigger this machine to conduct a performance audit and return response to your repository.
-
Measuring Page Speed with Lighthouse
And finally, Lighthouse has a CI version you can run in your continuous integration. We’ll use this method to schedule periodical benchmarks.
-
Ensure your Next.js app's performance is top-notch with Lighthouse CI and GitHub Actions
TLDR; I use the Google Chrome Lighthouse CI with a .lighthouserc json configuration to test next start. The Lighthouse CI GitHub app is used to return a pass or fail status check in a PR.
-
Everything you need to know about Web Performance (in 5 Minutes)
You should also incorporate performance checks into your CI/CD pipeline. Use Lighthouse CI to run a synthetic Lighthouse test on each PR (PS: Learn why you shouldn't believe the Lighthouse score alone) and bundlesize package to raise alerts if your bundle size exceeds a certain threshold. For more nuanced data you should use WebPageTest.
-
Accessibility Automation tool for CI pipeline
You can also run Google’s Lighthouse CI tool against multiple URLs, and then hook that up to their self-hosted dashboard service: https://github.com/GoogleChrome/lighthouse-ci
-
Understanding SEO and Web Vitals for your NextJS site and how to improve them?
You can also set up lighthouse-ci as a github action to evaluate the web vitals on push or in pull requests.
-
You’re probably using Lighthouse wrong: How we got tricked by a single magic number
You can have more consistent results if you set up Lighthouse CI in an external environment to test your page or use tools like SpeedCurve, but if you need to quickly inspect a website, I suggest taking a look at Page Speed Insights.
-
Frontend Testing: No more Unit/Integration/E2E categorizations and priorities
This name is already self-explanatory, and developers just need to run Lighthouse or its CI.
-
I built an open-source tool that scans your entire website with Google Lighthouse (unlighthouse.dev)
They also have a powerful CI tool (https://github.com/GoogleChrome/lighthouse-ci) with custom timelines, may look to implement it at some point
What are some alternatives?
lighthouse - Automated auditing, performance metrics, and best practices for the web.
pa11y - Pa11y is your automated accessibility testing pal
unbuild - 📦 An unified javascript build system
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
unctx - 🍦 Composables in vanilla JS
unrouted - Unrouted is a minimal, composable router built for speed, portability and DX
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
puppeteer-cluster - Puppeteer Pool, run a cluster of instances in parallel
WebPageTest.api-nodejs - WebPageTest API wrapper for NodeJS
chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions
pa11y-ci - Pa11y CI is a CI-centric accessibility test runner, built using Pa11y