lighthouse
webpack-bundle-analyzer
Our great sponsors
lighthouse | webpack-bundle-analyzer | |
---|---|---|
152 | 20 | |
27,741 | 12,483 | |
0.7% | 0.2% | |
9.5 | 6.4 | |
6 days ago | 4 months ago | |
JavaScript | JavaScript | |
Apache License 2.0 | MIT License |
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.
lighthouse
-
Top 20 Frontend Interview Questions With Answers
Google Core Vitals now represent the most important metrics to focus on when it comes to technical SEO. Google Core Vitals are a set of standardized metrics that Google uses to evaluate the user experience offered by a web page and assign it a technical SEO grade. Several tools exist to measure and report technical SEO performance, but the most reliable is Google Lighthouse.
-
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,
-
Is Lighthouse a misleading performance tool?
There has been discussion about adding a visual indicator to make the mode more obvious, but it has not made it into Chrome devtools!
-
7 Proven Practices to Boost Development Speed and Project Quality
When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.
-
Performance scores for Google Lighthouse/Insights seem to be very inaccurate
There's a link to what they mean by mobile network there (https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md) and it says:
-
How to store your app's entire state in the url
Here's the non-psuedo code equivalent that can leverage CompressionStream rather than using a browserified-gzip-library: https://github.com/GoogleChrome/lighthouse/blob/437eb4d757c5...
We use it in Lighthouse for the exact same purpose, a URL #hash full of state. We found that modern browsers support 10mb of data in the hash. https://github.com/GoogleChrome/lighthouse/pull/12509#discus...
-
Nightmare on Dev Street: Terrifying Situations to Make Your Spine Tingle
You can find out if your SaaS app is slowing down with Google Chrome Lighthouse. Lighthouse should be a staple in your monitoring because it lets you see the performance, accessibility, and SEO metrics related to your app's performance.
- Why your website should be under 14kb in size
-
Benchmarking Bun & Next against Deno and Fresh
Lighthouse: A tool developed by Google to measure a website’s performance using an average of six metrics.
- Top 25 Tips for Building an EXTREMELY FAST Website!!!
webpack-bundle-analyzer
-
Web Performance Resources for Front End Developers
Webpack Bundle Analyzer
-
🚀 Angular 14 + ESLint, Material + Transloco + Jest, TestCafe + Docker + Prettier 🚀
npm run analyse - analyse bundle with webpack-bundle-analyzer
-
I shaved 80 MB from my TypeScript build by removing googleapis
This was my question as well. The article does answer the question, but off the bat I'd assumed the author was talking about output/dist. The web treemap cli is a great tip. If you are using webpack, webpack-bundle-analyzer is a helpful tool for quickly finding bloated packages. It's definitely helped me cut down my build times: https://github.com/webpack-contrib/webpack-bundle-analyzer
-
Zero experience with Angular. I'm in charge of our CI and we're getting extremely slow prod build times (~1 hour 34 mins). Where should I start researching solutions for this?
Here are a few tipps where you could save some time: 1)check angular.json (configurations -> "your ci config") - look for buildOptimizer / optimization 2)If you run npm ci during your pipeline it might make sense to create the node modules folder beforehand, it seems to save time (https://github.com/npm/cli/issues/2011) 3)Use ng build --stats-json to analyze your build 4)Use https://github.com/webpack-contrib/webpack-bundle-analyzer (also works together with 3. ) 5)Check your package.json for unused dependencies 6)Check your imports, import only what is needed Hope this helps
-
The best Angular 13 Starter Project
- `npm run start` - Start the app - `npm run lint` - Lint the project - `npm run test` - Run unit tests - `npm run build` - Build the project - `npm run build:prod` - Build the project in production mode - `npm run build:prod:stats` - Build the project in product mode with stats - `npm run analyse` - Analyse bundle with [webpack-bundle-analyzer](https://github.com/webpack-contrib/webpack-bundle-analyzer) - `npm run compodoc` - Generate [compodoc](https://github.com/compodoc/compodoc) documentation - `npm run version` - Generate changelog - `npm run prettier` - Format the whole project - `npm run audit` - Audit this application using Sonatype OSS Index
-
10 Must-Have React Developer Tools to Write Clean Code💻🔥
4. Bundle Analyzer
-
Angular 12 + ESLint + Material + Transloco + Jest + Compodoc + Docker
npm run analyse - analyse bundle with webpack-bundle-analyzer
-
How to get started with improving site performance
One of the first tools that I started using is webpack-bundle-analyzer. It generates a report of the output of your webpack build which visualises the filesize of your JavaScript files and what libraries are included in each file. Here is an example screenshot:
-
Minimizing Webpack bundle size
Let’s start by getting an understanding of all the code & dependencies that need to be sent to the browser, along with the memory size of each. Adding webpack-bundle-analyzer to your webpack configuration is the perfect starting point.
-
Using Vite with React
In our "old" build system - I configured webpack-bundle-analyze to inspect bundle chunks and understand what it made of. I added rollup-bundle-visualyzer instead (although there is an issue that the reported size is not correct).
What are some alternatives?
awesome-vite - ⚡️ A curated list of awesome things related to Vite.js
vite-plugin-svgr - Vite plugin to transform SVGs into React components
axe-core - Accessibility engine for automated Web UI testing
esbuild - An extremely fast bundler for the web
unlighthouse - Scan your entire site with Google Lighthouse in 2 minutes (on average). Open source, fully configurable with minimal setup.
rollup-plugin-visualizer - 📈⚖️ Visuallize your bundle
Vue Storefront - Alokai is a Frontend as a Service solution that simplifies composable commerce. It connects all the technologies needed to build and deploy fast & scalable ecommerce frontends. It guides merchants to deliver exceptional customer experiences quickly and easily.
Turbolinks - Turbolinks makes navigating your web application faster
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀
sveltekit-blog-mdx - SvelteKit MDX starter blog with MDsveX (Svelte in markdown)
Gantt chart for React.JS - dhtmlxGantt with ReactJS