A deep, human read on your whole product.
Radar watches your product every day; once in a while it pays to sit down and read the whole picture in depth. Product Health Check runs the same checkpoints Radar watches, experience, performance, security and the technical stack, as a one-time, 360° audit, then an expert reads and prioritizes the findings into a clear verdict of what's wrong and what to fix first.
Where it fits
Care · periodic. Product Health Check and Radar cover the same checkpoints. Radar watches them continuously, Product Health Check audits them once, in depth, with an expert reading the results. It's the 360° snapshot: what's strong, what's risky, what to fix first. When you want those fixes made, the work routes straight into Product Support & Optimization.
Who it's for
Teams about to invest, a redesign, a scale-up, a hand-off, a funding round, who want an expert, prioritized read on what's strong, what's risky, and what to fix first. And teams who simply want a periodic deep check that goes beyond automated alerts.
What you get
- A full written audit across experience, performance, security and the technical stack
- Findings ranked by severity and effort, so you know what to do first
- Expert recommendations, not just a list of problems
- A clear roadmap into Product Support & Optimization
- An executive summary your stakeholders will actually read
What we check
Nineteen checkpoints across design, code, infrastructure and growth, each inspected by hand and shown here as cards, pulled live from our Techniques library.
Deployments
Expert review of how code reaches production.
- What
- Release process, environments, rollback safety and deployment hygiene.
- How
- A person walks the deploy pipeline and history, looking for risk.
- Purpose
- Bad deploys cause most outages, so we find the gaps before one bites.
- When
- During each Product Health Check.
Security Keys
A hands-on audit of credentials and access.
- What
- Secrets, API keys, admin accounts, file permissions and config hardening.
- How
- Manual inspection against a hardening checklist: wp-config, headers, permissions, key rotation.
- Purpose
- The quiet security gaps automation misses are where breaches start.
- When
- During each Product Health Check.
Plugins
A judgment call on every plugin you run.
- What
- Versions, known CVEs, abandoned or risky plugins, and what can be removed.
- How
- Manual review of active vs installed plugins against vulnerability data.
- Purpose
- Plugins are the most common attack surface, so we keep them fewer, safer and current.
- When
- During each Product Health Check.
Documentations
A check that the product is actually documented.
- What
- Setup, architecture, access and runbooks: what exists and what's missing.
- How
- Expert review of existing docs against what a new team would need.
- Purpose
- Undocumented products are fragile and expensive to hand off.
- When
- During each Product Health Check.
AI Audit Summary
AI that turns a messy audit into one clear report.
- What
- All human and automated findings, deduplicated and prioritized.
- How
- AI compiles, ranks by severity and effort, and drafts the executive summary.
- Purpose
- You get a decision-ready report, not a pile of notes.
- When
- At the end of each Product Health Check.
AI Accessibility Scan
AI-assisted accessibility pass across the product.
- What
- WCAG issues: contrast, labels, structure, keyboard and screen-reader gaps.
- How
- AI scans pages and flags violations with remediation hints for the team.
- Purpose
- Accessibility is easy to miss by eye and costly to ignore.
- When
- During each Product Health Check.
SSL Certificates
Always-on check that your site's security certificate is valid and won't lapse.
- What
- Certificate validity, chain, and days-to-expiry across every domain and subdomain.
- How
- Automated daily TLS handshake against each endpoint; expiry thresholds trigger early alerts.
- Purpose
- An expired certificate breaks trust and blocks visitors instantly — we catch it weeks ahead.
- When
- Checked daily; alerts fire well before expiry.
Server Metrics
Continuous watch on the health of the server behind your product.
- What
- CPU, memory, disk usage and overall system load.
- How
- Automated polling of host metrics with thresholds tuned to your stack.
- Purpose
- Strain shows up here long before users feel a slowdown — we act before it bites.
- When
- Continuous, sampled around the clock.
Uptime Events
Round-the-clock confirmation that your site is actually reachable.
- What
- Up/down status plus the duration and cause of any outage.
- How
- Automated checks from multiple locations; a confirmed outage alerts instantly.
- Purpose
- Downtime costs revenue and trust by the minute — you hear it from us, not your customers.
- When
- Continuous, with near real-time alerting.
Backups
Verification that your safety net is real, not assumed.
- What
- Whether scheduled backups ran, completed, and can actually be restored.
- How
- Automated check of backup jobs and the integrity of the latest snapshot.
- Purpose
- A backup you can't restore is no backup — we confirm recovery is possible before you ever need it.
- When
- Checked after each scheduled backup; reviewed weekly.
Speed Monitor
Ongoing measurement of how fast your pages really load.
- What
- Load time, Core Web Vitals and performance scores, trended over time.
- How
- Automated lab and field measurement on key pages, compared week over week.
- Purpose
- Speed is conversion and SEO — we catch regressions before they cost rankings or sales.
- When
- Weekly full run; on demand after releases.
Integrity Scan
A sweep for anything that shouldn't be in your codebase.
- What
- File-integrity changes and known malware signatures.
- How
- Automated scan comparing current files against a trusted baseline.
- Purpose
- Catches a compromise early — quietly altered files are how most hacks hide.
- When
- Weekly full scan; alerts on any unexpected change.
Mozilla Observatory
Your site's security posture, graded against best practice.
- What
- HTTP security headers, TLS configuration and an overall letter-grade score.
- How
- Automated assessment via Mozilla Observatory, tracked over time.
- Purpose
- Hardened headers close common attack vectors — we keep your grade from slipping.
- When
- Weekly; re-checked after infrastructure changes.
SEO Audits
A regular health check on how findable your product is.
- What
- Indexing, metadata, broken links, structured data and technical SEO signals.
- How
- Automated crawl and audit, with deltas tracked against the previous run.
- Purpose
- SEO erodes silently — we surface slips while they're still cheap to fix.
- When
- Weekly audit; trend report monthly.
Tickets
A read on the volume and responsiveness of your support.
- What
- Open ticket count plus response and resolution times against SLA.
- How
- Automated tracking from your support channel, summarized into trends.
- Purpose
- A rising queue or slipping SLA is an early warning — we see it before it becomes churn.
- When
- Continuous; summarized weekly.
Templates
A check that your site's building blocks stay consistent and current.
- What
- Template and component versions against the approved baseline.
- How
- Automated comparison flagging drift or outdated versions.
- Purpose
- Inconsistent templates cause subtle breakage — we keep the foundation clean.
- When
- Weekly.
Code Quality Review
Expert review of the codebase's health.
- What
- Project structure, dependencies, versions, technical debt and fragile points.
- How
- A senior engineer reads the code and error logs, mapping risk.
- Purpose
- The fragile spots are invisible until they break, so we find them first.
- When
- During each Product Health Check.
Database Audit
A look under the hood at your data layer.
- What
- Table sizes, autoload, transients, orphan tables and duplicate content types.
- How
- Direct queries and analysis, with a concrete cleanup plan.
- Purpose
- A bloated, messy database silently slows everything, so we trim it safely.
- When
- During each Product Health Check.
Performance Audit
A human read on why the product feels slow.
- What
- Core Web Vitals, slow queries and cache strategy.
- How
- Measured, then diagnosed by an expert, not just a score.
- Purpose
- Speed is conversion and SEO; the fix needs a cause, not a number.
- When
- During each Product Health Check.
A complete picture: not a green-light dashboard, a considered verdict.
Expert eyes, not just a score
Radar can tell you a page is slow; Product Health Check tells you whether it matters, why, and what to do about it. The same signals, read by a person, findings weighed, ranked by severity and effort, and the judgment calls a dashboard can't make (the checkout that feels untrustworthy, the empty state that confuses first-time users) added on top. You leave with a prioritized plan, not a wall of numbers.
AI assists the audit
AI carries the heavy, repetitive load so our experts spend their hours on judgment, not legwork.
AI Audit Summary
Compiles human and automated findings into one prioritized report.
AI Accessibility Scan
An AI-assisted WCAG pass with remediation hints.
How it runs
A human-led, one-time engagement with a fixed deliverable: the 360° audit, a prioritized list of findings, and the roadmap to fix them. A typical audit runs 1–2 weeks. Run one periodically, and always before a major investment. When you want the findings actually fixed, that work moves to Product Support & Optimization, and Radar keeps watch on the same checkpoints between audits.
Scoped to your product's size and complexity, a one-time engagement with a fixed deliverable. Typical duration 1–2 weeks. From $400.
Backed by fifteen years, 10,000+ screens, 90+ products shipped, and 35M people a month.
Questions, answered
They cover the same checkpoints. Radar is automated and always-on, watching those signals around the clock. Product Health Check audits them once, in depth, with an expert reading the results and judging the things a scan can't, like whether a flow feels trustworthy or content lands. Most teams run both: Radar between audits, Product Health Check at the milestones that matter.
Nineteen checkpoints across design, code, infrastructure and growth: experience and UX, performance, security, the technical stack, accessibility and content. Some of it overlaps what Radar measures, but here it's inspected by hand and read in context, not just scored.
A written audit with findings ranked by severity and effort, expert recommendations (not just a problem list), a clear roadmap into Product Support & Optimization, and an executive summary for stakeholders.
No. Product Health Check diagnoses and prioritizes. The fixes and the improvements happen in Product Support & Optimization, so you decide what to act on with a clear roadmap in hand.
Periodically, and always before a major investment like a redesign, a scale-up, a hand-off or a funding round. Between audits, Radar keeps continuous watch so nothing drifts unseen.
No. Product Health Check is a standalone engagement. They simply complement each other: Product Health Check is the deep periodic read, Radar is the always-on watch in between.
A typical audit runs 1–2 weeks and starts from $400. The exact timeline and price depend on the size and complexity of your product. Tell us about it and we'll scope the audit after a short call.
Start
Tell us about your product and we'll scope the audit.
Related services
Product Health Check is one part of how we keep products healthy.
