A site on 1C-Bitrix takes 4–8 seconds to load? LCP >4s, CLS >0.2, INP >200ms — a typical picture for stores on this CMS. Google factors Core Web Vitals into rankings, and users leave after a delay of more than 3 seconds. We conduct an end-to-end audit and optimization: from diagnostics to final testing with a guaranteed PageSpeed Insights pass. Our experience covers 5+ years and over 50 projects. In one project, we worked with an auto parts store on Bitrix: LCP was 6.2s, CLS 0.3, INP 250ms. After optimization — LCP 1.8s, CLS 0.05, INP 120ms. Conversion rose by 22%, bounce rate dropped by 25%. Investment in optimization pays for itself in 3–6 months through higher conversion and lower abandonment. Typical optimization cost for an e-commerce Bitrix site ranges from $1,500 to $3,000, providing an estimated monthly revenue increase of $2,000–$5,000 for stores with 10,000+ visitors.
Why Core Web Vitals are critical for a Bitrix site
Google uses these metrics to evaluate user experience. Poor Core Web Vitals reduce conversion by 20–40% and hurt rankings. For Bitrix sites, the main sources of issues:
- LCP: slow TTFB + large images in the main banner
- CLS: images without width/height, fonts without font-display, dynamic blocks (cart, banners)
- INP: heavy JavaScript, blocking scripts in the head, excessive event listeners
In practice, every second store on Bitrix fails Google's assessment. We solve these problems with a guaranteed result.
According to Google's recommendations, LCP should be under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds.
What the Core Web Vitals optimization includes
Diagnostics
We use Chrome DevTools Lighthouse for synthetic testing and PageSpeed Insights for real user data (CrUX). We evaluate TTFB, JS/CSS size, images, and cache settings. The result is a detailed priority report.
LCP: critical rendering path
The LCP element in a Bitrix store is usually the main banner or first image. The problem: the image is loaded via JavaScript after rendering. The solution — preload with fetchpriority="high":
<link rel="preload" as="image" href="/upload/banners/main.webp"
imagesizes="100vw" fetchpriority="high">
Add this in <head> via AddHeadString() of the component. Sliders are the main enemy: Swiper.js adds 100–300 KB of JS. Optimization: first slide in static HTML, JS initialization via defer or requestIdleCallback.
CLS: layout shifts
Non-zero CLS in Bitrix is caused by:
-
Images without dimensions. Standard components often output
<img> without width/height. We add sizes:
// In template.php of catalog.element component
$width = $arItem['PREVIEW_PICTURE']['WIDTH'] ?? 300;
$height = $arItem['PREVIEW_PICTURE']['HEIGHT'] ?? 300;
echo '<img src="' . $arItem['PREVIEW_PICTURE']['SRC'] . '" '
. 'width="' . $width . '" height="' . $height . '" '
. 'loading="lazy" decoding="async" alt="' . htmlspecialchars($arItem['NAME']) . '">';
JavaScript: render blocking and INP
In Bitrix, the <head> often includes 10–20 JS files via CJSCore::Init(). We switch to defer:
<script src="/bitrix/js/main/core.js" defer></script>
In the module settings “Performance”, we enable moving scripts to the end of the page. We diagnose INP via DevTools Performance, analyzing long tasks and event handler latency.
Images: WebP and lazy loading
We configure the resize_image module in /bitrix/.settings.php:
'resize_image' => [
'value' => [
'webp' => true,
'webp_quality' => 80,
],
],
Lazy loading for offscreen images: loading="lazy" decoding="async". LCP image — no lazy. WebP compresses images 30-50% better than JPEG without quality loss, speeding up load time.
CSS: critical path
We inline critical CSS in <style> in <head>, load the rest asynchronously with <link rel="preload" as="style" onload="this.rel='stylesheet'">. Use PurgeCSS to remove unused styles.
How to optimize LCP step by step
- Identify the LCP element via Chrome DevTools.
- Ensure this image is preloaded with
fetchpriority="high".
- Optimize the image: WebP at quality 80%, size not exceeding 200 KB.
- Configure TTFB caching: use Bitrix tagged caching.
- Move blocking scripts to footer or use
defer.
How tagged caching affects TTFB
Tagged caching in Bitrix allows clearing cache only for changed blocks instead of a full reset. This reduces TTFB to 50ms vs 200-400ms without cache. Configuration is done via /bitrix/.settings.php and components with caching support.
Typical optimization mistakes
- Neglecting TTFB: without server and cache tuning, LCP won't improve.
- Using
loading="lazy" on the LCP image — this worsens LCP.
- Not reserving space for dynamic blocks (cart, sliders) — CLS remains high.
Example cost savings calculation
With an average order of 2,000 rubles and a conversion of 3%, a 25% bounce reduction yields an additional 30 orders per month from 10,000 visitors. That's an extra 60,000 rubles in monthly revenue.
What you get after optimization
| Metric |
Before |
After |
Improvement |
| LCP |
4–8 s |
<2.5 s |
2–3x |
| CLS |
0.2–0.5 |
<0.1 |
2–5x |
| INP |
>200 ms |
<200 ms |
>30% |
Comparison of image optimization methods
| Method |
Compression |
Quality |
Support |
| WebP |
30-50% |
high |
all modern browsers |
| JPEG |
10-20% |
medium |
universal |
| PNG |
lossless |
high |
universal |
Why choose us
- 5+ years of experience with Bitrix
- 50+ completed projects
- Certified specialists
- Guaranteed PageSpeed Insights pass
Order an audit and get a detailed report with recommendations. Contact us for a consultation — we will assess your site and propose a Core Web Vitals optimization plan.
More about metrics: official page. Additional information on cache configuration: 1C-Bitrix documentation.
80% of Bitrix sites slow down due to one table
b_iblock_element_property is an EAV structure where each row stores one value of one property of one element. A catalog of 50,000 products with 30 properties yields 1.5 million rows. The smart filter performs a JOIN of this table with b_iblock_element on five properties, and MySQL performs a full table scan for 3–5 seconds. Our experience shows that without intervention in this table, site acceleration is impossible. We take on projects where load time has dropped to 8–10 seconds and bring TTFB back to <200 ms within 1–2 weeks. Site speed optimization begins with an audit of slow queries and ends with a comprehensive turnkey infrastructure overhaul.
Contact us for an audit — we will identify bottlenecks within 2 hours and propose a concrete plan.
How to achieve TTFB below 200 ms?
Server optimization is the first step. Nginx configuration goes beyond simple gzip. Specifically:
-
gzip_comp_level 4-5 — higher is pointless, CPU consumes more than it saves bandwidth.
-
brotli on with brotli_static on for precompressed files.
- HTTP/2 with
http2_max_concurrent_streams 128.
-
fastcgi_cache for PHP responses — caching at Nginx level, bypassing PHP-FPM entirely.
-
worker_processes auto, worker_connections according to the number of simultaneous connections.
PHP-FPM tuning: choose between pm = dynamic and pm = static. Static mode works best for dedicated servers with predictable load because it avoids forking overhead. Dynamic saves RAM under low traffic. Calculate pm.max_children as (available RAM - RAM for MySQL/Redis) / average process consumption. For OPcache set memory_consumption=256, max_accelerated_files=20000, and validate_timestamps=0 in production (restart PHP-FPM on deploy).
MySQL/MariaDB: the main bottleneck is almost always the database. Enable slow_query_log with a threshold of 0.5 sec and analyze every query via EXPLAIN. Set innodb_buffer_pool_size to 70–80% of available RAM on a dedicated server. Create composite indexes for faceted search: (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) on b_iblock_element_property. Run OPTIMIZE TABLE b_iblock_element_property after mass operations.
How to configure three-level caching?
Managed component cache. Set TTL individually for each component. Catalog — 3600 sec, news feed — 300 sec, banners — 86400. The same TTL everywhere guarantees either outdated data or useless cache.
Composite cache. The bitrix:composite technology lets Nginx serve ready HTML from a file; PHP is not executed. Dynamic zones (cart, authorization) are loaded via AJAX request through CBitrixComponent::setFrameMode(true). TTFB drops below 50 ms. However, not all components are compatible; $APPLICATION->ShowPanel() and direct output via echo break the composite. We check every page through the panel 'Performance → Composite Site'. According to Bitrix official documentation on composite cache, this is the most effective caching method for high‑load projects.
Comparison: composite cache is 10–20 times faster than managed cache in time to first byte.
Memcached / Redis. Transfer cache from the file system: sessions go to Redis (session.save_handler = redis) — 10–50 times faster than files, plus cluster support. Component cache goes to Memcached via .settings.php: 'cache' => ['type' => 'memcache']. Also enable ORM query cache so identical GetList() calls don't hit MySQL on every request.
What is the fastest way to optimize Bitrix database?
Default MySQL settings are insufficient. Indexes — composite for faceted search, covering for frequent queries. MySQL responds from the index without accessing the data. Partial indexes (MariaDB) for filtering by ACTIVE = 'Y'. Audit unused indexes — each slows down INSERT/UPDATE.
Partitioning. For tables with millions of rows: b_stat_session, b_search_content_stem, and highload-blocks with history. Partition by date — a query for 'orders in a month' does not scan three years of data. Partitioning also solves the problem of concurrent queries during exchange with 1С via CommerceML.
Real case: a catalog of 200,000 products, 50 properties. Filtering by 10 properties took 12 seconds. After creating composite indexes on (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) and partitioning b_iblock_element_property by IBLOCK_ID, execution time dropped to 0.3 seconds. MySQL load decreased by 40 times.
Cleanup. Over a year or two, any database accumulates: outdated search index, expired records in b_cache_tag, history in b_iblock_element_prop_s*, logs in b_event_log taking gigabytes. We set up regular cleanup via agents.
Frontend and CDN
Images account for 60–80% of page weight. Convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + conversion. Use srcset + sizes — never load a 3000px image into a 400px block. Add loading="lazy" for everything below the fold. AVIF offers another 20–30% savings vs WebP.
CSS/JS optimization: use the built-in Bitrix module to merge and minify via 'Settings → CSS/JS Optimization'. Apply PurgeCSS / UnCSS — in a typical Bitrix project, 60–70% of CSS is unused. Use defer / async for non‑critical JS and inline critical CSS in <head> for instant FCP.
Fonts: add <link rel="preload" as="font" crossorigin> for the main font. Set font-display: swap — text visible immediately. Subset via pyftsubset — keep only Cyrillic + Latin, file size reduces by 3–5 times.
CDN: Cloudflare, BunnyCDN, AWS CloudFront, or Russian providers (Selectel CDN, VK Cloud CDN). Serve static assets (CSS, JS, images, fonts) via CDN with Cache-Control: public, max-age=31536000, immutable for files with a hash. Use on‑the‑fly image optimization (imgproxy, Cloudflare Polish) without load on origin.
Why is load testing necessary?
Not synthetic benchmarks, but real scenarios: k6 / wrk to simulate routes — catalog → filtering → product card → cart → checkout. Measure RPS, response time (p50, p95, p99), error rate. Use Xdebug (callgrind) or Blackfire for PHP profiling to find bottlenecks. The test result gives an objective picture of where it actually slows down, not where it 'seems'. After optimization, run again to record improvements.
Results
| Metric |
Before |
After |
| TTFB |
800–2000 ms |
50–200 ms |
| Full load |
4–8 sec |
1.5–2.5 sec |
| PageSpeed (mobile) |
30–50 |
80–95 |
| Concurrent users |
50–100 |
500–2000+ |
What is included in the work?
-
Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
-
Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
-
Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
-
Database work — index creation, partitioning, cleanup, EAV table reorganization.
-
Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
-
CDN — connection, caching rule setup.
-
Load testing — real user scenarios, metric report.
-
Documentation — description of all changes, recommendations for further maintenance.
-
Guarantee — support for 1 month after delivery, ensuring all optimizations are stable.
Monitoring
Without monitoring, everything degrades in six months. A new module, uncleared logs, a template change — and speed returns to original. Use web-vitals API for Real User Monitoring from actual visitors. Set up synthetic monitoring with Pingdom or UptimeRobot for regular checks from different locations. Configure alerts — TTFB > 500 ms or LCP > 3 sec triggers notification.
Timelines and cost
| Type of work |
Timeline |
| Basic optimization (cache, images, minification) |
2–3 days |
| Database optimization (indexes, slow queries, configuration) |
3–5 days |
| Server infrastructure (Nginx, PHP-FPM, Redis) |
2–3 days |
| Comprehensive (server + database + frontend + CDN) |
1–3 weeks |
| Load testing and profiling |
2–3 days |
| Cluster architecture (balancing, replication) |
1–2 weeks |
Cost is calculated individually after the audit. Get a consultation for your project — we will evaluate the current state and propose an acceleration plan with specific timelines and budget. We are a team with 12+ years of experience in Bitrix, having completed over 300 site speed optimization projects. Contact us to start the performance audit today.
