What You'll Learn
You'll discover when a webpage becomes fully interactive and how server-side rendering's hydration process influences that critical moment.
What Time to Interactive (TTI) Measures
Time to Interactive (TTI) marks the point when your webpage is not just visible, but fully responsive to user input. Think of it like a phone call: First Contentful Paint (FCP) is when you hear "Hello?" (something's there), but TTI is when the other person can actually hear you and respond—the connection is truly two-way.
The Interaction Capability Threshold
A page reaches TTI when three conditions are met:
- Visual content is rendered (FCP has occurred)
- Event handlers are registered (buttons, links, and inputs work)
- The main thread is available (no long-running JavaScript blocking interactions)
If users click a button before TTI, nothing happens—or worse, the action fires after an unexpected delay.
How Hydration Affects TTI in SSR
In server-side rendering, the HTML arrives quickly (good TTFB and FCP), but it's initially "non-interactive"—the markup is there, but JavaScript hasn't attached event listeners yet.
Hydration is the process where your JavaScript framework "wakes up" the static HTML by:
- Attaching click handlers to buttons
- Binding data to interactive components
- Enabling dynamic behavior
During hydration, TTI is delayed. Large JavaScript bundles or complex component trees extend this gap between "I can see the button" and "the button actually works." This creates a frustrating "uncanny valley" where the page looks ready but ignores user input.
Optimizing TTI in SSR means reducing JavaScript bundle size, prioritizing critical interactions, and using techniques like progressive hydration or partial hydration.
Key Takeaway: Time to Interactive (TTI) measures when a page becomes fully usable, and in SSR applications, the hydration process directly determines how long users must wait between seeing content and actually interacting with it.