Performance testing, Claude Code workflows, anti-forgery trust signals, and the engineering behind Site Check. No buzzwords. Evidence over claims.
Site Check is for fast verification at three levels. JMeter is for journey-driven, multi-region, distributed load. Here's where the line between them actually sits.
Patterns we see across AI-built sites: what they almost always pass, what they almost always fail, and the three changes that move the score most.
An honest audit of every Claude Code skill in our install, cross-referenced against trending round-ups. Ten skills that matter, three that are worth trying, and one we skip on purpose.
Most feature requests we get are too vague to act on. Here's what makes one ship the same week, and what gets quietly archived.
We sell two paid certificates. Each one issues a different verifiable artefact. Here's exactly what you get for each price point and where the cert lives.
Walk blocked, timeout, certificate failure, redirect loop, and the dreaded "no pages fetched" — translated into plain English with what to do next.
Single performance scores are useless without context. Here's how the baseline comparison view works and what to look at first when a release lands.
Most NFRs we see are aspirational. Here's how to set thresholds that catch real regressions without crying wolf.
BLOCKED isn't BROKEN. Here's what it actually means, why it happens to enterprise sites, and the three options to get a real reading.
The five numbers on every Site Check report and what each one tells you about real users. Skip the technical jargon, read the actionable bit.
Three test levels, three different questions answered. A practical guide to which one fits your site, your stage, and your budget.
First time on Contexta? This is the 60-second version. What Site Check does, what the two scans tell you, and what to do with the result.