AJAX and fetch API monitoring for real users

Ajax / fetch times every XHR and fetch call that real browsers make, by endpoint, and separates your own domain from third parties, so you see which calls cost users the most time.

Ajax / fetch XHR / fetch timing

“Which XHR and fetch calls cost users the most time?”

Sample data
Last 24 hours
All platforms
All events
Base domain · Third party

Total requests: 3.86M
Median load: 321 ms
P90 load: 1,100 ms
Cumulative load: 1.27B ms·req; headline

/api/app-data P90 2,270 ms: slowest tracked
/api/header = 27% of requests

Endpoints

10 tracked · Requests · Load time · Cumulative

/api/v2/header33.7%

1.04M req · 490 ms median · 1,546 ms P90
/api/v1/category-tree11.6%

356K req · 112 ms median · 1,231 ms P90
/api/v4.2/cart/summary6.2%

189K req · 144 ms median · 340 ms P90
/api/v1/app-data5.4%

167K req · 406 ms median · 2,270 ms P90
/api/v2/products2.1%

65K req · 594 ms median · 1,429 ms P90

Connection-phase breakdown

median · 349 ms

Response 291 ms

DNS 29 ms
Connect 19 ms
SSL 10 ms
Response 291 ms

Almost all of the time is server response, not the network.

Where cumulative load concentrates

share of tracked load

header 46%category-tree 21%12%

header 46%
category-tree 21%
app-data 12%
Other endpoints 21%

Sample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.

What you can see on Ajax / fetch

Duration by endpoint at median and p90
Your own domain and third parties, kept separate
Failed and slow calls
Calls per page

Questions about Ajax / fetch

Does it capture failed calls?

Yes. Calls that error or time out are counted along with slow ones.

Can I see third-party APIs separately?

Yes. Calls are split into your base domain and third-party domains.

Last updated 6 Nov 2026 · Reviewed by [Name], [Role]

Related screens

Book a demo Start a free trial