Krevia is a Shopify theme built around one rule enforced in CI: total JS stays under 60KB gzipped, or the build fails. No framework runtime, no bloat — just fast, native storefronts. Native filtering, quick-add, variant swatches, sticky add-to-cart, subscriptions and popups — zero required apps. WCAG AA accessible by default. A real live-preview theme editor. Built solo because I was tired of installing five apps just for a fast product page. Feedback welcome.
Hey Product Hunt 👋
I'm Amit — I build Shopify themes and storefronts for a living, and Krevia came out of a specific frustration: every "fast" theme I evaluated for clients turned out fast only until someone installed a review app, an upsell app, and a popup app, and then it wasn't anymore.
So with Krevia I set one non-negotiable rule and enforced it in CI: 60KB of JavaScript, total, gzipped, theme-wide. If a PR pushes past that, it doesn't merge. No framework runtime sitting underneath. Sections that don't need JS don't load any.
A few things I'm proud of that don't usually make it into theme marketing pages:
- WCAG AA is the default, not an upsell tier
- Native filtering, quick-add, subscriptions, and popups — so you're not stacking apps just to hit table-stakes features
- The theme editor is a real live
preview, not a settings panel that makes you guess.
Live demo here: krevia.kreatrs.com
Genuine question for this crowd: when you're evaluating a theme or template for a client project, is a hard performance budget (like this 60KB cap) something you'd actually value, or does it feel like premature optimization compared to just picking based on design first? I have a real answer I lean toward, but curious what actually drives decisions for people building storefronts day to day.
Happy to answer anything about the build, the CI setup, or the accessibility work — I'll be in the comments all day.