Time to Interactive

Published on Updated on

Translated to: Español, Português, 한국어, Pусский

Time to Interactive (TTI) is one of six metrics tracked in the Performance section of the Lighthouse report. Each metric captures some aspect of page load speed.

Measuring TTI is important because some sites optimize content visibility at the expense of interactivity. This can create a frustrating user experience: the site appears to be ready, but when the user tries to interact with it, nothing happens.

Lighthouse displays TTI in seconds:

A screenshot of the Lighthouse Time to Interactive audit

What TTI measures

TTI measures how long it takes a page to become fully interactive. A page is considered fully interactive when:

  • The page displays useful content, which is measured by the First Contentful Paint,
  • Event handlers are registered for most visible page elements, and
  • The page responds to user interactions within 50 milliseconds.

Both First CPU Idle and TTI measure when the page is ready for user input. First CPU Idle occurs when the user can start to interact with the page; TTI occurs when the user is fully able to interact with the page. See Google's First Interactive And Consistently Interactive if you're interested in the exact calculation for each metric.

How Lighthouse determines your TTI score

The TTI score is a comparison of your page's TTI and the TTI for real websites, based on data from the HTTP Archive. For example, sites performing in the ninety-ninth percentile render TTI in about 2.2 seconds. If your website's TTI is 2.2 seconds, your TTI score is 99.

This table shows how to interpret your TTI score:

TTI metric
(in seconds)
0–3.8Green (fast)
3.9–7.3Orange (moderate)
Over 7.3Red (slow)

See the Lighthouse performance scoring post to learn how your page's overall performance score is calculated.

How to improve your TTI score

One improvement that can have a particularly big effect on TTI is deferring or removing unnecessary JavaScript work. Look for opportunities to optimize your JavaScript. In particular, consider reducing JavaScript payloads with code splitting and applying the PRPL pattern. Optimizing third-party JavaScript also yields significant improvements for some sites.

These two Diagnostic audits provide additional opportunities to reduce JavaScript work:

Tracking TTI on real users' devices

To learn how to measure when TTI actually occurs on your users' devices, see Google's User-centric Performance Metrics page. The Tracking TTI section describes how to programmatically access TTI data and submit it to Google Analytics.

TTI can be difficult to track in the wild. Tracking First Input Delay can be a good proxy for TTI.

How to improve your overall Performance score

Unless you have a specific reason for focusing on a particular metric, it's usually better to focus on improving your overall Performance score.

Use the Opportunities section of your Lighthouse report to determine which improvements will have the most value for your page. The more significant the opportunity, the greater the effect it will have on your Performance score. For example, the Lighthouse screenshot below shows that eliminating render-blocking resources will yield the biggest improvement:

Lighthouse: Opportunities section

See the Performance audits landing page to learn how to address the opportunities identified in your Lighthouse report.


Updated on Improve article

This site uses cookies to deliver and enhance the quality of its services and to analyze traffic. If you agree, cookies are also used to serve advertising and to personalize the content and advertisements that you see. Learn more about our use of cookies.