Module guide Web Back to help

Web

Check site health, spot problem pages, and rerun checks after a fix.

Use the sections below for the full walkthrough and the most common follow-up questions.

What this module does

The Web module gives you a quick health check on important URLs instead of making you guess whether a page is fine. It is useful when a client says a page feels slow, looks broken, or is missing something obvious. You add the URLs you care about, inspect the score and issues, and then rerun the check after you fix the page.

What you need to set up first

Add the pages you want monitored, starting with the homepage and the key landing pages.
Make sure the pages are reachable from the public web.
Decide which issues you want to treat as urgent versus informational.
Keep the list focused so the table stays useful instead of noisy.

How it works

1 When a URL is added or refreshed, the module checks whether the page responds and whether it looks healthy.
2 The score is calculated from the check output so you can compare URLs quickly.
3 Issue notes are stored next to the check result so you can read the problem without opening a separate tool.
4 If a page is unreachable, the module still saves the failed attempt so you can see what broke.
5 The latest check becomes the summary number at the top of the page.

What you'll see in the UI

The summary cards show how many URLs are being monitored and how healthy they look overall.
The checked URLs table lists each page, its score, issue count, and latest status.
The issue column helps you see whether the problem is a warning or a true failure.
The add URL action lets you grow the watch list as the site grows.

How to act on the output

Fix the page that has the lowest score first.
Rerun the check after making a change so you can confirm the result improved.
Use the export if you want to hand the audit list to a developer.
Add more URLs when a new campaign or landing page goes live.

Limits and known gaps

The module is not a full crawl or a full Lighthouse replacement.
Some checks depend on the target page being publicly reachable.
If a site is down, the page can still record the failure but it cannot explain every root cause.
The current surface is optimized for quick triage, not deep performance engineering.

FAQ

Short answers for the most common follow-up questions.

What does the score mean?

It is a quick health signal, not a lab-grade performance score. A lower number usually means the page needs attention sooner.

Can I monitor more than one page?

Yes. The table is built to hold several URLs so you can keep the important pages in one place.

What happens if a page cannot be reached?

The failed check is still stored. That way you can see when the issue started instead of losing the history.

Do I need a CMS connection?

No. The module works on public URLs and can be used before any CMS integration is added.

Need more help?

If the guide did not solve it, jump back to the contact form and send a note.

Go to contact form