The screens
Extra steps.
Ask on the first screen.
You tap through a goal, then a pitch. The email field is still on the third screen.
The short answer
Ask for the email on the first screen. Stumblet flags the walk when two or more screens come before the first field whose label says email, e-mail, or password. One screen before that field is not this finding.
Walk your signup
Why the form shows up late
The first screen asks you to pick a goal. The next one shows a pitch. The email field is on the screen after that. You already decided to try it, and you are still not in the form. One screen of that is not this finding. Two is.
Put the email on the first screen. A goal and a pitch can wait until the account exists. A step counter such as Step 3 of 5 is a different finding. It reads the label. This one counts the screens the walk actually passed.
What Stumblet flags
12 screens before the form
Pick a goal, then See a demo, then a form with Email and Password. The title is 2 screens before the form. The title does not put quotes around the count. The fix is Ask for the email on the first screen. The line is I went through “Pick a goal” and “See a demo” before the form. The rank is 46.
The finding is filed on the form screen. The step index is that screen's index. The names in the line are the screens before it, not the form. Two names are joined with and. Three use a comma, and and before the last. The line quotes at most three, in curly quotes, and then a full stop.
Specific findings sort by rank, highest first. An earlier screen wins a tie. Password rules that live only in the placeholder share rank 46. A show-password miss ranks at 44, so this one sits above it. Unmarked required fields rank at 41 and are a generic form finding, so they sit behind it. That check is on required fields. A button that only says Continue ranks at 35. That check is on button text. The questions below have the rest of the order. The report keeps five fixes.
2One screen is not this
One screen before the email field is not this finding. The form on the first screen is not this finding. The check runs once, on the steps the walk recorded. A page that did not load, a bot check, and a URL that is not a signup often stop on the first screen, and then there is no form and no finding.
The label that ends the count is email, e-mail, or password, in the stored field name. Work email matches. Confirm password matches. Passcode does not. A checkbox that says Email me updates matches, and that can end the count early. A trap field is removed first. The walk stores eight labels, and it records six screens at most.
The title uses the number of screens passed. Four screens before the form, with a name on each, is 4 screens before the form, and the line names the first three. A blank name is dropped. Two names are still required. The questions below have the name, the clip, and the screen the finding is filed on.
3The form screen, and a mock that stays there
The mockup does not move the email onto the first screen. When this finding is the one drawn, the before side is the form screen. The before line is Step, then that step's index plus one, then the quote. For a form at index 2, that is Step 3. The line under the mock is the fix.
The after heading is the form step's headline when there is one. With no headline, it uses the screen name, unless that name is the button or the document title, and then it is Create your account. The button stays as it was, or Create account when the step has none. The after side does not drop the pitch screens, because it draws the form.
A step counter is a different finding, on signup fields. A total from 4 to 12 ranks at 38. A total of 2 or 3 ranks at 34 when the screen has a headline or an email or password field. This one ranks above both. A higher finding can be the one drawn instead. The questions below have the dropped labels, and when there is no mockup.
Questions
Which field ends the count?
The first recorded step whose field labels contain email, e-mail, or password. Capitals do not matter. The labels are taken after a trap field is removed. The words are leave this field blank, leave the field blank, leave field blank, leave blank, do not fill, honeypot, for bots only, and bot-field, read from the type, the label, the name, the placeholder, and the autocomplete. What remains is the first eight fields that are not hidden. A checkbox is included. A radio is included. A hidden input is left out. The stored name is the label, then the placeholder, then the name attribute, and underscores and hyphens become spaces. A trailing colon or asterisk is dropped, and the first character is made a capital. That capital is not applied when the name is empty. An empty name becomes the input type as written, so a password input with nothing else is stored as password and matches, and an email input with nothing else is stored as email and matches. An email input whose only text is the placeholder you@example.com, with no label and no name, is stored as You@example.com, and that does not match. A name of user_email, with no label and no placeholder, is stored as User email and matches. Confirm password matches, because password is in it. Work email matches. Passcode does not match this check. A checkbox whose label says Email me updates matches, and that can end the count on a screen that is not the account form. A ninth field is not stored, so it cannot end the count. The form on the first screen is not this finding. One screen before the form is not this finding. If none of the recorded screens has that label, there is no finding. The walk records six screens at most, so the largest title is 5 screens before the form, when the form is the sixth screen.
Which screens are named?
Each screen before that field. The name is the headline. With no headline, it is the screen name the step stored. A trailing full stop, question mark, or exclamation mark is removed. A name that is still blank is dropped. Two names are required. One named screen is not this finding, even when more screens were passed and their names were blank. The line quotes at most the first three names. The title uses the number of screens passed, which is the form's step index, not the number of names in the line. Four screens before the form, with a name on each, is the title 4 screens before the form, and the line names the first three. The walk's own screen name falls back to This page, so a recorded step still has a name. That stored name is Payment when the screen has a card and no human check, and Email check when it is an email check and no human check. Otherwise it is the heading, clipped at 42 characters. Mixed case stays as written. A shouted heading in capitals is sentence-cased, and a short brand in capitals stays in capitals. A longer heading keeps 41 characters, trimmed, and then an ellipsis. With no heading, it uses the form's title, then a signup button, then the document title when that title is not split by a bar, a middle dot, a bullet, or a dash with a word after it, and then This page. The line prefers the headline as written. It does not use that sentence-cased screen name while a headline is present. Each quoted name is then clipped at 48 characters. A longer name keeps 47 characters, trimmed, and then an ellipsis.
How is the line written?
Two screens, Pick a goal and then See a demo, then the form: the title is 2 screens before the form. The title does not put quotes around the count. The fix is Ask for the email on the first screen. The line is I went through “Pick a goal” and “See a demo” before the form. Three names use a comma, and and before the last: I went through “Pick a goal”, “See a demo”, and “Your plan” before the form. The names are in curly quotes. The line is given a full stop. The fix does not change when the field that ended the count was a password field. The rank is 46. The finding is filed on the form screen, not on the first of those screens. The step index is the form's index. With no screen name on that step, the screen is This page. The walk keeps one of this finding. It is added after the other findings, and it is not added twice. When a model rewrites the walk, it can replace the line and the fix. It leaves the title and the rank.
What about a step counter?
A different finding. This one does not read a step label. The walker reads Step N of M and Step N/M when the current step is at least 1, the total is from 2 to 12, and the current step is not past the total. A total from 4 to 12 ranks at 38. The title is that label, then before the product, as in Step 3 of 5 before the product. The fix is Cut this to one screen, or say what this step is for. A total of 2 or 3 ranks at 34 when that screen has a headline, or an email field, or a password field. A passcode field counts as that password field. The fix is Say what this step is for, or ask for the email on one screen. A counter on the form, and two screens before that form, can both be recorded. This finding ranks above both of those. The rest of the counter is on the signup fields guide.
Where does this finding sit, and what does the mockup change?
The rank is 46. It is a specific finding. Password rules that live only in the placeholder share that rank. Specific findings sort by that number, highest first, and an earlier screen wins a tie. That order picks the stuck point and the finding that is drawn. This finding is recorded on the form screen, and it is added after the findings from that screen. When the rank and the screen are the same, the one already recorded stays ahead in that order. With one persona, the report lists up to five fixes by rank number, highest first, and an earlier screen wins a tie. A tie that is still left is broken by the title. A page that did not load, a bot check, and a URL that is not a signup rank at 90. An extra field ranks at 80 when it is required and at 72 when it is not. A human check on the page ranks at 75. Welcome back on a first visit ranks at 74. A quoted field error ranks at 68. A button that stayed disabled ranks at 66. An email check before the product ranks at 65. A handoff to another account ranks at 64. A screen whose only way in is a provider button ranks at 60. No signup on the screen ranks at 55. A provider button above the email ranks at 52. Password rules that are missing rank at 50. A box that starts ticked ranks at 48. Placeholders as the only labels rank at 47. A button or a field under 16 pixels ranks at 45, and so does a card. A show-password miss ranks at 44. Work email only ranks at 42. A human check holding the button ranks at 40, and so does jargon. A vague heading ranks at 38. A required terms box ranks at 36. A button that only says Continue ranks at 35. A hint that only asks for a work email ranks at 34. Unmarked required fields rank at 41 and are a generic form finding, so they sit behind this one in the walk's order. Labels that are not tied to the fields rank at 28 and are the other generic finding. A missing price ranks at 32 and is a template finding, so it sits behind this one. No person and no company ranks at 24 and is a template finding too. The terms sentence under the button ranks at 8 and sits last. The mockup does not move the email onto the first screen. This finding is not one the after side redraws. When it is the one drawn, the step is the form screen. The before line is Step, then that step's index plus one, then the quote. The after heading is the step's headline. With no headline, it uses the screen name, unless that name is the button or the document title, and then it is Create your account. A screen name that ends in …, with at least 8 characters before the ellipsis, and that starts the document title, counts as the title. The button stays as it was, or Create account when the step has none. The after side keeps up to three field labels. A label that says checkbox or radio is dropped. A label is also dropped when it matches company, organisation or organization, team size, company size, employees, role, job title, phone, use case, industry, workspace, headcount, website, username, user name, display name, confirm password, repeat password, re-enter password, reenter password, password again, or again password. If nothing is left, the after side shows Email and Password. The line under the mock is the fix. A finding whose screen, or what the step did, says hands off to is not the one drawn. There is no mockup when the page did not load, when a bot check stopped the walk, when the URL is not a signup, when a human check holds the button, or when the signup is clean. This finding is enough to keep the signup from being called clean. A walk whose only other note is the terms sentence keeps both. If this finding is absent and that sentence is the only note, the walk is called clean and the sentence is dropped.
Which fields to cut, including the step counter, is on signup fields. Asking for the password twice is on confirm password. What the first screen should say is on signup page copy. A button that stays disabled is on signup button. Showing the rules before anyone types is on password rules. Asking for a work email is on work email. A provider button above the email is on social login. A password with no show control is on show password. A required terms tick box is on terms box. A card before the product is on credit card. Welcome back on a first visit is on welcome back. A button that only says Continue is on button text. A field that doesn't say it's required is on required fields. A button or a field under 16 pixels is on tap targets. Running it yourself, and keeping the top five, is the new-user signup test. The short list is the onboarding checklist. The AI onboarding audit is the walk, and the signup prompt is the job it runs.
The walk is free. It starts on the home page.
Walk your signup