What is automated Lighthouse testing?

It runs Lighthouse audits for a saved public page on a recurring schedule and stores the completed results. This replaces ad hoc reminders with a consistent set of lab measurements you can compare over time.

How often can NEKTIQA run scheduled tests?

Simple supports daily and weekly schedules. Pro also supports every-four-hour and every-eight-hour intervals. The interval is configured separately for each project page.

Can I schedule mobile and desktop tests?

Yes. A page can test mobile, desktop, or both. The two strategies create separate Lighthouse runs and separate analysis baselines; choosing both uses two tests per scheduled interval.

Will a scheduled test run at an exact time?

No exact minute is promised. NEKTIQA checks due schedules regularly and deliberately spreads execution around the target interval, so treat daily or weekly as a cadence rather than a calendar appointment.

Does automated testing send regression alerts?

Not currently. Scheduled tests build the history used to review changes, but NEKTIQA does not yet send score-drop alerts or act as a CI deployment gate. The results are Lighthouse lab data, not real-user monitoring.

Automated Lighthouse testing

Schedule Lighthouse tests before manual checks get skipped

Choose the pages, device strategies, and testing rhythm that matter. NEKTIQA runs repeatable PageSpeed Insights audits and adds each completed result to the same performance history.

Run a free Lighthouse test View pricing

Per-page schedules · Mobile, desktop, or both · Monthly usage estimate before saving

Auto-test schedulerhttps://storefront.example

Example data

Active — runs 3 times a day, testing Both (mobile + desktop)

Scheduler settings: choose a repeatable cadence and see its estimated monthly usage.

Replace reminders with a system

Performance changes between the audits you remember to run

A recurring schedule creates comparable checkpoints without asking someone to open a testing tool every day. Each page keeps its own setting, so the testing rhythm can follow how often that part of the site changes.

Configure each page

Turn automatic testing on for a specific project page instead of applying one schedule blindly to every URL.

Choose the device baseline

Schedule mobile, desktop, or both strategies and keep their Lighthouse results separate in analysis.

Understand the cost

Review the estimated 30-day test usage before saving; testing both strategies consumes two tests per interval.

A small setup

From one public URL to a recurring Lighthouse history

Intervals depend on the active plan. They define a testing rhythm, while the scheduler deliberately spreads work rather than promising an exact wall-clock minute.

Every 4 hours · ProEvery 8 hours · ProDailyWeekly

Select a project page

Add the public page you want to monitor and open its scheduler settings in the dashboard.

Set interval and strategies

Choose an interval available on your plan, then test mobile, desktop, or both device strategies.

Review the accumulated evidence

Completed scheduled runs appear with manual tests in charts and run history for the same page and strategy.

Automation with an audit trail

Every completed scheduled test becomes a result you can inspect

Automation is most useful when it leaves more than a current score. NEKTIQA keeps the dated summary, trends, and recent detailed audit together.

One timeline for manual and scheduled runs

Compare a test you started yourself with the recurring checks that ran between releases.

Separate mobile and desktop history

Review like-for-like results without treating two Lighthouse environments as the same baseline.

Category scores and lab metrics

Follow Performance, Accessibility, Best Practices, SEO, LCP, CLS, FCP, and TBT over time.

Recent audit detail

Open a retained detailed result when a trend or history row needs closer investigation.

Explore performance history

Historyhttps://storefront.example

Example data

Manual test

Status	Perf	SEO	A11y	Best	LCP	CLS	TBT
Success	93	97	95	98	1980ms	0.030	100ms
Success	88	97	95	98	2470ms	0.040	160ms
Success	85	96	94	97	2840ms	0.050	210ms
Success	82	96	94	97	3110ms	0.060	250ms
Success	83	96	94	97	3020ms	0.060	240ms
Success	77	96	93	97	3610ms	0.080	330ms
Success	70	95	92	96	4320ms	0.100	440ms
Success	66	95	92	96	4860ms	0.120	520ms
Success	87	96	93	97	2580ms	0.050	170ms
Success	89	96	93	97	2360ms	0.040	140ms

Run history: scheduled and manual tests stay visible in the same dated record.

Questions

Automated Lighthouse testing FAQ

Start with a baseline

Run the first test now, then let the schedule build the comparison

Try one public URL for free. When you are ready for recurring checks, choose the plan and cadence that fit how often the page changes.