Reads the forms on one page and counts what makes them harder to finish: how many fields, how many are required, which fields have no label and which fields about the visitor do not tell the browser what they are. Where a published source states a figure for that kind of form, it compares the form with it and names the source and its date. For founders whose sign-up, contact or checkout form loses people.
How to use it
Enter the address of the page that holds the form. You can leave out https://.
- Type or paste the address of the page with the form and press Run check.
- Read the table of forms to see how many fields each has, how many are required and how many have no label.
- Work through the findings from the top. Each one names the fields it counted and the practice it comes from.
- Make the changes and run the check again to see the counts drop.
How Reavlo tests this
This tool runs on our server, because a browser cannot read another site's page. Nothing about the request is stored or logged: not the address, not the page. The check fetches the one page, with a size cap and a time limit. Addresses that point to private or internal networks are refused before any connection is made.
What is counted. For each form in the HTML: its fields (hidden fields and buttons are not counted), how many are required, how many are of each type, how many have no label, and how many fields about the visitor have no usable autocomplete. A single search box is shown but not judged. A written step count such as Step 1 of 3 is reported when the page states one.
Only cited practices are compared. The practices live in the Reavlo form-practices dataset, and each one carries its source, a word-for-word quote and the date it was read. A practice without a reliable published source is not in the dataset; the tool then shows the count as an observation and makes no numeric comparison. The dataset is reviewed every six months.
Field count. Baymard Institute's 2024 study of checkout flows found an average of 11.3 form fields and says most sites need only 8. These figures describe checkouts, so the tool compares only a form that looks like a checkout (it posts to a checkout or payment address, or asks for card or billing details). A contact or sign-up form is counted, never compared with the checkout figure.
Labels. WCAG 2.2 Success Criterion 3.3.2 requires labels or instructions when content requires user input. A field with no label, aria-label, aria-labelledby or title is a warning.
Autocomplete. WCAG 2.2 Success Criterion 1.3.5 requires the purpose of an input that collects information about the user to be programmatically determinable. A name, email, phone or address field with no autocomplete attribute, or with autocomplete off, is a warning. Fields are recognized by their type, name and id.
Limits. The check reads the raw HTML only. A form that scripts build after the page loads is not in it, and neither is a step that scripts reveal, so the tool may report no form on a page that has one. It does not submit the form, test validation messages or measure completion, and it cannot tell you how many fields your audience will accept.
Questions
Is the address I enter stored?
No. The address goes to our server only to fetch the page, and neither it nor the page is stored or written to a log. Analytics records only that the tool ran, never the address.
Why does the tool say my page has no form?
It reads the HTML the server sends. If your form is created by scripts after the page loads, which many form widgets do, it is not in that HTML. The tool cannot see it, and it says so rather than guess.
How many fields should a form have?
There is no number that fits every form. The only figure the tool uses is Baymard's for checkout flows, which says most sites need only 8 fields. For other forms the tool reports the count and leaves the judgment to you.
Why is a missing autocomplete a warning?
WCAG 2.2 asks that fields collecting information about the user state their purpose in code. It also lets browsers fill the field for the visitor, which removes typing from the form.
Does fixing these findings raise my completion rate?
The tool cannot promise that. The findings point at friction that is documented in the cited sources. Whether removing it helps your visitors is something you can only learn by testing the change.