Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Monitors

Page load monitor

A page load monitor loads a web page together with the files it needs, such as stylesheets, scripts, images and icons, and times the whole thing. Use it to see how long your page really takes, how big it is, and when its files start failing to load.

For a plain "is the site up" check, a website monitor is lighter and can check more often.

What you need first

  • The full address of the page, such as https://www.example.com/.
  • The page must be on the public internet. The check cannot sign in, so for a page behind a login it times whatever the server shows a visitor who is not signed in.

Limits

  • Page load monitors are checked at most every 5 minutes, whatever your plan allows for other monitors.
  • You can have up to 20 page load monitors per account, and up to 2 for any one site. For more pages on the same site, use website monitors.

Set it up

  1. Open Monitors and press Add monitor.
  2. Choose Page load (full page).
  3. In URL, type the page address. If you leave out https://, it is added for you.
  4. Give it a Friendly name, such as "Home page load".
  5. Choose Check every. Choices under 5 minutes are raised to 5 minutes when you save.
  6. Look over Where alerts go and press Start monitoring.

What it measures

Each check first fetches the page's HTML. It then reads the HTML for the files a browser would load for the first view: stylesheets, scripts, images, icons and preloaded files. It fetches those six at a time, as a browser does. The load time is the time for the HTML plus the time to fetch all the files.

It does not run the page's JavaScript. Files that scripts load later, such as content filled in after the page opens, are not counted.

So that one check cannot flood a site, there are limits on each check:

LimitValue
Files fetched50
Files from any one outside server (for example a CDN)10
Size of one file5 MB
Whole page, HTML and files together20 MB
Size of the HTML1 MB
Time for the whole check30 seconds

Files past the number limits are not fetched, and a file over 5 MB is only read up to that size. Neither counts as a failure. Files still loading when the 30 seconds run out count as failed.

When it counts as down

  • The page answers with a status code outside 200 to 399, or does not answer at all.
  • Many of its files fail: at least 3, and about half or more of the files fetched.

A single broken image does not make the monitor go down, but it shows in the failed count on the monitor page. Two cities must fail twice in a row before you get a down alert. Checks run from all our cities, taking turns. Page load monitors have no More settings panel, so the form cannot change these rules.

Reading the monitor page

The top of the monitor page shows the typical full page load and the range between the fastest and slowest city. Next to it are the page size and the number of requests, with any failed ones. The Right now card names the slowest file and how long it took, which is often the best place to start speeding a page up.

Send a test

Open Alerts and press Send test on each channel. Then open the monitor. After the first round, it should show a load time, page size and request count.

When it does not work

  • "Up to 20 page load checks per account." or "Up to 2 page load checks per site." You are at a limit. Use a website monitor for the extra pages.
  • An error like "12 of 20 files failed to load". Many files could not be fetched. Open the page in your browser with the developer tools open and look for files that fail. If the error ends with "stopped after 30 s", the page took longer than the time allowed.
  • An error like "HTTP 403". The page refused the request. Some firewalls and bot filters block automated visitors. See Allowing our checks through a firewall.
  • The load time is much lower than in your browser. The check does not run JavaScript, so work your scripts do after the page opens is not included.
  • It says down but the site works. See A monitor says down but my site works.
← Third-party services Heartbeat monitor (cron jobs) →

Still stuck? Email [email protected] and say which guide you were following.