What it does: Runs Lighthouse against a list of the site’s own pages once a day through the operator’s own PageSpeed Insights key, and draws the result as a second line on the free trend chart beside what real visitors measured. How to access: VelocityForge > Monitoring, in the panel below the chart. Notes:

• The key, the Google quota and the billing relationship are the operator’s. The site calls Google directly; nothing is proxied through Avakode and we never see the key, which is encrypted at rest with a value from wp-config.php and is never shown back.
• The panel’s status line is the run’s own: nothing started says nothing, an open run says “Queued at HH:MM UTC”, and a finished one repeats exactly the wording the history table uses (completed / partial / failed / timed out, with the counts) so the line and the table can never disagree.
• Results are ordinary rows in the ordinary profile table, so the trend, the regression history, the e-mail and the Telegram / Slack / webhook alerts all treat them like any other measurement — but never compare them against a real visitor’s measurement.
• Lab runs band TBT along with LCP, CLS and TTFB (§11).
• Useful exactly where field data cannot help: a page nobody has visited yet, a staging site, a change made at midnight.