Every component ships every component's JS.
The builder loads a runtime that supports every possible widget so you can drag any of them in. Your simple landing page ends up shipping 800kb of JavaScript.
What breaks · Mobile Lighthouse 40s
Featured · Journal
How to rank in AI answer engines.
Generative Engine Optimisation — what it is, why it matters now, and eight things to check before next Monday.
Read the field guide →By topic
The JournalField notes from the team at WebHeroCustomer storiesReal businesses, real Avago sitesGEO & SEO field guidesGet found on Google and AI enginesKnowledge baseEvery Avago how-to, indexable and linkableHelp centreAI chat, 24/7IntegrationsEvery app that connects to AvagoFor agencies & enterpriseWhite-label and APIStatusLive platform health
Need a hand with something specific? Try Avago Extra →Esc to close
The differentiator
Designed by humans. Populated by AI.
The Hybrid Design Engine — every site starts on a template a human built, then the AI writes your copy into it. Designed sites that don't look designed by a machine.
Read the deep-dive →The platform · seven feature pages
Hybrid Design EngineHuman-designed templates, populated by AI from your sourcesLogo generationVector logos via Recraft — scale to a favicon or a van, no quality lossThe visual editorClick-to-edit, section library, separate mobile editor — you stay in controlSEO & GEOSchema, GBP sync, llms.txt — found by Google, cited by ChatGPTSecuritySSL, backups, GDPR, WCAG — on every plan, not behind an upsellPerformanceGlobal CDN, image pipeline, JS budget, Core Web Vitals tunedAnalyticsFirst-party, cookie-free, no consent banner, real numbersCustom domainsConnect, transfer, register — free SSL, always portableIntegrationsMailchimp, HubSpot, Slack, Notion and 40+ more — connected from your dashboardAll features →The full capability map on a single page
Popular integrations
Compare
New here? See how it works in 90 seconds →Esc to close
Feature · Performance & Core Web Vitals
Fast on the first visit. Fast on the worst phone.
Performance isn't a vanity score — it's Google's ranking signal and the difference between a bounce and a booking. Avago ships every site behind a global CDN with image optimisation, lazy loading, JS-free defaults and HTTP/3 enabled.
94Median Lighthouse score, mobile
<1.8sLargest Contentful Paint, p75
300+CDN PoPs worldwide
The shape of the problem
Why most builder sites score 40 on mobile.
Three structural reasons modern website-builder sites end up slow — and the one we chose not to make.
Upload a 4MB photo. Serve a 4MB photo.
No automatic image optimisation, no responsive variants, no AVIF/WebP. The hero image alone is bigger than the rest of the page. LCP is whatever your DSLR exports at.
What breaks · LCP > 3 seconds
Compile only what you use. Optimise everything you upload.
Per-page JS is tree-shaken to only the components on that page. Every image is auto-converted to AVIF + WebP at the right size for each breakpoint. Lazy-loaded below the fold.
What you get · Mobile Lighthouse 90+
What's included
Speed, by structural choice. Not by 'optimisation tips'.
Performance can't be bolted on. These four choices are baked into how Avago ships every site.
300+ points of presence.
Your site is served from the nearest of 300+ edge locations. HTTP/3, Brotli compression, edge caching, image transformations at the edge. No origin trips for static assets.
- HTTP/3 + 0-RTT
- Brotli compression
- Edge image transforms
Right format, right size, right second.
Upload once. Avago generates AVIF, WebP and JPEG variants at five breakpoints, picks the right one per visitor, and lazy-loads anything below the fold.
- AVIF + WebP + JPEG
- Five responsive breakpoints
- Lazy-load below fold
Per-page, tree-shaken.
Pages only download the JS for the components on that page — not the whole builder runtime. Average page payload is under 80kb of JS, often zero on content pages.
- Per-page tree-shaking
- <80kb avg JS payload
- Zero-JS on content pages
LCP, INP, CLS — measured & tuned.
Every published site is monitored against Google's CrUX data. We surface real-user metrics in the dashboard and flag pages slipping out of the 'good' band before Google does.
- Real-user CrUX monitoring
- Per-page LCP / INP / CLS
- Regression alerts in dashboard
How it works
What makes an Avago page feel quick.
Three things happen between you publishing and the page reaching a visitor — and they're the difference between a 40 score and a 94.
Build-time optimisation.
When you publish, Avago compiles your page: tree-shakes JS, inlines critical CSS, generates image variants, builds a per-page asset bundle. Done before the first visitor arrives.
Edge delivery.
The compiled page goes to all 300+ CDN PoPs simultaneously. Static assets cache at the edge with a 1-year TTL. Dynamic content (forms, bookings) hits the origin only when it has to.
Run-time observation.
Real-user metrics come back from every visit. Lighthouse audits run weekly. Regressions show up as alerts in your dashboard before Google penalises you for them.
Live performance · per-page
Real-user numbers, not synthetic.
Lighthouse synthetic scores plus Google's Chrome User Experience Report (CrUX) data for every page on your site. You see what your actual visitors see — not what a clean test environment sees.
LCP 1.4sINP 102msCLS 0.02Lighthouse 94Origin 38ms
FAQ · 4 short answers
The questions we get about performance. Most weeks.
Will my Avago site pass Core Web Vitals?
Yes — most Avago sites sit comfortably in Google's 'good' band for LCP, INP and CLS on both mobile and desktop. The dashboard surfaces any page slipping out of band, with the specific image / script / layout shift to fix.
Do I have to do anything to enable the CDN?
No. Every Avago site is behind our CDN automatically from the moment you publish, on every plan. No setup, no config, no extra fee.
What about my images — do I need to compress them first?
No. Upload at any size. We re-encode to AVIF + WebP + JPEG at five responsive breakpoints, strip EXIF, and serve the right one to each visitor. The original is kept for re-encoding if formats change.
Can I add custom scripts (analytics, chat widgets) without tanking my score?
Yes — they're loaded async and below-the-fold by default. The dashboard warns you if a script you add pushes you out of the 'good' Core Web Vitals band, so you can decide whether it's worth it.
The rest of the platform. One click away.
All features →Have an idea? Just have a go.
Your website is waiting to be built. No credit card. No commitment. Free to build — only pay when you're ready to go live.