What is page response time
There is a lot of things to be done after someone hits a link to your website:
- DNS name resolution;
- SSL/TLS connect/handshake to your server;
- TCP connection to your server;
- negotiations specific to the particular protocol(s) involved;
- redirects (e.g. from http:// to https://);
- content generation on your server;
- content transfer from your server to the user.
So the response time is the time from a "hit" to TTFB (time to first byte) or TTLB (time to last byte) of the transferred content depending on the check's method and technology. In this context the transferred content is not the whole webpage with images and other external resources and content, but the entire html-page (html-file) only.
So what's the problem?
Everybody loves fast websites. Really.
As Phocuswright research authority reports:
There are also 2 great articles by Jakob Nielsen on this topic:
What is your approach?
Check. Store. Analyze.
AppSiteDown checks the response time (TTLB) of your website from different places and stores this information so you could:
- be confident your website is fast enougth for every visitor from different places of the planet Earth;
- find deviations with day-2-day, week-2-week and month-2-month statistics;
- see dependencies of response time on website changes.