Find what is holding your site back

Open the web audit, paste an address, and read the result. That is the whole workflow.

What it checks

Findings are ranked by impact, so the first item on the list is the one worth fixing first. That ordering is the useful part: a list of forty faults sorted alphabetically helps nobody.

What each limit is

Registering is free and needs no card. The reason to do it is the associated-files group: robots.txt and sitemap.xml are two of the most common reasons a site is invisible to search engines, and a guest audit does not look at them.

Reading a result without over-reacting

Fix the SEO and accessibility findings first. They are specific, they are actionable, and each one is a real defect.

Treat the performance score as a direction, not a grade. Scores move between runs on the same unchanged page: network conditions vary. A score that moves from 71 to 78 tells you nothing. A score that moves from 40 to 75 after you compressed your images tells you plenty.

Read what a finding actually says. "Missing alt text" names the images. "Low contrast" names the colors. The finding is a repair instruction, not a rating.

Auditing your own InboundSavvy site

Audit the built site, not the editor. The audit fetches a real address the way a visitor does, so it can only see what a build has published.

The natural loop is: fix, build a preview, audit the preview, then publish.

Most findings on an InboundSavvy site fall into three buckets, all of them yours to fix rather than the platform's: images larger than they need to be (images), missing alt text or heading structure faults (site settings and search), and layouts that break on a narrow screen (mobile layout).

Certificates, hosting, and the sitemap are handled by the platform and should come back clean. If one of those fails on a published InboundSavvy site, that is worth reporting rather than fixing.

Scheduled monitoring

Pro and Enterprise re-run the audit on a schedule and tell you when something changes. That catches the class of problem nobody catches by hand: a certificate approaching expiry, a page that quietly started returning an error, an image someone replaced with a 6 megabyte original.

Next