Skip to content
In development

Tenvey is not running yet. Every number on this site comes from one example website, not from a live service. What that means

Tenvey

Guide

Getting started

Adding a website takes one field and no code. This page covers what happens after that: the first minute, the checking schedule, and how to read what Tenvey sends back.

Add your website

Open the dashboard and paste the address of the page you want watched, or run a one-off scan from the scan page first if you would rather see the output before signing up.

  1. Enter the address. yourwebsite.com, https://yourwebsite.com and https://www.yourwebsite.com/ are all accepted — Tenvey normalises the scheme and follows redirects to the address that actually answers.
  2. Tenvey fetches the page once to confirm it is reachable. If it answers with a status other than 2xx, or does not answer at all, you get the reason rather than a spinner.
  3. The first check starts immediately. You do not install a tag, change DNS or deploy anything.

Monitor the address your visitors use. Watching https://www.yourwebsite.com when everyone lands on https://yourwebsite.com measures the redirect instead of the site.

The first 60 seconds

The opening pass runs in about six seconds and is deliberately readable while it works — each step names itself and stays on screen once it is done.

  • 0–1 s — Tenvey resolves the host, follows redirects and fetches the page.
  • 1–3 s — it measures performance: time to first byte, largest contentful paint, transfer size, render-blocking requests.
  • 3–4 s — it reads the SEO tags: title, meta description, canonical, heading structure, robots directives.
  • 4–5 s — it verifies the TLS certificate and the response headers.
  • 5–6 s — it scans the rendered page for accessibility problems.

At that point you have a health score and the first issues. For the rest of the minute the crawler follows internal links and /sitemap.xml to find the other pages on the site, up to the page limit of your plan. At 60 seconds the first scheduled uptime check runs, and from then on it repeats every minute.

How checks work

Uptime, every 60 seconds

Every minute, Tenvey requests your address from Frankfurt FRA, Washington IAD and Singapore SIN, and records the status code and the response time for each. A check counts as failed only when at least two regions agree, so one bad network path between Singapore and your host does not wake you at three in the morning.

Full checks and crawls

The complete pass — performance, SEO, security, accessibility — runs every six hours, and again within two minutes of a deployment if you send Tenvey a deployment webhook. The crawl that discovers new URLs runs once a day. Every check keeps the status code, response time, response headers and an HTML snapshot, which is what lets Tenvey show you a change as a difference between two pages rather than as an assertion.

Let Tenvey through

Tenvey identifies itself on every request and never pretends to be a browser:

TenveyBot/1.0 (+https://tenvey.com/docs)

If a firewall, rate limiter or bot filter sits in front of the site, allow that user agent. The crawl obeys robots.txt, so a blanket disallow leaves Tenvey with one page to look at:

User-agent: TenveyBot
Allow: /
Crawl-delay: 1

The 60-second uptime check ignores robots.txt for the single address you entered, because that request is the measurement — but it is one request per region per minute and it is not a crawl.

How to read an issue

Every issue is written at three depths, so the same record works for the person who has to decide and the person who has to fix it. A real one from the demo dashboard:

  • Checkout returns a server error — what is wrong, in one line.
  • 128 requests to /checkout returned a 500 in the last 24 hours, starting 14 minutes after deployment v2.4.1 — the measurement behind the line.
  • POST /checkout → 500 Internal Server Error · 128 occurrences — the raw evidence, shown when you expand the issue.
  • Next step: roll back v2.4.1 or fix the payment handler it changed. Every issue names one, and it is always an action rather than a goal.

Severity is ranked by consequence, not by category. Critical means visitors are being turned away right now. Warning means it will cost you soon — an expiring certificate, a page that got 1.8 s slower. Info means it is worth fixing on a normal working day. An issue closes itself when a later check no longer finds it, and the record stays so you can see what changed and when.

Where to go next