Audit methodology
How Roast My Web reviews a page
Every audit combines rendered page views, whatever technical signals are available, and an AI review. The output is a point-in-time critique of one public URL, not a full-site certification.
Last reviewed
The five-step process
From a submitted URL to a report you can edit. Most audits finish in about 2 minutes.
Step 01
Capture the page
The system loads the submitted public URL and takes full-page desktop and mobile screenshots once the page has had time to render.
Step 02
Prepare the evidence
It splits the desktop view into readable sections, prepares the full desktop and mobile views, and requests on-page SEO, link, performance, and search context.
Step 03
Review the page
The AI receives the images, the page type you selected, and any description you supplied, then reviews each section and the page as a whole.
Step 04
Prioritize the findings
Each finding gets a label for importance and for how hard it is to fix. Category scores move down when the review flags warnings or important issues.
Step 05
Publish an editable report
The report collects category summaries, screenshots, recommended actions, and whatever SEO evidence arrived. You can edit it before sharing a web or PDF version.
What the visual review covers
Six categories, each with the questions the AI is asked to answer.
- Design and aestheticsVisual hierarchy, consistency, legibility, imagery, and brand fit.
- User experienceNavigation, comprehension, interaction friction, forms, and page flow.
- Originality and creativityDistinctive choices, generic patterns, and whether the page is memorable for useful reasons.
- Content and copyMessage clarity, structure, specificity, evidence, and readability.
- ConversionOffer clarity, calls to action, proof, objections, risk, and decision friction.
- MobileMobile layout, readability, tap targets, content order, and likely device-specific friction.
SEO and performance evidence
Technical evidence is added when the data source responds, and left out honestly when it does not.
What the report can include
Page metadata, headings, indexability and canonical signals, content checks, internal and external links, performance fields, backlink context, domain context, and recent search movement.
What happens when a source fails
A failed optional SEO request does not invent a zero. The visual audit finishes without it, and the report omits data that did not arrive.
How category scores change
The AI gives each visual category an initial score from 0 to 100. The application then applies the same rule to every category.
- Points removed for a suggestion
- 0
- Points for each warning
- −2
- Points for each important issue
- −5
A score cannot fall below 0. Treat it as a prioritization aid, not a percentile, a usability-test result, or proof that a page will rank or convert. The evidence and the recommendation behind a finding matter more than the number above them.
Limits you should account for
What this method cannot tell you, stated before you rely on it.
One URL, not a domain
The audit covers the single public page you submit. It does not crawl every page on the domain.
The capture can be blocked
Login walls, bot protection, consent screens, personalization, and delayed content all change what the screenshots see.
Screenshots have a ceiling
An image cannot reveal every interaction, analytics pattern, customer objection, or business constraint behind a page.
The AI can misread a page
It can suggest a change that conflicts with your brand, legal, accessibility, or technical requirements. Read the reasoning before acting.
Accessibility notes are not compliance
Automated findings do not establish WCAG or legal compliance. Use manual and assistive-technology testing for that.
Third-party data can be missing
Search and performance data can be incomplete, delayed, or unavailable for a given URL.
How to use the report
A report is a structured second opinion. It is worth what you do with it.
Check it against what you know
Test each finding against your analytics, user research, technical constraints, and the goal of the page.
Cut and rewrite
Delete the weak findings, rewrite the vague ones, and assign an owner to what is left.
Rerun after a real change
Run the same URL again when the page has materially changed. Keep the original report as an audit trail.
Read About Roast My Web for who maintains the product and what it does not do, or check the privacy policy before you submit a URL.
Audit one public page
Point Roast My Web at a page and read the evidence behind every finding. Most audits finish in about 2 minutes, and you decide which findings are worth keeping.