Page checks
Every page a scan loads is also checked for problems your visitors would hit, like broken links, missing images and script errors. They are listed on the project's Page checks page.
What each page is checked for
- Broken links
- Links to pages that answer 404 or 410. Up to 200 links are tried each scan.
- Files that fail to load
- Images, scripts, stylesheets and fonts from your own site that answer 404, 410 or a server error.
- Failing requests
- Requests the page makes to your own site that answer 404, 410 or a server error, such as a 500 from your API.
- Script errors
- Errors thrown by the scripts on the page.
- Hidden from search
- Pages that start telling search engines to skip them (noindex).
- Security certificate
- A certificate that expires within 14 days and is in the last fifth of its life, or has expired.
- Insecure files
- Files a secure page loads over http, which the browser blocks.
- Accessibility
- Serious and critical problems under WCAG 2.1 A and AA, like a button with no name. A page is checked again when it changes, or after a week.
While it learns your site, Regress also notes pages that show an error meant for developers, and counts that read wrong, like “1 items”.
New, already there and fixed
The same problem on many pages is listed once, with how many pages it is on. The Page checks page splits them into three lists:
- New: appeared on a page after Regress had already checked it.
- Already there: found the first time Regress looked at the page. These never alert, except a certificate about to expire.
- Fixed: gone in the last 30 days.
Alerts
New broken links, files that fail to load, failing requests, pages hidden from search and insecure files go into your alerts as things that can wait, by default in the daily summary. A security certificate about to expire is urgent. Script errors and accessibility problems are only listed on the Page checks page. A page check never fails a test or a GitHub check.