Compressed CSS
Complete browser-delivered stylesheet set
VERIFIABLE PERFORMANCE + ARCHITECTURE
Speed is a build artifact, not a sales adjective.
Instead of promising a site is “fast,” SITEBORNE publishes the actual numbers: how much a visitor's browser has to download, how it was tested, who owns the production system, and where its limits are. Anyone can inspect the same evidence used to decide whether a release is ready to ship.
Production evidence current
278 KB
Total download weight of a representative production page—the smaller this number, the faster the page loads for a visitor.
Verified August 2, 2026. This is a repository build measurement, not a synthetic claim about every possible route, network, or device.
Compressed JavaScript
Interactive browser code across the production build
Representative page
Largest HTML + browser assets + largest production image
Automated accessibility runs
Critical routes, desktop and mobile projects
THE FAIR COMPARISON
Compare evidence, not stereotypes.
There is no defensible universal payload for “traditional agencies,” Webflow, Framer, WordPress, Next.js, or any other category. SITEBORNE therefore publishes its own measurements and gives buyers the exact questions needed to inspect another production build.
No competitor range below is invented from a category label. A specific deployed URL should be measured before making a numeric comparison.
“Outsourced build” means a traditional agency or freelance build. “Visual SaaS” means a drag-and-drop website builder such as Wix, Squarespace, Webflow, or a similar hosted platform.
CSS payload
Ask for the compressed production artifact. “Optimized” is not a measurement.
Generated styles vary by project and platform configuration; inspect the deployed build.
15.6 KB compressed across the current production build.
JavaScript payload
Ask which interactions require hydration and whether the primary journey works without it.
Visual effects, tracking, and runtime features can add browser work; test the actual URL.
87.7 KB compressed. Astro renders server-first and hydrates only explicit interaction boundaries.
Data layer
Confirm who owns the database, how requests are limited, and what happens when a provider fails.
Convenient managed data can reduce setup time but may limit portability and operational visibility.
Client-owned Cloudflare D1 for durable records and atomic limits; KV for expiring cache, deduplication, and rate state.
Accessibility
Request route-level automated results plus keyboard and focus evidence—not an accessibility badge.
Accessible output still depends on content structure, component choices, and manual configuration.
28/28 automated Axe runs passed, with keyboard navigation, focus restoration, reduced motion, and 400% reflow checks.
Ownership
Confirm who controls the domain, production account, source, data, billing, recovery, and transfer path.
Platform ownership can simplify operation while increasing migration dependence.
Client-owned Cloudflare production, source access, documented recovery, visible provider costs, and an explicit exit path.
THE PERFORMANCE CHALLENGE
Ask every vendor for the same four artifacts.
- A compressed production payload report
- Route-level accessibility results
- A client-ownership and transfer map
- A documented failure and fallback path
THE ANTI-AGENCY MODEL
Trust is designed into the delivery model.
Radical clarity is not a tone-of-voice exercise. It changes account ownership, claims, secrets, monitoring, pricing, failure states, and what happens when the relationship ends.
Architecture scenarios, not fictional case studies
Prototype situations are labeled as modeled scenarios. No invented customer, quote, conversion lift, or revenue outcome is presented as history.
Client-owned infrastructure
Domains, production accounts, billing, data, source, and recovery access stay with the client. SITEBORNE does not create a hosting-margin dependency.
Inactive means inactive
The system status and disclosures identify unbound providers and fallbacks instead of implying that a logo in an architecture diagram equals a live integration.
Secrets stay server-side
Automated scanning checks the browser bundle for credential patterns. Cloudflare and R2 credentials are not shipped to visitors.
Performance is a release gate
The production build is measured against committed payload budgets. A material regression fails verification before publication.
Claims carry evidence and limits
Published capability, allowance, accessibility, and operational statements are tied to code, completed checks, or named provider documentation.
MEASUREMENT BOUNDARY
What these numbers do—and do not—prove.
The report measures compressed browser assets generated by the repository build and a conservative representative page calculation. It does not guarantee identical transfer size on every route, network latency, device execution time, search ranking, conversion rate, or permanent provider pricing.
Core Web Vitals still require field observation after meaningful traffic exists. SITEBORNE Care can track that operating evidence without making the website dependent on Care.
See optional Care protection