The core reason
Hand-coded websites outrank page-builder sites for the same reason that a chef-prepared meal beats microwaved food: the constraints of the system that produced them.
Page builders (Webflow, WordPress + Elementor, Squarespace, Wix) ship a generic CSS and JavaScript bundle on every page. The bundle has to handle every possible thing the builder allows — every layout option, every animation, every component variant — even if your specific page only uses 5% of it. The result is page weight that's 3–10× larger than equivalent hand-coded work.
Google measures this. Page weight directly affects LCP, INP, and TBT (Total Blocking Time) — three of the metrics in Google's Core Web Vitals ranking signal. Smaller pages rank higher.
The numbers
Real-world page weight on the homepage of a typical small-business site:
- Wix: 1.2–2.5 MB
- Squarespace: 800 KB–1.8 MB
- WordPress + Elementor: 800 KB–2 MB
- WordPress + custom theme: 300–600 KB
- Webflow (default): 200–500 KB
- Webflow (heavily optimized): 150–300 KB
- Hand-coded modern stack: 80–250 KB
LCP (Largest Contentful Paint) on a typical 4G mobile connection:
- Wix: 4–7 seconds
- Squarespace: 3–5 seconds
- WordPress + Elementor: 3.5–6 seconds
- Webflow: 2–3.5 seconds
- Hand-coded: 1–2.5 seconds
Google's "good" LCP threshold is 2.5s. Most builder-platform sites land yellow or red without aggressive manual optimization. Hand-coded sites consistently land green.
Why this matters for ranking
Google has confirmed Core Web Vitals as a ranking signal since 2021, with weight increasing over time. The signal isn't huge for a single page — moving a query from #15 to #8 — but it compounds across an entire site. A site with green Core Web Vitals across all pages outranks an otherwise-equivalent site with yellow scores.
For small-business local search ("Red Deer web design," "Calgary auto detailer," "Edmonton accountant") the ranking difference between green and yellow is often the difference between page 1 and page 2 of Google.
Beyond Core Web Vitals
Hand-coded sites win on three other SEO surfaces:
1. Schema markup freedom. Page builders constrain what JSON-LD you can ship. Hand-coded sites can declare any Schema.org type — Service, ProfessionalService, FAQPage, HowTo, Article, BreadcrumbList, Person, Organization — without plugin gymnastics. More structured data → more rich-result eligibility → higher click-through rate.
2. Internal linking control. Page builders typically generate URLs based on their internal structure (collection pages, dynamic content). Hand-coded sites have full URL control, which lets you build clean keyword-targeted slugs (/red-deer-web-design vs /locations/r-2024-rd).
3. LLM citation surface. A hand-coded site can ship llms.txt at the root, custom AI-bot allow rules in robots.txt, and densely structured FAQ + comparison content that LLMs preferentially extract. Page builders limit what you can put at the site root.
What page builders are actually good for
Hand-coded isn't always the right answer. Three cases where a page builder wins:
- You need to launch in a weekend. Builders win on time-to-first-page.
- Your team needs to publish constantly. A CMS-equipped builder beats hand-coded for daily content updates if you don't want a developer in the loop.
- The site genuinely doesn't matter for revenue. If web traffic is incidental to your business, builder economics make sense.
For everyone else — anyone where the website's ranking and conversion materially affect revenue — hand-coded is the right call.
What we measure on every project
Every site we ship at Designer Digital targets:
- LCP < 2.0s on mid-tier mobile (faster than Google's "good" threshold)
- INP < 100ms (half Google's threshold)
- CLS < 0.05 (half Google's threshold)
- Lighthouse 100/100 on SEO and Best Practices
- Lighthouse ≥95 on Performance
- Total page weight < 250 KB on the landing route
We profile on real devices, not just on Lighthouse desktop. Failing any of these is a deal-breaker we don't ship.
What to do if you're on a page builder
Three options:
- Optimize aggressively in place. Strip unused features, lazy-load everything, defer JavaScript. Get Webflow under 300 KB, WordPress under 500 KB. Possible but takes work.
- Migrate to hand-coded. What we do. The migration plan preserves SEO equity (URL redirects, content transfer, backlink preservation). Typical timeline: 8–12 weeks.
- Accept the ceiling. Some businesses don't need top-tier ranking. If your traffic is fine and your business is fine, you don't need to optimize.
For businesses where ranking growth is the goal, option 2 is the answer.