← Our stack

SvelteKit for when performance is the feature.

Compiled components, zero virtual DOM overhead, and a framework that stays out of the way. We use SvelteKit for animation-heavy and performance-critical projects.

svelte.dev ↗
How we use SvelteKit

The site you're on right now runs SvelteKit. We chose it for ComCreate because the compiled output is small, the reactivity model is intuitive, and it pairs beautifully with GSAP and Three.js for the kind of animation work we do on brand-forward projects. We use SvelteKit for sites where every kilobyte matters.where scroll-driven animations need to run at 60fps on mobile and the bundle can't carry the weight of a runtime framework. Svelte 5's runes give us fine-grained reactivity without the boilerplate. We deploy on Vercel with the SvelteKit adapter for edge-optimized static generation.

When the site is the product, we reach for Svelte.
Why SvelteKit

SvelteKit compiles away the framework. There's no virtual DOM diffing at runtime, which means less JavaScript shipped and faster time-to-interactive. For animation-heavy sites where we're layering GSAP ScrollTrigger, smooth scrolling with Lenis, and WebGL effects, that performance headroom matters. The developer experience is also exceptional. Less boilerplate, more building. We reach for SvelteKit when the project is brand-driven and the site itself is the product.

Where we use it

Agency & Brand Sites

High-fidelity marketing sites with scroll-driven animations, GSAP transitions, and cinematic page experiences.

E-Commerce Storefronts

Headless Shopify storefronts built on SvelteKit for minimal bundle size and fast product page loads.

Performance-Critical Applications

Projects where Time to Interactive and Largest Contentful Paint are business metrics, not just Lighthouse scores.

Get started

Let's talk about
your next build.