Skip to main content
Start for free

Release quality

Catch drops before the client does.

Insight shows which URLs dropped after a release.

Start a release check How it works

Result comparison from the Growth plan

Release Sep 29, 6 URLsExample
  • /pricing 8871 New chat script blocks rendering
  • /contact 8578 “Send” button has no name

The situation

Shipping the code does not finish the website check.

Template or asset changes can affect the public site. Comparing audits helps identify areas for the release team to investigate.

Today

  • No quick diff after the public version ships.
  • Regressions mix with expected changes.
  • Unclear who should own a specific difference.

With Insight

  • A comparison with the pre-release result
  • A list of URLs where something dropped
  • A result to hand to the release owner

Project stages

One measurement from quote to ongoing care.

This scenario is one of five stages. The same audit runs at each one, so results compare.

  1. Before the project
    New client Specific site issues before you quote.
  2. During the project
    Redesign & migration Old and new version side by side. Project handover A dated report for sign-off.
  3. After launch
    Release quality Drops after a release, before the client sees them. You are here Ongoing care A monthly before-and-after of your fixes.

How it works

Three steps, one result.

You end up answeringWhich differences are expected, and which need investigation?

  1. Pick the key URLs

    Focus on pages the release changed or pages that bring in customers.

  2. Measure after the release

    Run an audit right after the new version goes live.

  3. Review the differences

    Separate drops to check from changes you expected, and pass them to whoever owns the release.

What you get

A list of drops for the release review

One document with a date, scope and sources. Share it with a link; the recipient needs no Insight account.

See a sample change report
Have ready
  • A result from before the release
  • The release date
  • A list of key URLs

Result comparison from the Growth plan

Limits

What Insight will not do here.

An automated audit is a starting point. What it cannot see stays with you.

Outside the audit
  • It is not a full QA or end-to-end test.
  • It does not monitor servers or infrastructure.
  • It does not replace code review or pre-release testing.
Methodology and analysis scope

What you use

Modules and industries for this scenario.

The Insight areas this scenario uses most, and the industries where it comes up most.

Compare a release on the same thresholds.

The Free plan needs no card. Comparisons and result history are on paid plans.

Start a release check All use cases
  1. 1 Pick the key URLsFocus on pages the release changed or pages that bring in customers.
  2. 2 Measure after the releaseRun an audit right after the new version goes live.
  3. 3 Review the differencesSeparate drops to check from changes you expected, and pass them to whoever owns the release.