Webflow
Webflow exports clean, server-rendered HTML and gives you real control over heading levels and custom code, so most findings here are genuinely quick.
What tends to go wrong here
Of the hosted builders, Webflow gives the most markup control. You choose heading tags directly, you can add JSON-LD per page or per template, and the output is static HTML served from a CDN. Response time findings are rare.
Where the findings land
- Easy To Fix
- Everything in Page Structure and Entity Clarity, including per-template structured data through the custom code panel.
- Harder To Fix
- Nothing significant, though CMS collection templates need their structured data written once and bound to fields.
- Usually Structural
- Almost nothing, unless the site is a single-page design where all the content lives behind interactions.
Worth knowing
Webflow sites that score poorly usually have not used the custom code panel at all. Adding a publisher node and a page-type declaration to the site-wide head is a fifteen-minute job that lifts every page.
Others in Site Builders
- Squarespace Content renders server-side, which is the important part, but head-level control is limited to what the injection panel allows.
- Wix Modern Wix sites render server-side, but older ones and heavily app-driven pages can still return very little in the raw HTML.
Find out which of these apply to you
Everything above is what usually happens on this platform. The inspection tells you what is actually happening on your page.