Time to Interactive (TTI): When a Page Becomes Usable

Time to Interactive is the moment a page is both fully visible and responsive to user input without long delays.

Quick Definition

Time to Interactive (TTI) is when a page becomes fully usable and responsive to input.

What It Is

Time to Interactive (TTI) marks when a page is fully rendered and can respond to user input quickly.

It checks that the main thread is quiet enough for clicks and taps to work.

How It Works

  • The page must be fully visible.
  • Long tasks on the main thread delay interactivity.
  • TTI looks for quiet periods where the page can handle input.

Why It Matters

  • A page that renders but ignores clicks feels broken.
  • Heavy JavaScript often delays interactivity long after content appears.
  • It pairs with Total Blocking Time to explain input delays.

How to Improve

  • Cut unused JavaScript and defer what is not needed.
  • Break long tasks into smaller pieces.
  • Use lazy loading so scripts only run when needed.
  • Prefetch critical interactions.
Example in Practice

Before: a page paints quickly but buttons freeze for five seconds while analytics scripts load.

After: scripts are deferred and long tasks are split up.

The result: the page becomes interactive almost as soon as it paints.

The lesson: usable means clickable.

💡

Quick Tip

In Chrome DevTools, the Performance panel shows the long tasks that push TTI out.

Frequently Asked Questions

The moment a page is fully rendered and responds to user input without long delays.
FCP is when content appears; TTI is when the page can handle interaction.
Heavy JavaScript and long main-thread tasks are the usual causes.
Remove unused scripts, defer the rest, and break long tasks into smaller ones.

Time to Interactive, in Short

Rendering is not the same as being ready.

Make the page clickable as soon as it is visible.