This distinction is fundamental in web analytics and server behavior:
Page view
A page view is a logical, user-centric event:
- It represents a user loading or viewing a page in their browser.
- Counted once per page load (typically).
- Used in analytics (e.g., Google Analytics) to measure traffic and engagement.
- Tied to user sessions, navigation, and content consumption.
Example:
A visitor loads https://example.com/article → 1 page view
Request
A request is a low-level HTTP transaction:
- Every file the browser asks the server for is a request.
- Includes HTML, CSS, JavaScript, images, fonts, AJAX calls, etc.
- Generated automatically by the browser as it builds the page.
Example:
Loading that same page might trigger:
- 1 request for HTML
- 1 request for CSS
- 3 requests for JavaScript files
- 10 image requests
→ 15+ total requests for a single page view
Key differences
| Aspect | Page View | Request |
|---|---|---|
| Level | High-level (user action) | Low-level (network activity) |
| Count basis | Per page load | Per resource fetched |
| Typical ratio | 1 page view ≈ many requests | Many per single page view |
| Purpose | Analytics, traffic measurement | Server load, performance metrics |
Bottom line
- A page view answers: “How many pages did users look at?”
- A request answers: “How many files did the server have to deliver?”
They’re related, but operate at completely different layers—analytics vs. infrastructure.