Sign in Sign up free

Recording of the visual regression run on www.getsignalwise.com · signalwise — app walkthrough.

In this video· click a step to jump to it

W

Passed ✓

Test recording

signalwise — app walkthrough

24,312 ms · 1,348 pixels changed

We built this regression test for www.getsignalwise.com — it's yours to keep, free.

Take this test with you

This is a real Playwright test, recorded against www.getsignalwise.com. Claim it into your own workspace and re-run it on every deploy — free.

Claim this test — free Sign in to run it

export async function test(page, baseUrl, screenshotPath, stepLogger) {
  const STAMP = Date.now().toString(36);
  const DEMO_EMAIL = `viktor+signalwise${STAMP}@lastest.cloud`;
  const DEMO_PASSWORD = `•••`;

  const BUSINESS_INTERACTIONS = [
    {
      slug: 'run-audit',
      input: {
        labels: ['url', 'website', 'domain', 'page'],
        placeholders: ['url', 'website', 'domain', 'enter', 'https://', 'example.com'],
      },

+183 more lines — claim the test to get the full code.

Checks run

Run

✓

Visual

1.71%

Text

—

DOM

✓

Network

—

Console

6 new

A11y

—

Perf

102 over

URL

✓

Variables

—

1,348

Diff px

24s

Duration

—

Accessible

A

Fast

Web Vitals · 100

Notes from the demo run

AI-generated

SignalWise positions sharply for agencies ("When AI picks someone else, know the reason and the next fix") with a clean two-column signup form and Google OAuth as an alternative. Pricing page reuses the same minimalist palette. However, the email+password signup endpoint returns auth_failed for every submission tested — a launch-blocking issue you almost certainly want to know about.

Highlights

Sharp positioning
Hero copy is unusually specific for an agency tool — "know the reason and the next fix" frames the value-prop as an action plan, not a dashboard.
Clean signup UX
Single-column form, inline password rules, Google OAuth as the secondary path. Best-in-class for an indie B2B SaaS.

Friction points

Email+password signup returns auth_failed for every submission
Tested 3x in this session (1x from Lastest EB, 2x from a real Chromium browser) with both @gmail.com and @lastest.cloud addresses. Each submit redirects to /login?error=auth_failed&mode=signup with the generic banner "Authentication failed. Please try again." No 4xx visible in browser console. Likely cause: Supabase Auth hook (aiqtrhtoidvffctkaxal.supabase.co is the configured project) rejecting the call, or a server-side validator (HCaptcha token, allowlist, rate limit) that isn't rendered in the form UI. Anyone hitting the form right now sees "sign-up broken" and bounces.
Generic error copy obscures the cause
"Authentication failed. Please try again." gives the visitor no actionable signal — was it the password rules, a reCAPTCHA timeout, a duplicate email? Even "too many requests, try again in 60s" would convert better than the current text.

Couldn't reach

/dashboard·Could not authenticate — signup endpoint returned auth_failed on all attempts
/audit (authed)·Same — the public /audit page is a marketing variant of the homepage CTA; the real audit runner is behind signup

2 visual changes

Share this run

Earned · Lastest awards

Proof your app is not AI slop

LASTEST

starter

tests

all passing

regressions

0

Badges stay live, ratchet upward, only downgrade on confirmed regression.

57,604 test runs recorded · 1,174 products tested with Lastest

This test was built for www.getsignalwise.com — claim it free

One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.

Claim this test Sign in

Browse more live Lastest demo reports →