SpeedInts docs

Documentation

Everything you need to monitor speed, understand your reports, and automate performance with SpeedInts.

On this page

Start here

SpeedInts monitors page speed, Core Web Vitals, SEO checks, domain health, visual changes, and alerts for the websites you manage.

Create your first monitor

Add a production URL, choose how often SpeedInts should test it, then save the monitor. No script tag, browser extension, or site deploy is required for lab-based monitoring.

Choose URLs to track

Start with pages that affect acquisition or revenue: home page, pricing page, key landing pages, high-traffic templates, and paid campaign destinations.

Read your first report

Each report groups performance metrics, SEO checks, accessibility findings, best-practice issues, and domain health signals so teams can decide what to fix first.

Lab speed tests

Lab tests create repeatable measurements for the same page over time. Use them to catch regressions after deploys, plugin changes, design updates, tracking changes, and CMS edits.

Best first setup

Track the same URLs on a fixed schedule. Keep your test list short at first, then add templates once the first alert rules are tuned.

Core Web Vitals

SpeedInts tracks LCP, INP, and CLS alongside supporting diagnostics like render delay, request timing, page weight, and blocking resources. Use the trend view to confirm whether fixes improved the page.

Domain health

Domain checks cover TLS certificates, DNS, email records, security headers, robots rules, structured data, and AI crawler readiness.

Reports and alerts

Use alerts for threshold breaks and use reports for client communication. This keeps urgent issues separate from recurring optimization work.

Alerts

Start with a small set of alert rules for pages that matter. Add more rules after your team has seen a few normal fluctuations.

Client reports

Share reports when you need a compact record of what changed, what is slow, and what the next implementation step should be.

Visual changes

Screenshot comparisons help catch page changes that performance metrics alone can miss, including broken layouts, missing modules, and unexpected template updates.

API and MCP

Teams can pull SpeedInts data into internal dashboards, client portals, automation jobs, and MCP-ready assistants.

API overview

Use the API to retrieve monitored sites, latest reports, historical checks, issue details, and report links.

MCP server

The SpeedInts MCP server lets AI assistants list monitored websites, trigger speed tests, inspect speed history, review reports, check visual changes, and list active alert configurations without copying data manually.

Need help?

If you are not sure how to interpret a report or set alert thresholds, contact the SpeedInts team and include the URL you are monitoring.