Return to Answer

It seems this 'Finished' time in Chrome devtools includes the asynchronously loading(non blocking) objects/elements on the page which may continue downloading way after the onload event for page has fired.

The response time for a website generally speaking means 'Load' time because that is more easily user perceivable, at this point user can see browser has finished working and page is ready on their screen. Finish time, although technically also a response time doesn't have as much end-user implication.

In some cases it seems the Finish timer never stops and continues increasing so it may not be the best assessment of web page response time.

The Finish time in Chrome Devtools includes the asynchronously loading  (non blocking) objects/elements on the page which may continue downloading way after the onLoad event for the page has fired.

The response time for a website generally means the Load time, because that is user perceivable, and at this point user can see that the browser has finished loading and page is ready on their screen.

The Finish time, although technically also a response time, doesn't have as much end-user implication.

In some cases, it seems that the Finish timer never stops but continues increasing, so it may not be the best assessment of web page response time.

It seems this 'Finished' time in Chrome devtools includes the asynchronously loading(non blocking) objects/elements on the page which may continue downloading way after the onload event for page has fired.

The response time for a website generally speaking means 'Load' time because that is more easily user perceivable, at this point user can see browser has finished working and page is ready on their screen. Finish time, although technically also a response time doesn't have as much end-user implication.

In some cases it seems the Finish timer never stops and continues increasing so this certainly would not be fair assessment of web page response time.

It seems this 'Finished' time in Chrome devtools includes the asynchronously loading(non blocking) objects/elements on the page which may continue downloading way after the onload event for page has fired.

The response time for a website generally speaking means 'Load' time because that is more easily user perceivable, at this point user can see browser has finished working and page is ready on their screen. Finish time, although technically also a response time doesn't have as much end-user implication.

In some cases it seems the Finish timer never stops and continues increasing so it may not be the best assessment of web page response time.

It seems this 'Finished' time in Chrome devtools includes the asynchronously loading(non blocking) objects/elements on the page which may continue downloading way after the onload event for page has fired.

The response time for a website generally speaking means 'Load' time because that is more easily user perceivable, at this point user can see browser has finished working and page is ready on their screen. Finish time, although technically also a response time doesn't have as much end-user implication.

It seems this 'Finished' time in Chrome devtools includes the asynchronously loading(non blocking) objects/elements on the page which may continue downloading way after the onload event for page has fired.

The response time for a website generally speaking means 'Load' time because that is more easily user perceivable, at this point user can see browser has finished working and page is ready on their screen. Finish time, although technically also a response time doesn't have as much end-user implication.

In some cases it seems the Finish timer never stops and continues increasing so this certainly would not be fair assessment of web page response time.