Improving Load Performance - Chrome DevTools 101

Chrome for Developers · 335K views · 2018 · 13:29

Open on YouTube

Web developmentSoftware performance & optimizationTesting, debugging & developer toolstutorialdated

Why Stack Overflow recommends it

Stack Overflow users link it as a starter walkthrough for running Lighthouse audits and using DevTools to measure and improve page load speed.

Recommended by 2 people across 2 different months, 2019 to 2024.

What it is

A 13-minute Chrome DevTools 101 tutorial from the Chrome team. Presenter Kayce uses a demo cat site to show how to audit a page, read the report, apply one fix at a time and measure each change. It covers text compression, large images, render-blocking resources and excess JavaScript.

What people said

Recommends André Tzermias · 2019-03 · Stack Overflow · on “Can I use pagespeed insights for my local host website or offline?”

Yes. Use the "Lighthouse" tab from your google chrome dev tools. This is a great starter tutorial on how to do that: [this video] Edit: user izogfif [LINK] pointed out the "Audit" tab was replaced by "Lighthouse".

Recommends 0leg · 2020-03 · Stack Overflow · on “How to use Angular ChangeDetectionStrategy to make a table with multiple inputs faster?”

In order to improve the performance one first needs to figure out - what causes the lag. Dev Tool Performance Use Chrome Dev Tools [LINK] (or any other similar tool) to record and measure the performance on the page. Example output: [LINK] Determine what causes the problem. Is it a slow JavaScript execution? Is it a network problem. Fix it accordingly. JavaScript-related problem can be caused by a number of reasons. May be you are running some code in a loop and it causes extra calculations. What table are you using. Is a a Material Table [LINK] , see the tools to improve the performance (like pagination). If you are dealing with thousands of records, consider using Data Grids (e.g. Ag Grid

Cites Josue Centurion · 2024-06 · Stack Overflow · on “Chrome Dev Tools - "Size" vs "Content"”

I just want to mention that if you're following a tutorial like this: [this video] the name of the "Large request row" changed to "Big request row" in chrome newest version