How does Google PageSpeed ​​Insights calculate server response time?

Question

Google

There is such a situation:



and this is for a static HTML page.

Do I understand correctly that this is a strange situation? Yes, this HTML page is not a small 1.1Mb, it has a lot of CSS, JS, etc. connections.

But how can this affect the time the server returns the first byte?

Am I correct or not - correct me:

• A request arrives from a browser or Google PageSpeed ​​Insights to this static HTML page
  
• the web server (in my case it is nginx/1.14.1) simply finds the HTML file of this page in the public_html folder in response to a request
  
• the browser receives and starts rendering HMTL, including CSS, JS, etc. - but this is the work of the browser, even if it sends new requests to my server
  

those. in fact, the server response time is the time it takes for my nginx to process a request to an HTML page and issue it to the browser?

Those. support answers me like this:

Answer 1

Well, if you have a ready-made html, then ttfb in 0.46 seconds is possible if the check is done from the states, and you have hosting in Russia. Your users in the states actually see this ttfb.
Nobody canceled the delay in the network. Latency can be measured in pings.