What is the page interaction point?
- The page interaction point is the moment a user can interact with the core functionality of a webpage.
- Interaction is seeing the content and being able to interact with it (click buttons, choose options, navigate, etc.)
- The page interaction point is a conceptual moment rather than a technical pageload event.
The real goal, the finish line, the entire point of making a page faster is to make it faster for people to interact with.
Let's book a hotel
A good example would be a hotel booking site, where you can see things on the page, but the place to actually book a hotel is not usable for a couple seconds after the page has loaded.
If the entire reason that a person uses a page is to book a hotel, then the page may well be "loaded and "visible" but may not be usable for the function the person is hoping to use that page for.
In such a case, there is no current distintion between the page loading and the page being usable.
That page may load in two seconds, but if a person that is using that page to book a hotel can not book a hotel for seven seconds, then it doesn't seem accurate to state that the page is loaded in two seconds.
The importance of the "page interaction point"
- It highlights that the experience a person has with a webpage is the core goal of pagespeed optimization.
- It is a useful and meaningful way to compare two scenarios based upon user experience rather than technical page load events.
- Alerts that the core functionality of the page is the most basic metric upon which to decide what is best for that page.
How to optimize for the page interaction point
- Determine the core functionality of the page
- Determine what can be removed from the critical rendering path without affecting the core functionality
- Defer everything that is not required for the core functionality
Making a decision using the page interaction point
Using the page interaction point means we determine the core functionality of the page first and then our decisions become easier.
Now let's look at each of those pages in more detail...
A hotel booking page
defer vs async?
The entire purpose of the page interaction point is to highlight that the pagespeed optimizations made should be based upon the core functionality of the page.
Everything should be based on one question: How does the user get to do what they want to do as fast as possible?
All page speed considerations are dependant on the page interaction point
Do not use any page speed recommendation without considering the core functionality of the page.
The overall goal should be to get to the page interaction point as quickly as possible (the user doing what they want to do as fast as possible).