The platform

Three questions, one workspace.

Can people use it? Is the design right? Is it fast, and does it hold up? Every page below answers one of them, and every number on it says whether it was measured or predicted.

Start testing free See how it works

Usability
Design
Performance
Every page
Teams
The rules

Search studies, sessions, themes…AI chat

← Checkout redesign — payment stepResults

Usability score71/100sample study

AI sessions18simulated · labelled

Human sessions6by link · consented

Goal reached58%14 of 24 sessions

Calibration: AI vs human

Completion gap11pp apart22% — outside ±5%

Ease gap0.1 apart3% — within ±5%

Time gap—not measured on one side

Completion AI61% (n=18) Humans50% (n=6)Legend simulated human testers

Ease rating, 1–5Mean — AI 2.9 · Humans 3.012345

Usability — can people use it?

Three moves, in the order a study makes them

Each one is a page of its own. Beside them: the tester library, the study builder, and Journeys for the visitors who arrive on their own.

Test it with AI, now

A cohort of any size at once — in seconds, or live in a real browser.

Confirm it with people

One link or QR code. Consent first. Sessions land beside the AI’s.

Hand over the evidence

Findings ranked, AI and human side by side. Present, share or export.

Design — is the design right?

Four audits. No study, no tasks, no testers

An expert read of the screen, the words, every screen size or the build — back in minutes.

UX Audit

One screen, one goal, ranked findings. Every finding a prediction.

Get a backend engineer to start a free trialPasted copy6 registers

Measuredfrom the copy itself — reproducible1 finding — 1 worth fixing before you ship. 2 rewrites ready.Findings by severity

Findings 1Rewrites 2

Body paragraph · ClarityMeasured9 words describe the product, not the person using it.

Now

InsteadPush your code. We handle provisioning, scaling and rollbacks — so you're not paged at 2 a.m.

Sentence length · long from 25Passive voice · 2 of 1 clausesLongest 30 wordsProduct words, not people wordsleverageholisticrobustseamlessecosystemempower

Read forSearchClarityVoiceCalls to actionTrustScannability

Content Audit

Six registers. Measured and judged kept apart. Rewrites ready to paste.

shop.example.com/checkoutLive website5 sizesCheck again

Responsive verdictHolds from 1440 down to 768px, and breaks at 390px and below.

320Small phoneBreaks

390iPhoneBreaks

768Tablet uprightHolds

1024Tablet sidewaysHolds

1440DesktopHolds

Issues to fix8from 13 findings

Sizes that break2 of 5holds at 768, 1024, 1440px

Most serious1 critical2 major · 5 minor

How it was found11 measured2 predicted by AI

The AI’s read · a prediction, medium confidenceFrom 768 up the two columns hold; at 390 the total only shows on the pay button.

Every check at every size5 of 15 checks found something · 47 of 56 passed · measured, not guessedOnly what failed

32039076810241440

Mobile viewport tag–––

Sideways scrollingCriticalCritical

Content cut off at the edge

Clipped or truncated text

Overlapping text

Text too small to readMinorMinor

Body text size on phones–––

Form fields that zoom the pageMajorMajor–––

Tap targets too smallMajorMajor–

Fixed bars covering the screen–

Stretched or squashed images

Images that fail to load

Oversized headings on phones–––

Lines too long to read––––Minor

Content missing at this size–

Responsive Audit

One design at phone, tablet and desktop widths. Measured checks name their rule and the size where it breaks — no score, on purpose.

Fidelity

The design and the built screen side by side, scored on how close they are, with every comparison saved so you can watch a screen improve.

Performance — is it fast, and does it hold up?

Measured, never predicted

Tests against a domain you have proved you own, and the speed your real visitors get.

Search studies, sessions, themes…AI chat

← PerformanceStorefront✓ shop.example.com · verifiedproductionstaging

SuitesEnvironments & domainsRequests & loadReal usersMonitoring & alerts

LCP · p752.1 s Good · 1,240 real visits

Checkout API14/15 Passed · 3 min ago

Monitors3 of 3 up certificates valid

Alerts1 firing Slow INP → Slack

LCP p75production · real visits1 h6 h24 h72 h7 d

3.0 s2.5 s2.0 s1.5 s

good ≤ 2.5 sv2.4.0v2.4.1v2.4.2

6 Oct8 Oct10 Oct12 Oct

SuitesNew suite

Checkout APIAPI · Every hour14/15Passed

Storefront pagesPageSpeed · Every day12 pagesPassed

Account APIAPI · Every 6 hours9/9Passed

Alerts4 rules

Slow INPINP p75 above 200 ms · productionFiring

Slack sent today, 09:12Checkout API downOKStaging certificateOKCheckout API suiteOK

Performance testing

