Scanverra
Designer vs. platform audit

Webflow Website Audit

Some of what shows up in a Webflow audit you can fix in the Designer this afternoon. Some of it you can't touch no matter how long you spend in there. Scanverra tells you which is which.

What's yours to fix, and what isn't

The split that makes a Webflow audit different from an ordinary one.

Fixable in the Designer

Image compression and format

Webflow doesn't compress on upload. A heavy hero or gallery image stays exactly as heavy as the file you exported.

Alt text on CMS image fields

Left blank by default across every collection item - one of the most common findings on Webflow CMS-driven sites.

Per-page meta tags and Open Graph settings

Title, description, and social preview data live in each page's SEO settings panel, page by page.

Custom code and font loading

Self-hosting fonts as project assets instead of the default Google Fonts CDN request, and trimming interactions that add JavaScript weight, both go through the custom code embed.

Locked by the platform

Response headers

HSTS, X-Frame-Options, and similar headers are Webflow's to set - there's no headers() config file or server you can reach.

CDN and caching behavior

Beyond what Webflow's own hosting settings expose, cache-control and edge behavior aren't yours to tune.

Rendering strategy

There's no server-vs-static choice to make. Every page renders the way Webflow's platform renders it, for every visitor.

What we check for Webflow

Each finding is tagged Designer or Platform, so you know where to go fix it.

Image weight & compressionDesigner
Missing alt text on CMS itemsDesigner
Per-page meta tags & Open GraphDesigner
Interaction & animation JS weightDesigner
Response-level security headersPlatform
CDN caching behaviorPlatform

How it works

Three steps from URL to a Designer-fixable breakdown.

Paste your Webflow site URL

Any published Webflow site, on a webflow.io subdomain or a connected custom domain, works the same way.

We confirm the Designer's fingerprints

The generator meta tag, data-wf-page and data-wf-site attributes, and a window.Webflow object in the page all confirm the platform before scoring.

Get a Designer-fixable vs. platform breakdown

Every finding is labeled so you know immediately whether it's a five-minute Designer fix or a platform limit to work around.

FAQ

Frequently asked questions

Can I fix everything Scanverra finds without leaving Webflow?

Not everything. Most performance and SEO items - image compression, alt text, meta tags, font loading, interactions - are fixable in the Designer. Response headers and CDN/caching behavior are controlled by Webflow's platform and aren't exposed to site owners.

Does Scanverra know my site is built on Webflow?

Yes - the generator meta tag, data-wf-page and data-wf-site attributes on the page, and a window.Webflow object in the rendered HTML all identify the platform.

Can I add custom code to fix a flagged issue?

Webflow's custom code embeds, at the page or site level, cover a lot of ground - meta tags, structured data, small script tweaks. They can't change response headers or your CDN's caching behavior, though.

Will missing alt text on CMS items actually move my score?

Yes - accessibility checks flag missing alt text image by image, and Webflow's CMS collection fields don't populate it for you automatically.

Does self-hosting fonts help a Webflow site's speed?

It can - it avoids the render-blocking external request that Webflow's default Google Fonts CDN link adds to every page load.

Free - no sign-up required

See what's fixable in your Designer today

Image weight, alt text, meta tags, and font loading - scored, and separated from what only Webflow controls.

Run free audit