Page size monitoring measures the raw byte size of your page response and alerts when it exceeds configurable warn and critical thresholds. Page bloat slows load times and increases CDN egress costs.
⚙️How it works
Uptrue fetches your URL and measures the response body size in kilobytes. If it exceeds your warn threshold, status goes degraded. If it exceeds the critical threshold, an incident opens.
✓What Uptrue checks
- HTTP response body size (KB)
- Warn threshold
- Critical threshold
⚠Alert conditions
- Page size exceeds warn threshold (degraded)
- Page size exceeds critical threshold (down)
Why this matters
Unnoticed asset additions, image uploads without compression, or third-party script bloat can double your page weight. Monitoring catches it before it affects user experience and Core Web Vitals.
Set up in 60 seconds
Free plan · 3 monitors · No credit card required
?Frequently asked questions
What thresholds should I set?
Typical: warn at 1MB, critical at 3MB for HTML pages. For APIs, much lower (warn 100KB).
Does this include images and CSS?
This measures the raw HTML response only. Full page weight including assets is measured by Lighthouse tools.
Related Monitor Types
📦
Ready to set up Page Size Monitoring?
Join teams who monitor their infrastructure with Uptrue. Free plan, no credit card required.
Start Monitoring Free