MEDIA
Screenshot of ur-met.ru
ur-met.ru
Metal structuresLCP from 9 s to 1.9 s — Bitrix untouched
- 1.9 s
- LCP
- < 100 ms
- Search
- 6 wks
- Launch
Read case study →
Comparison
Headless or Bitrix: which is right for your store?
We break it down across concrete criteria: speed, cost, risk, timelines. We will figure out your case. No pressure to switch.
- LCP 1.7–2.2 s on headless
- Bitrix backend stays
- Free consultation
- 10 comparison criteria
Web storefront
iOS + Android
PWA
Frontbox · core
Next.js + Elasticsearch
SSR · ISR · edge cache · facets · synonyms · auth
~120msTTFB
1.9sLCP
88mssearch
1C‑Bitrix
1C
CRM / ERP
When to choose headless
Four situations where switching your frontend delivers results
Catalog is sluggish
Standard Bitrix LCP — 6–14 s. On headless (Next.js + edge cache) — 1.7–2.2 s.
5× faster
Search does not work
Built-in Bitrix search — from 2 s. Elasticsearch with facets — under 100 ms at 100k+ SKU.
< 100 ms at 100k SKU
SEO in the red
Core Web Vitals red? Headless moves them to green via SSR and edge cache.
Core Web Vitals into the green
Frontend is outdated
Need a new design without rewriting the backend? Frontbox changes only the frontend — Bitrix and 1C stay.
no backend replacement
Comparison
Headless (Next.js) vs 1C-Bitrix monolith
Relevant for stores with a catalog of 500+ SKU and traffic of 1,000+ unique visitors per day.
Criterion
Headless (Next.js)
1C-Bitrix monolith
- Page speed (LCP)1.7–2.2 s on 4G6–14 s without CDN
- TTFB90–150 ms on edge cache800–3,000 ms on typical hosting
- Catalog searchElasticsearch < 100 ms, facetsBuilt-in search, from 2 s
- Core Web VitalsGreen (SSR + edge cache)Often yellow/red
- Backend replacementNot required — connect via APIAny redesign touches the backend
- Launch timeline2–6 weeks4–12 months
- Entry costfrom ~$380/mofrom $15K–60K up-front
- 1C integrationStays intact, no changesRewritten or reconfigured
- Rollback if issues ariseInstant — switch traffic backComplex, touches the backend
- Best for500+ SKU catalog, Bitrix on backend, speed mattersNew site from scratch, small business without Bitrix
Benchmarks
Real numbers from production sites
- LCP (headless)1.7–2.2 sLargest Contentful Paint on 4G. Bitrix monolith without CDN: 6–14 s.
- TTFB (headless)90–150 msTime to first byte on Vercel/Cloudflare edge cache.
- Search (Elasticsearch)< 100 msFaceted query over a 100k+ SKU catalog.
- Launch2–6 weeksFrom first call to traffic switchover.
How it works
Three steps: from question to concrete plan
We do not push headless. We analyse your site and give you a straight answer — worth switching or not.
- 011–2 days
Current site audit
We measure LCP, TTFB, Core Web Vitals. We review catalog architecture, search, and 1C integrations.
- 022–3 days
Analysis against your KPIs
We calculate what a migration would deliver in your specific conditions: traffic, catalog, budget, timelines.
- 03on the call
Recommendation and roadmap
We are direct: worth switching or not. If yes — we give you the plan. If no — we explain why.
Live projects
Clients who switched to headless and stayed
Two Bitrix-backed online stores. Headless frontend added. Backend untouched.
Two paths to headless
Frontbox on top of Bitrix, or a full migration to Next.js
Headless is not a single scenario. The right choice depends on budget, timeline and how much control over the stack you need.
Path 1 · Frontbox
Headless frontend on top of your Bitrix
The fastest and safest option. Backend and 1C stay untouched. Frontbox connects via API — the frontend changes, business logic does not.
from ~$380/mo
Subscription from ~$380/mo or license ~$1,000/mo × 18 mo
- Term
- Monthly or 18 mo
- Hosted on
- Our servers or your perimeter
- Ownership
- Bitrix stays yours, frontend stays yours
- Live in 2–6 weeks
- Bitrix, 1C and integrations untouched
- LCP 1.7–2.2 s, search < 100 ms from day one
- Gradual traffic switch with zero downtime
- Instant rollback if anything goes wrong
Path 2 · Full migration
New Next.js site from scratch
When the Bitrix backend is leaving entirely, or you are building a new project. Full architectural freedom — but longer and more expensive.
On request
Cost depends on scope and requirements
- Term
- Fixed-price or T&M
- Hosted on
- Your infrastructure
- Ownership
- Full stack handed over to you
- Full control over frontend and backend
- No constraints from Bitrix architecture
- Stack chosen to fit your business needs
- Timeline: typically 3–6 months for mid-market e-commerce
- Best for: new builds, leaving Bitrix, complex business logic
Frontbox vs full migration: key parameters
| Parameter | Frontbox (on Bitrix) | Full migration |
|---|---|---|
| Launch timeline | 2–6 weeks | 3–6 months |
| Backend replacement | Not required | Yes — full overhaul |
| Cost | from ~$380/mo | On request |
| Risk | Instant rollback | Higher — full stack replacement |
| Best for | Have Bitrix, need speed now | New project or leaving Bitrix |
We will help you pick the right path in a free 30-minute consultation.
Honest about limitations
When headless is overkill — and we will tell you so
Headless solves specific problems. If those problems do not exist, it is unnecessary expense. Four situations where we will say "not worth it".
Catalog under 500 SKUs
With a small assortment, Bitrix monolith speed is sufficient. The investment will not pay off.
No 1C-Bitrix on the backend
If there is no Bitrix backend — it is simpler to build on Next.js directly, without Frontbox as a middleware layer.
Budget under ~$380/mo
Headless requires resources to maintain. Below this threshold, look at other ways to speed things up.
Planning a full platform replacement
Replacing the entire platform? Frontbox as an intermediate step is redundant. We design the new stack directly.
FAQ
Frequently asked questions about choosing an architecture
What is the fundamental difference between headless and Bitrix monolith?
In a monolithic Bitrix setup, the frontend and backend are in one system — Bitrix renders the templates itself. In a headless architecture, the frontend is separate (Next.js) and pulls data from Bitrix via API. The backend does not know what the site looks like. This delivers speed (SSR + edge cache), design flexibility and independence from CMS updates.
Do we need to migrate data when switching to headless?
No. With the Frontbox approach, Bitrix remains the source of truth. The frontend reads from Bitrix via API in real time. Product data, orders, and customer records stay exactly where they are.
Is headless only for large stores?
It makes practical sense starting from a catalog of 500+ SKU or traffic of 1,000+ unique visitors per day. At lower volumes the speed difference exists, but the cost of maintaining a headless stack outweighs the gain. If your case does not fit — we will say so honestly.
How does headless affect our 1C integration?
It does not. Frontbox operates on top of Bitrix — the 1C integration stays untouched. Orders, stock levels, and prices synchronise through the same Bitrix that was working before.
What is better value: Frontbox or a full Next.js migration?
It depends on the objective. Frontbox is faster (2–6 weeks), cheaper to start (from ~$380/mo), and rollback is instant. A full migration makes sense when Bitrix architecture is blocking business logic, or you are building from scratch. We will work through your specific case on the consultation call.
How long does the Frontbox migration take?
2 to 6 weeks: scoping and theming (2–3 days), integration and indexing (1 week), testing and traffic switch (2–7 days). In the first week we give you a clear plan with timelines scoped to your catalog.
What happens to SEO during the switch?
SEO migrates correctly: we preserve URL structure, meta tags, redirects, sitemap and robots.txt. Core Web Vitals typically improve immediately thanks to SSR and edge caching. Full index transition takes 2–4 weeks.
How do we choose between headless and other ways to speed up Bitrix?
Three paths: Bitrix cache tuning (free, yields 20–30% improvement), CDN on top of Bitrix (cheaper, but does not fix TTFB), headless frontend (5× LCP difference, resolves it completely). We run an audit and tell you which path will deliver results in your case.
Not sure which to choose? Let us work it out together.
Free 30-minute consultation: we analyse your site and tell you straight, when headless is worth it, and when it is not.
Tell us about your project
Our offices
- Russia
Saint Petersburg, Rizhskaya st. 5, bldg. 1, office 402
+7 (967) 555-90-32 - Kazakhstan
Almaty
+7 (707) 340-29-12