API suites run as one signed-in session, load tests you can shape, PageSpeed across your pages, uptime and SSL monitors, and alerts in Slack, Teams or a signed webhook. Verified domains only.

StorefrontSuitesEnvironments & domainsRequests & loadReal usersMonitoring & alertsproduction1 h6 h24 h72 h7 d Receiving data

LCPiGoodLargest Contentful Paint2.1 sp75 · 1,240 visits

INPiNeeds workInteraction to Next Paint240 msp75 · 1,240 visits

CLSiGoodCumulative Layout Shift0.04p75 · 1,240 visits

FCPiGoodFirst Contentful Paint1.4 sp75 · 1,240 visits

TTFBiGoodTime to First Byte620 msp75 · 1,240 visits

iINP · Interaction to Next PaintAfter a click, a tap or a key press, how long until the screen shows the response.Good ≤ 200 msPoor > 500 msWhen it is badHeavy JavaScript on the main thread, long React renders, or long lists rendered at once.See Slowest components →

Slow pagesLCP p75 · events

/search3.4 s860

/orders/:id2.8 s312

/product/:id2.4 s2,140

/checkout2.3 s540

/shoes2.0 s1,310

/1.8 s3,020

/orders/123 → /orders/:id

Slowest componentsp95 render

<ProductGrid>64 ms2,300 renders

<CartDrawer>41 ms1,120 renders

<ReviewList>22 ms880 renders

<SearchBox>18 ms3,410 renders

One frame is 16 ms

Frontend errors4.1 per 1,000

Cannot read properties of undefined (reading 'price')41 times

ChunkLoadError: Loading chunk 812 failed12 times

Real-user monitoring

The Web Vitals real visitors get at p75, from one npm package — slow pages and components, each deploy marked, the visitors who have it worst, and what to fix first.

Everything in the platform

Every page, by the question it answers

Nothing here is on a roadmap.

UsabilityCan people use it?

AI testing

A cohort of AI testers attempts your task at once, thinking aloud, streamed live.

Open

Human testers

One share link, consent built in — or a live, recorded call when you want to ask why.

Open

The study builder

Missions and thirteen question-block types in one ordered list.

Open

Tester library

Built-in archetypes and your own — traits that change how a session goes.

Open

Journeys

The paths real visitors take through your live site, and where they struggle.

Open

DesignIs the design right?

UX Audit

One screen, one goal — ranked findings and a blueprint, no testers required.

Open

Content Audit

The words read against their job — six registers, reading level measured, rewrites ready to paste.

Open

Responsive Audit

One design at phone, tablet and desktop widths — measured checks that name their rule.

Open

Fidelity

What shipped against what was designed — scored overall and per category, every comparison kept.

Open

PerformanceIs it fast, and does it hold up?

Performance testing

API suites as a signed-in session, load tests, PageSpeed and uptime monitors.

Open

Real-user monitoring

The Web Vitals real visitors get, deploys marked, and what to fix first.

Open

Across all three

Evidence & reports

Ranked findings, scored tasks, and a report you can hand over.

Open

Integrations

Findings to Jira, Linear, Notion, Slack and more — and to coding agents over MCP.

Open

Around the studies

The parts that make it a workspace, not a tool

A workspace per client, roles per area, and a bill you can read line by line.

the billing page · one pool of credits, and where they went

A workspace per client

One organization can hold as many as you need. Studies, testers and reports stay inside the workspace they belong to, so nothing from one client is visible in another.

Roles and per-area access

Admin, member or guest, with each person's areas ticked under usability, design and performance — so a stakeholder can read a report without being able to start a run.

A bill you can read

One pool of credits for the whole account, a published price per action, and a breakdown of where the credits went — by kind of work and by workspace, with a budget per workspace if you want one.

Handing work out

Share a read-only report link, export a PDF, or send the findings to a coding agent as a work order. None of it needs an account on your side.

Two colleagues reviewing a session together at a laptop — a review, the morning after a run

What it never does

The rules the product keeps about its own numbers

Enforced in the product, not promised on a page.

Simulated is labelled simulated

Anything the AI predicted is labelled in the results, in the PDF, and on any link you share.

An estimate never wears a measurement's clothes

A predicted number says it is predicted; a measured one says how many sessions it came from.

Unmeasured says unmeasured

A metric nothing recorded says “not measured” — never a zero, which would read as a real result.

Human testers consent first

Nothing is recorded until the tester has agreed, and screen recording is a separate question again.

The tester app

Test from your pocket

The uTestMe tester app runs a study on a phone. Taps and screens recorded, consent first, results in the same view.

Coming soon onApp StoreGet it onGoogle Play

Scan to install

Tap tracking
Screen recording
Consent first

Test code · K7F2-9QA