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
303.4 KB
Conservative composed download weight—the largest HTML, browser assets, and production image added together, not one single measured route. The smaller this number, the faster a page tends to load for a visitor.
Verified August 3, 2026. This is a repository build measurement, not a synthetic claim about every possible route, network, or device. Download the machine-readable evidence. Full build narrative: Building SITEBORNE.
Compressed JavaScript
Interactive browser code across the production build
Conservative payload composition
Largest HTML + browser assets + largest production image, added together—not one single measured route load
Automated accessibility runs
Critical routes, desktop and mobile projects
SEE THE DECISIONS BEHIND THE EVIDENCE
The numbers above come from a documented build.
Review the complete internal build record: the constraints it was built under, the architecture decisions made and why, every accessibility and performance test, the known limitations, and how ownership and exit were designed in from the start.
BUILT WITH
Rich design tooling did not cost the payload measured above.
There is no fixed KB number this site is built to hit—the discipline is the technique, not a round ceiling. Every page is compressed aggressively, code-split so nothing loads until a visitor actually needs it, and built on native CSS instead of a JavaScript animation library whenever the same visual result is achievable without one. The homepage hero's Spotlight effect, the Signal Modules bento grid, the scroll-tracing beam on the Building SITEBORNE record, and that page's gradient-border button are all Aceternity UI-derived patterns, live on this site today—already counted inside the 91.4 KB compressed JavaScript figure measured above, not exempted from it. The first attempt at the beam and the button used Aceternity's original Framer Motion implementations; measured directly, that pulled in roughly 44 KB gzipped the moment either component was used—a real, measured regression against the build's own prior baseline. Rather than ship that regression or quietly drop the components, both were rebuilt on native CSS—@property and a conic-gradient for the button, animation-timeline: view() for the beam—which reproduces the same visual result with no JavaScript framework cost at all. Both degrade gracefully to a static (non-animated) state in browsers without scroll-driven animation support, and both respect prefers-reduced-motion. The full Aceternity UI and Framer Motion toolkit stays available for projects where the scope justifies its cost—see the Design Lab for a live, working sample, measured and disclosed separately from the numbers on this page.
Astro
Static-first rendering with isolated interactive islands
Cloudflare Workers + Pages
Edge runtime, hosting, and client-owned production account
React
Used only inside the specific islands that need client-side interaction
Aceternity UI + Framer Motion
Animated component patterns—used selectively, not applied wholesale
Tailwind CSS
Utility styling, compiled and purged at build time
TypeScript + Zod
Typed content, configuration, and validated form input
Cloudflare D1, KV, R2, Vectorize, Workers AI
Durable data, cache, storage, retrieval, and optional inference
The point is not "no animation." It is that visual polish and a small shipped payload are a build decision enforced by technique—compression, code-splitting, native CSS first—not a tradeoff or an arbitrary limit. Every interactive component is opt-in per page, not loaded by default, and the richer alternative is one click away at /design-lab/ rather than hidden.
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.
16.7 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.
91.4 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.
SITEBORNE VS. THE MEDIAN WEBSITE
Not a category guess—an industry-wide measurement.
Median mobile figures from the HTTP Archive Web Almanac 2025 (crawl: July 2025), covering millions of real, live production websites—not one category label.
Median website — Compressed JavaScript632 KB
SITEBORNE production — Compressed JavaScript91.4 KB
Median website — Compressed CSS77 KB
SITEBORNE production — Compressed CSS16.7 KB
This compares JavaScript and CSS payload specifically, where measurement convention lines up cleanly. Total page weight is not shown here—HTTP Archive's median includes every image and font a page loads, while SITEBORNE's 303.4 KB figure above is a deliberately conservative composition (largest HTML, browser assets, and one production image), not a full-page byte count. Comparing dissimilar totals would not be an honest measurement.
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
PUBLISHED PRICING, VERIFIED AT THE SOURCE
Real numbers from real pricing pages—not category stereotypes.
Unlike the payload comparison above, entry price and contract terms are published by each provider on their own site, so they can be checked directly. Every figure below links to the exact page it was read from and the date it was checked. This says nothing about the quality of any provider's work—only what they publicly charge to start.
SITEBORNE
Entry price: $6,500–$9,500 (Foundation Web System)
Commitment: Fixed-scope project; Care is optional and cancels month to month.
See the full SITEBORNE pricing pageFlow Ninja
Entry price: $30,000 minimum (Webflow Development); $45,000 minimum (flowTransform)
Commitment: Ongoing WebOps retainers from $6,000/month on a 12-month commitment.
Read the published pricing pageSuperside
Entry price: $15,000/month minimum
Commitment: All subscriptions run on an annual commitment.
Read the published pricing pageDesignjoy
Entry price: $4,995/month (discounted from $5,995/month)
Commitment: Month-to-month subscription; one active request delivered at a time, average 48-hour turnaround.
Read the published pricing pageWhat these numbers reveal about actual value
The agency and subscription models above are built around continuous recurring revenue—either through massive upfront minimums with 12-month lock-ins, or perpetual monthly subscriptions with no finish line. SITEBORNE's model is built on client ownership and a defined exit.
- True Value: You pay once for a bounded deliverable. Foundation pricing has a firm ceiling—no scope creep, and no open-ended billing cycles.
- Strong Value: Absolute client ownership. You are never trapped paying a recurring monthly minimum just to keep your site online.
- The Benefit: Complete operational flexibility. Ongoing Care is entirely optional. The system remains yours, performant, and fully functional.
Year 1 Minimum Cost Comparison
Superside$180,000
Flow Ninja$102,000
Designjoy$59,940
SITEBORNE$6,500 – $9,500
Superside and Designjoy figures are twelve months of their published subscription price. Flow Ninja's figure adds its $30,000 Webflow Development minimum to one year of its $6,000/month retainer, since Flow Ninja's model requires both. SITEBORNE's figure is the one-time Foundation project price, with no retainer required to keep the site running.
These four are cited because they are named and quoted specifically in SITEBORNE's own competitive research, not selected to flatter the comparison. Pricing changes; re-check the linked page before relying on any figure here.
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 composed-payload calculation—not a single measured route load. 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