In short
Vibe Monitoring watches the site your users see. Add a URL to a project and VibeDoctor checks it every few minutes, recording whether it is up, how fast it answers and when it went down. Each URL scan adds a deeper look: Lighthouse performance, security headers, SSL, console errors, broken links and page weight.
Uptime checks
Once a project has a URL, VibeDoctor checks it on a schedule and shows:
- whether the site is up right now, and its uptime percentage;
- how fast it answers, now and on average;
- each incident: when it went down, when it came back and how long it lasted;
- how many days are left on its SSL certificate.
| Plan | Checked every |
|---|---|
| Free Week | 5 minutes |
| Watch | 3 minutes |
| Guard | 1 minute |
| Shield | 1 minute |
Monitoring runs during your Free Week and on every paid plan.
What every URL scan measures
A URL scan loads your site in a real browser and measures what your users get.
Performance
| Metric | What it measures | Good |
|---|---|---|
| LCP | When the largest content finishes rendering | Under 2.5 s |
| FCP | When the first content appears | Under 1.8 s |
| CLS | How much the layout jumps while loading | Under 0.1 |
| TBT | How long the page is blocked from responding | Under 200 ms |
| Speed Index | How quickly the visible page fills in | Under 3.4 s |
Security headers
HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy. AI tools rarely add them, and most hosts do not add them for you.
SSL
Whether the certificate is valid, who issued it, how many days it has left and which TLS version it uses.
Errors, links and weight
JavaScript errors in the console, internal links that return 404, total page size and request count, and resources loaded over HTTP on an HTTPS page.
Code and live site in one place
Some problems only show in the code, like leaked secrets or a vulnerable package. Others only show on the live site, like a slow page or an expiring certificate. Add both a repository and a URL to one project and every scan checks both, in one report with one score. For the code side, see Vibe Check.
When something looks wrong
| What you see | First step | Lasting fix |
|---|---|---|
| Site down | Check your host's status page; restart the service if you host it yourself | Add a health endpoint and a second instance |
| Certificate running out | Renew it or trigger the auto-renewal | Check that auto-renewal is set up |
| Performance dropped | Look at the latest change for heavy imports or large images | Set a performance budget; lazy-load heavy parts |
| Console errors | Open the browser's DevTools on the live site | Add error boundaries, null checks and error handling |
| Missing security headers | Add them in your host's config (vercel.json, next.config.js, Caddyfile) | Keep one header template for every project |
Every finding in your report has a fix prompt to paste into your AI coding tool.
FAQ
How often does VibeDoctor check my site?
Every 5 minutes during the Free Week, every 3 minutes on Watch, and every minute on Guard and Shield.
Can I monitor a site without a GitHub repository?
Yes. A URL-only project gets uptime checks and the live-site scan. The code checks need a repository.
Does monitoring cost extra?
No. It is part of every paid plan and of the Free Week.
Does VibeDoctor replace a dedicated uptime tool?
It is built for founders who want one place for their code and their site. If you need checks from many regions, status pages or incident workflows, a dedicated uptime tool fits better.
How steady are the Lighthouse scores?
Scores move a little between runs, as Lighthouse always does. The trend over several scans is the reliable signal.
Want the long version? Read Vibe Monitoring: uptime, performance and SSL for vibe-coded apps.