Boost Your 1C-Bitrix Site: Slash TTFB from 1.2s to 200ms

We see a typical picture after several years of Bitrix project development: TTFB 800-1200 ms, Largest Contentful Paint over 4 seconds, PageSpeed Insights in the red zone. The causes are usually not in the hosting — they are inside the application itself: uncached components, unoptimized infoblock queries, 200+ HTTP requests per page due to unbundled JS/CSS, and uncompressed images uploaded at original resolution. According to Google, increasing LCP from 2.5 to 5 seconds raises bounce probability by 90%. For a Bitrix store with a monthly turnover of 1 million rubles, each second of delay can cost 200-300 thousand rubles in lost sales. Practice shows that comprehensive 1C-Bitrix optimization is not a single action but a sequential elimination of several problem classes. Order matters: server side first, then frontend. With a proper approach, we can reduce TTFB by 3-5 times in the first week, and PageSpeed moves from red to green. Recently on a project with 15,000 SKUs, we lowered TTFB from 1.4s to 180ms in one week — details in the case study. Our optimization services are priced on request and pay off quickly through increased conversion. Our company has been working with Bitrix for over 10 years and has completed more than 200 optimization projects. Assess your project — contact us.

Price of a Slow Site: Impact on Conversion and SEO

Loading speed directly affects conversion and search rankings. 53% of users leave if a page takes longer than 3 seconds. For Bitrix online stores, each second of catalog loading can cost thousands of rubles. After optimization, our clients record a 20-30% increase in mobile traffic conversion.

Server Side: Cache, Queries, Agents

Component caching is the first step in any audit. In Bitrix, each component manages its cache via the CACHE_TYPE and CACHE_TIME parameters. Often developers set CACHE_TYPE = N (no cache) during debugging and forget to revert. One such component on the homepage multiplies TTFB.

Check via \Bitrix\Main\Diag\Debug::dumpToFile() or the bitrix.performance module to list uncached components and their execution time. The standard tool is the performance panel (/bitrix/admin/perfmon_panel.php).

Database query optimization. Infoblocks in Bitrix, when used carelessly, generate queries like SELECT * on b_iblock_element, b_iblock_element_property, b_iblock_section without field limits. Switching to D7 API (Iblock\ElementTable) with explicit select reduces data transfer and MySQL load. A separate issue is the N+1 problem: a component in a loop makes a query for each element. Detected via $DB->ShowSqlStat() or MySQL slow query log with long_query_time = 0.1. Query caching improves TTFB 2-4 times faster than uncontrolled execution.

Agents and background tasks. Bitrix agents by default run in the context of a web request if cron mode is not configured. This adds 50-300 ms to random requests. Moving agents to cron (/bitrix/modules/main/tools/cron_events.php) eliminates this delay entirely.

How Composite Mode Accelerates a Site and When It Doesn't Help

Composite mode caches HTML pages in the file system and serves them without executing PHP, replacing dynamic blocks (cart, authorization) via AJAX. For content and catalog pages, it's the most powerful tool — TTFB drops to 20-50 ms. Composite speeds up server response up to 10 times compared to regular PHP.

But composite doesn't work automatically. It requires marking dynamic zones with the bitrix:nocache tag, converting authorization and cart to AJAX components, and setting exclusions for personalized pages. Incorrect configuration leads to cached data for logged-in users — a critical error on projects with personal accounts.

Frontend: HTTP Requests and Resource Weight

After server optimization, we examine the client side via Chrome DevTools → Network. Typical problems of Bitrix projects:

• Unbundled CSS/JS: each module loads its own files separately. On a heavy project, this means 30-80 files. Bitrix can combine them via compression settings (Settings → Performance → Compression), but requires correct path configuration and HTTP/2.
• Unoptimized images: original files from the media library are served without conversion to WebP, without srcset for retina. The resize_image module can crop images on the fly, but without caching the cropped versions, it creates load.
• Missing lazy load: images below the fold load with the initial screen. In Bitrix, this is solved via the loading="lazy" attribute in component templates or JavaScript IntersectionObserver.

Case Study: From TTFB 1.4s to 180ms in One Week

One of our clients — a corporate online store with 15,000 SKUs on Bitrix "Business", VPS 4 CPU / 8 GB RAM. Before optimization: PageSpeed Mobile — 22/100, TTFB — 1.4s, LCP — 5.8s. Customer complaints about slow catalog loading.

Audit findings:

• 4 components with CACHE_TYPE = N on the homepage (left by developer during debugging)
• N+1 in the "similar products" component — 48 queries per product page
• Agents in web mode, 11 agents running synchronously
• 94 HTTP requests on the homepage (CSS/JS not bundled)
• Images in JPEG without WebP, average size 340 KB

Work sequence:

1. Fix component caching → TTFB: 1.4s → 380ms
2. Optimize N+1, migrate to D7 API → queries per product page: 48 → 6
3. Move agents to cron → eliminated 80-200ms latency
4. Bundle CSS/JS → HTTP requests: 94 → 18
5. WebP via CFile::ResizeImageGet() + lazy load → average page weight: 2.8 MB → 680 KB
6. Configure composite mode for catalog and homepage

Result: PageSpeed Mobile 71/100, TTFB 180ms, LCP 2.1s. Mobile traffic conversion increased — users stopped leaving slow catalog pages. Composite sped up TTFB by 10x compared to initial state.

DIY Diagnostics Tools

Before contacting specialists, you can check:

• /bitrix/admin/perfmon_panel.php — built-in Bitrix performance panel
• MySQL slow query log (long_query_time = 1) — slow queries
• Chrome DevTools → Lighthouse — frontend overview
• For Bitrix: php bitrix/modules/main/tools/cron_events.php to check agents

For more on web application performance, see Wikipedia.

Comparison of Optimization Methods

What's Included

• Full performance audit with report on each bottleneck
• Fix component caching and configure tagged cache
• Optimize database queries (migrate to D7, eliminate N+1)
• Set up composite mode with dynamic zone markup
• Frontend optimization: CSS/JS bundling, WebP, lazy load, minification
• Move agents to cron and monitor their execution
• Load testing and metric recording
• Maintenance documentation for achieved speed

Stages and Timeframes

Timeframes are approximate and depend on custom code volume. We recommend regular audits. We guarantee an objective assessment and transparent work plan. Get a consultation — tell us about your project, and we will choose the optimal solution. Contact us to order an audit. Закажите услуги по оптимизации Bitrix: ускорение сайта, настройка кеширования, композитного режима, оптимизация изображений и HTTP-запросов.

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

What is included in the work?

1. Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
2. Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
3. Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
4. Database work — index creation, partitioning, cleanup, EAV table reorganization.
5. Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
6. CDN — connection, caching rule setup.
7. Load testing — real user scenarios, metric report.
8. Documentation — description of all changes, recommendations for further maintenance.
9. 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

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.