Web application performance monitoring
WebMonitor doesn't time your pages — it reads them. Catch the content regressions performance dashboards miss: broken templates, missing sections, error text, and vendor incidents.
WebMonitor.fyi is not a page-speed tool: it doesn't measure load times, Core Web Vitals, or response times — for those, use Lighthouse, PageSpeed Insights, or an APM platform. What it adds alongside them is content-level regression monitoring. After a deploy or a third-party change, the AI checks that key pages still render what they should — the pricing table is present, the signup form loads, no error text crept in — and emails a plain-English summary when something breaks. It can also watch the public status pages of your CDN, host, and critical vendors and alert when a degraded-performance incident posts.
What it does
Content regression checks
Describe what must be on the page ("the pricing table with three plans", "the checkout button"). On each check, the AI confirms it's still there and alerts when it isn't.
Vendor status-page monitoring
Point a monitor at the public status page of your CDN, host, or payment provider. Get an alert when a new incident or degraded-performance notice posts.
Plain-language criteria
No scripting or selectors — write what a regression looks like in normal words, and the AI reads the page's meaning rather than matching pixels or markup.
No alert noise
Smart deduplication fires once per detected problem and stays quiet while nothing changes — no re-alerts on every check.
How to set it up
Pick the pages worth tracking
High-traffic SEO landing pages, the homepage, key conversion-funnel pages, and the status pages of critical vendors.
Describe what should be there
One plain-language criterion per page: "alert me if the pricing table is missing or any error message appears".
Set a frequency
30-minute or hourly checks (Pro) around deploys and campaigns; daily for steady-state pages.
Route the alerts
Email by default; a Slack webhook for team visibility; a generic JSON webhook into your own tooling.
Common use cases
- Engineering teams catching post-deploy content breakage on key pages
- SEO teams making sure ranking-critical pages keep rendering their content
- Marketing teams confirming landing pages stay intact during paid campaigns
- Operations teams watching vendor status pages for degraded-performance incidents
- Product teams confirming conversion-funnel pages still render what they should
Honest limits
WebMonitor does not measure response times, Core Web Vitals, or load metrics, and it doesn't run multi-region probes or real-user monitoring. It reads page content on each check, as often as every 30 minutes. For timing data, use PageSpeed Insights, Lighthouse CI, or an APM platform — and use WebMonitor to catch the content failures those tools don't look at.
Frequently asked questions
Does this measure Core Web Vitals the same way Google does?
It doesn't measure Core Web Vitals at all — WebMonitor reads page content, not timing. For LCP, INP, and CLS, use the Search Console Core Web Vitals report or PageSpeed Insights. WebMonitor complements them by catching content regressions on the same pages.
Can I monitor specific transactions, like a checkout flow?
Each monitor watches one page, so multi-step transactional monitoring (login → add to cart → checkout) isn't supported. The practical approach: monitor the key single pages in the flow — the cart page, the checkout entry page — for error text or missing content.
How does this compare to Datadog Synthetics or Catchpoint?
Different categories. Those platforms measure timing and run scripted multi-step checks across regions. WebMonitor is lightweight content monitoring: it tells you when a page stops showing what it should, in plain English, for a few dollars a month.
Related
Try it on the page you want to monitor
Free to try. No credit card. Paste a URL, write a criterion, see the analysis.
Start free