URLTO GUIDE
Distinguish response-fetch time from screen loading
The speed check measures one server request. Do not report it as the time a visitor’s screen takes to finish.
URLTO editorial · Updated
Input and processing example
Compare it yourself · Illustrative example
측정 / Measured: 요청 시작 → 응답 본문 수신 별도 확인 / Separate: 이미지·스크립트 로딩 → 화면 렌더링
Steps to verify
- Record URL and time.
- Read final response and body size.
- Inspect perceived loading in a browser.
How to interpret the result
Elapsed time includes connection, redirects and body receipt. It differs from pure TTFB, all-asset loading and Core Web Vitals scores.
Deciding what to do next
A quick response can coexist with slow images or scripts. Combine server checks with page use to choose the next investigation.
Feature scope
Measure the received body and elapsed fetch time from the Korean server, not all assets, rendering, pure TTFB or a Core Web Vitals score.
Frequently asked questions
Is it every Korean visitor’s actual speed?
It is a Korean server observation. Visitor devices, networks and browsers differ.