No traffic in Google Analytics while load testing
What happens during a load test request
Every request hits your server where the application is hosted, but it does not load any assets:
- JavaScript
- CSS
- images
- fonts
- etc
The response time measures the elapsed time from just before sending the request to just after the last response has been received, it does not include the time needed to render the response, nor does process any client code, for example Javascript.
Why Google Analytics does not see load test traffic
Google Analytics, and most similar tools such as Mixpanel, Segment, or Hotjar, work by running a snippet of client-side JavaScript inside a real browser. That script fires an event back to the analytics service once the page has loaded and executed in the browser.
A load test does not run a browser. It sends raw HTTP requests directly to your server or API endpoint and measures how the server responds, without parsing HTML, without downloading linked assets, and without executing any JavaScript on the page. Since the Google Analytics snippet never runs, it never sends its pageview or event beacon, so the traffic never shows up in your Analytics dashboard, no matter how many virtual users you send at the endpoint. This is expected behavior, not a bug or a sign that your test failed to reach the server.
Where load test traffic does show up
Because the request itself is a real HTTP request, it is fully visible anywhere that observes traffic at the server or network level, rather than at the browser level:
- Web server and application access logs
- CDN or reverse proxy logs
- Backend APM tools (New Relic, Datadog, and similar)
- Infrastructure metrics: CPU, memory, connection counts
- LoadFocus's own test results, response codes, and response time charts
If you need to confirm your server actually received the load, check one of these sources rather than a client-side analytics tool.
Why this matters when reading your results
Because response time in a load test measures server and network time only, and excludes browser parsing, rendering, and script execution, a fast load test result tells you the backend responded quickly, but not how quickly a real visitor perceives the page as loaded. A page that returns its HTML in 100ms but then loads several megabytes of JavaScript and images can still feel slow to a real user, even though it looks fast in a raw HTTP load test.
If you also want to measure how a page performs from a real browser's point of view, including asset loading, rendering, and Core Web Vitals, under load, that is a different kind of check than a raw HTTP load test. See https://loadfocus.com/docs/guides/load-testing/page-speed-under-load for that side of performance testing.