Skip to Content
Platform.Ontology

Navigation and Resource Timing

Reports DNS, connect, TLS and download timings for the page and each resource.

Gets silentlySpeed and timingPerformance APIWeb browsersWhile you use it

In one line

Can see how fast the page and each file loaded for you

Reports DNS, connect, TLS and download timings for the page and each resource.

Reveals connection speed and CDN behavior, whether a request hit the cache, protocol (h2, h3) and TLS reuse. Cross-origin detail needs the Timing-Allow-Origin header, otherwise sizes and phases are zeroed.

What it can and can't do

What the user does: Nothing. It happens as the page loads

It can

  • Get timings for DNS, connection, security setup and download
  • Learn your connection speed and if a file came from cache
  • Learn the web protocol used, such as h2 or h3
  • Get full detail for outside files only if their site allows it

It cannot

  • See what is inside other sites' files
  • Ask permission first
  • Know who you are by itself
  • See full outside detail without that site's approval

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported292013-08-20None
EdgeSupported122015-07-29None
FirefoxSupported352015-01-13None
SafariSupported112017-09-19None
Safari on iPhoneSupported112017-09-19None
Chrome on AndroidSupported292013-08-21None
Samsung InternetSupported2.02014-10-17None

How a site asks for it

APIperformance.getEntriesByType('navigation'|'resource'); PerformanceObserver
Browser compat keysapi.PerformanceResourceTiming
api.PerformanceNavigationTiming
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Read PerformanceNavigationTiming and resource entries
  2. Check nextHopProtocol, transferSize, responseStart, connectStart
  3. Send to analytics

Data you get

What comes back: One entry per resource, about 20 timestamps each
Shape: list

FieldTypeUnitRangePrecision
durationfloatms0 to 600005 microseconds to 1 ms (timer limited)
transferSizeintegerbytes0 to GBexact for same origin or TAO; 0 if cached
nextHopProtocolstringNoneh2, h3, http/1.1exact

Technical limits

  • Cross-origin detail zeroed without TAO
  • Buffer limited to 250 resource entries by default
  • Cannot see response bodies

The story

What it is

Browsers report timings for the page and each file it loads: DNS, connection, security handshake and download.

For you

You never see it. Sites quietly collect how fast each page and image loaded for you. Your slow connection is turned into data that helps them fix slow pages.

For makers

It is the base of web speed monitoring. Teams compare load times by country, network and device. It also lets ad and tracker scripts see timing of other files, so browsers limit cross site detail.

Where you see it

TypeExampleApps
analyticsA monitoring service collects load times from real visitors and shows a map of the slowest regions.Datadog RUM, New Relic, Cloudflare Web Analytics
shoppingA retailer finds that its image server is slow in one country and adds a closer cache.None named
videoA video site checks how long the first video segment takes to arrive and adjusts quality.YouTube, Netflix
gamesA game portal measures asset download times to see how long players wait before playing.None named
adsAn ad network measures how long each ad takes to load and drops slow ad partners.None named
securityA fraud tool compares timing with the claimed location. A login that says Paris but loads like Asia looks odd.None named
newsA news site measures third party script times to learn which tags slow the page.None named

Risks

  • Can hint at your location
  • Cross site limits apply

What the platform says

Good uses and abuse

Legitimate uses

  • Real user monitoring, Core Web Vitals

Known abuse

  • Infer cache state, ISP speed, VPN latency

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits3Rough identifying entropy, when known

History

  • 2020-01, Chrome: Cross-origin entries reduced without Timing-Allow-Origin
  • 2023-09, Chrome: Resource timing gets responseStatus and contentType

Sources

How well checked: Based on official documentation.

On this page