URLTO GUIDE
Record results with differing cache and cookie conditions
Your browser and the inspection server do not share identical cache or cookies. Distinguish request conditions when reading timing differences.
URLTO editorial · Updated
Input and processing example
Compare it yourself · Illustrative example
조건 열 / Condition columns 조회 위치 / origin · 로그인 / login · 캐시 맥락 / cache context · 확인 시각 / time
Steps to verify
- Compare status and final view.
- Record known conditions.
- Recheck before assigning a cause.
How to interpret the result
A public server request can receive a different body from a logged-in browser. First and subsequent requests can differ with caching.
Deciding what to do next
A lower time does not establish a cache effect. Mark unknown cache state and add response evidence where available.
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
Does URLTO inspect my browser cache?
It requests from the Korean server. Browser cache is a separate target.