Website Design and Development: Myths, Facts and What Actually Drives Revenue
A performance-first look at how build decisions shape speed, tracking accuracy and conversion - and what to do before your next rebuild

Image via 123RF
In This Article
Build Is a Lifecycle, Not a Project
Design Choices Set Performance Limits
Instrument Before You Design
Why 'Website Design and Development' Means Something Different to a Growth Team
Most search results for this topic are glossaries. This one is not. For a US growth team, design and development is not an aesthetic exercise - it is the physical infrastructure your CAC, MER and attribution accuracy run on. Every hero video, font weight, plugin and data layer decision sets a ceiling on how cheaply you can acquire a customer for the next three years.
Below are seven myths we hear in almost every pre-rebuild conversation, each paired with the fact that should replace it, then what to actually do.
Myth 1: A Website Is a One-Time Project That Ends at Launch
Launch day is the midpoint, not the finish line. Treating a build as a finite deliverable is how companies end up with a site nobody can safely change.
Fact: The Build Is a Lifecycle - Design, Instrument, Test, Iterate
A production site is a loop: ship a variant, measure it in field data, feed the result back into the next iteration. Budget for a maintenance and CRO retainers alongside the build. Indicative US ranges for ongoing maintenance sit around $500-$3,000/month (estimates only), and that line item is what keeps the site from fossilising.
Myth 2: Design Comes First and Development Follows
Beautiful comps handed to a developer is a recipe for rebuilds six months later.
Fact: Design Decisions Set Hard Limits on Speed, Tracking and SEO
An autoplay hero video, six web fonts and four tag managers are design decisions with engineering consequences. Once the visual direction is locked, the performance ceiling is largely locked too. Specify the data layer and performance budget before the first Figma frame.
Myth 3: Page Speed Is Purely a Developer Problem
Designers, merchandisers and marketers all contribute to page weight - developers just inherit the bill.
Fact: Core Web Vitals Are Field Metrics Shaped by Design Choices
Core Web Vitals are measured at the 75th percentile of real users. Lab scores in PageSpeed Insights can look fine while field data tells a different story - and field data is what Google's page experience signals draw from. First Input Delay was retired in March 2024 and replaced by Interaction to Next Paint (INP).
Core Web Vitals Thresholds Every Design Brief Should Carry
LCP, INP and CLS limits at the 75th percentile of real users
| Metric | Good | Design decision that most affects it |
|---|---|---|
| LCP | ≤ 2.5s | Hero image/video weight, font loading |
| INP | ≤ 200ms | Third-party scripts, JS on interactive modules |
| CLS | ≤ 0.1 | Late-loading embeds, ads, banners |
Myth 4: Analytics and Conversion Tracking Are a Post-Launch Add-On
If tracking is specced after build, you spend the first ninety days guessing which campaigns worked.
Fact: Data Layer and Consent Architecture Belong in the Build Spec
Server-side tagging via a GTM server container gives you control over signal and data minimisation that a browser-only container cannot. Pair it with a consent management platform that feeds consent state into the data layer, and with Meta Conversions API / Google Enhanced Conversions for signal recovery. This is designed to support CCPA/CPRA and Global Privacy Control requirements - not a compliance guarantee.
Specify your event taxonomy, consent states and server-side endpoints before design begins. Retrofitting them is the most expensive part of a rebuild.
// Minimal GTM purchase push - put this in the build spec
dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: 'T-1042',
value: 148.00,
currency: 'USD',
items: [{ item_id: 'SKU-22', item_name: 'Trail Shoe', quantity: 1 }]
},
consent: { analytics: 'granted', ads: 'granted' }
});Explore the tracking and build framework in more detail at Prebo Digital's services overview.
Myth 5: The Cheaper DIY Builder Is Always the Cheaper Option
Sticker price is not total cost. A $40/month builder that forces a rebuild at 200 SKUs or blocks your data layer is the expensive path.
Fact: Compare Total Cost of Ownership and Rebuild Risk, Not Sticker Price
Custom marketing builds commonly quote in the $10k-$50k band for mid-market US companies (indicative estimates). DIY tools cost less upfront but cap your tracking control. Column four below is where the real decision lives.
Build Options Compared: DIY, Template + Freelancer, Custom Agency, Headless
| Option | Best for | Performance ceiling | Tracking control | 12-24mo TCO (indicative) | Rebuild risk |
|---|---|---|---|---|---|
| DIY builder | Early-stage, ≤50 SKUs | Low | Low | ~$1k-$4k | High |
| Template + freelancer | Budget-limited growth | Medium | Medium | ~$5k-$15k | Medium |
| Custom agency build | Scaling DTC, B2B | High | High | ~$10k-$50k | Low |
| Headless (Hydrogen) | Performance-critical Shopify | Highest | Highest | ~$25k-$80k+ | Medium |
Myth 6: More Pages Means More Organic Visibility
Thin category pages and duplicate tags do not earn rankings - they dilute crawl budget and internal link equity.
Fact: Architecture, Internal Linking and Migration Hygiene Decide SEO Outcomes
A clean 200-page architecture with deliberate internal linking outranks a 2,000-page sprawl every time. On Shopify, Hydrogen storefronts give you routing and rendering control a Liquid theme cannot; on WordPress, block themes with full-site editing reduce plugin sprawl that otherwise shifts CLS.
The Migration Redirect Map: The Highest-Risk Step in Any Rebuild
Every legacy URL needs a 1:1 destination before DNS flips. A missing redirect map is the most common way a rebuild erases organic revenue in week one.
Myth 7: Accessibility Is Optional Polish
Accessibility is often treated as a separate compliance track, oddly after launch.
Fact: WCAG 2.2, Usability and Conversion Move Together
Contrast, focus states, target sizes and reduced-motion support in WCAG 2.2 make forms clearer for everyone. Better focus states and larger tap targets lift form completion - accessible builds tend to convert better.
Which Build Path Fits Your Business? Three Buyer Profiles
- Early-stage, limited budget: template + freelancer, basic GA4, revisit at scale.
- Scaling DTC Shopify brand: theme optimisation or headless if performance-critical, plus server-side tracking and a CRO retainer.
- B2B SaaS/service with complex funnels: custom build, CRM/HubSpot integration, marketing automation and ETL so form-to-CRM handoff keeps attribution intact.
Pre-Build Checklist: Seven Decisions to Lock Before Design Starts
- Platform and rendering model confirmed
- Event taxonomy and conversion definitions documented
- Consent states and CMP selected
- Server-side container and endpoints scoped
- Performance budget agreed (LCP, INP, CLS)
- Redirect map drafted for every legacy URL
- Post-launch CRO and maintenance owner assigned
See how this applies to your build - talk to the Prebo Digital team.

