Skip to main content

Test live pages Pro

Rendered checks without a cloud

Scheduled pages finish in a real browser you control, so painted contrast, focus and layout get measured, and your pages are never sent to another service.

Updated for Lumtera 1.3.0 and Lumtera Pro 1.2.0.

Overview

A scheduled check runs on your server, without a browser, so it reads the markup and cannot measure painted contrast, focus or layout. Each scheduled page then waits for a browser you control, and the Page checks screen says what each page has had: Server check only, Rendered check without the keyboard walk, or Rendered check.

There are four ways to finish them. The background of an administrator's admin session loads pages due one at a time, out of sight, if you turn it on. Run rendered checks now on Page checks runs the full pass, with the keyboard walk. wp lumtera-pro rendered run does the same with Chrome or Chromium on the server. A scheduled job elsewhere can use the rendered-check script in the plugin's tools folder.

Why does it matter?

A scheduled check runs on your server, which has no browser. It can read the markup, but it cannot measure painted contrast, focus or layout. Most tools solve that by sending your pages to their cloud.

What do you get?

  • An administrator's admin session can finish pages in the background, one at a time. It is optional, and you can pause and resume it.
  • A button, wp lumtera-pro rendered run with a headless Chrome, or a scheduled job elsewhere with the script in the plugin's tools folder.
  • Each page says what it has had: Server check only, Rendered check without the keyboard walk, or Rendered check.
  • Your pages are never sent to another service.

How does it work?

  1. Schedule your pages

    Scheduled checks read each page's markup on your server, and mark the page as waiting for a rendered check.

  2. Choose your browser

    Turn on the background pass, press the button on Page checks, or run the command on a machine with Chrome.

  3. Read the result

    Each page shows which checks it has had, so nothing looks more complete than it is.

Who is it for?

  • Sites that cannot send pages to a cloud

    Public bodies and clients with strict data rules keep every page on systems they control.

  • Developers with a build pipeline

    Run the check from a scheduled job and fail it while pages are still waiting.

Good to know

How it behaves, what it needs, and where its limits are.

Plans
Included in every Pro plan.
The one-time pass
wp lumtera-pro rendered run makes a one-time sign-in address that works once, for two minutes, and only its hash is stored. It does not appear in the process list or server logs.
Pause and resume
Whoever paused the background pass can see that on the card and resume it.

Questions

Something else on your mind? Contact support

Does it need a cloud account?

No. It uses a browser you control, and nothing is sent to MantraBrain or anyone else.

Does the background pass run while I edit?

No. It does not run in an editor. It loads pages due out of sight while an administrator uses the dashboard, lists or Lumtera screens, and you can pause it.

Do I need all four?

No. One is enough, and you can mix them.

More in “Test live pages”

Rendered checks without a cloud

Get it with Lumtera Pro

In every Pro plan. Personal is $149 a year. Pro installs alongside the free plugin, and your settings and results stay.

14-day refund (opens in a new tab)Keeps working if you don't renew