For example, suppose that your Audits panel report says that your page's performance score is 70 and one of your biggest performance opportunities is eliminating render-blocking resources.
Now that the Audits panel can be used in combination with request blocking, you can quickly measure how much the render-blocking scripts affect your load performance by first blocking the requests for the render-blocking scripts:
And then auditing the page again:
You could alternatively use Local Overrides to add
async attributes to each
of the script tags, but "we'll leave that as an exercise for the reader." Go to
Multi-client demo to try it out. Or check out this tweet for a video demonstration.
Payment Handler debugging
The Background Services section of the Application panel now supports Payment Handler events.
- Go the the Application panel.
- Open the Payment Handler pane.
Click Record. DevTools records Payment Handler events for 3 days, even when DevTools is closed.
Enable Show events from other domains if your Payment Handler events occur on a different origin.
After triggering a Payment Handler event, click the event's row to learn more about the event.
Lighthouse 5.2 in the Audits panel
The Audits panel is now running Lighthouse 5.2. The new Third-Party Usage diagnostic audit tells you how much third-party code was requested and how long that third-party code blocked the main thread while the page loaded. See Optimize your third-party resources to learn more about how third-party code can degrade load performance.
Largest Contentful Paint in the Performance panel
When analyzing load performance in the Performance panel, the Timings section now includes a marker for Largest Contentful Paint (LCP). LCP reports the render time of the largest content element visible in the viewport.
To highlight the DOM node associated with LCP:
- Click the LCP marker in the Timings section.
Hover over the Related Node in the Summary tab to highlight the node in the viewport.
Click the Related Node to select it in the DOM Tree.
File DevTools issues from the Main Menu
If you ever encounter a bug in DevTools and want to file an issue, or if you ever get an idea on how to improve DevTools and want to request a new feature, go to Main Menu > Help > Report a DevTools issue to create an issue in the DevTools engineering team's tracker. Providing a minimal, reproducible example on Glitch dramatically increases the team's ability to fix your bug or implement your feature request!
Was this page helpful?
What was the best thing about this page?
It helped me complete my goal(s)
It had the information I needed
It had accurate information
It was easy to read
What was the worst thing about this page?
It didn't help me complete my goal(s)
It was missing information I needed
It had inaccurate information
It was hard to read
To discuss the new features and changes in this post, or anything else related to DevTools:
If you're on Mac or Windows, consider using Chrome Canary as your default development browser. Canary gives you access to the latest DevTools features.
Discover other DevTools features
Below is a list of everything that's been covered in the What's New In DevTools series.