What's New In DevTools (Chrome 78)

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.

Chromium issue #772558

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:

1. Click the LCP marker in the Timings section.

2. Hover over the Related Node in the Summary tab to highlight the node in the viewport.

1. 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!

Feedback

To discuss the new features and changes in this post, or anything else related to DevTools:

• File definite bug reports and feature requests at Chromium Bugs.
• Discuss possible features, changes, and bugs on the Mailing List.
• Get help on how to use DevTools on Stack Overflow.
• Tweet us at @ChromeDevTools.
• File bugs on this document in the Web Fundamentals repository.

Consider Canary

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.

Note: Canary is released as soon as its built, without testing. This means that Canary breaks about once-a-month. It's usually fixed within a day. You can go back to using Chrome Stable while Canary is broken.

<<../../_shared/discover.md>>