Website Speed Optimization on 1C-Bitrix: Reducing TTFB to 200 ms

An online store on Bitrix loaded the catalog page in 5 seconds; Google PageSpeed showed TTFB of 1.2 seconds. The client was losing 30% of conversions. After comprehensive optimization, TTFB dropped to 180 ms — conversion increased by 15%. Our team has 8 years of experience with Bitrix and has completed over 120 speed optimization projects. Certified specialists guarantee the result.

TTFB is the time from sending an HTTP request to receiving the first byte of the response. It covers pure server time: DNS, TCP connection, SSL handshake plus page generation time. Google PageSpeed considers a good TTFB under 200 ms. A standard Bitrix site without optimization typically has TTFB of 800 ms to 3 seconds.

Why TTFB Matters for Ranking?

Google incorporates TTFB into Core Web Vitals. According to Wikipedia, TTFB directly influences Largest Contentful Paint. For an online store, each extra millisecond means lost customers. We observed on projects where TTFB dropped from 800 to 200 ms, organic traffic increased by 20-25% over three months. Average ROI for TTFB optimization is 2-3 months due to conversion growth.

What Makes Up TTFB in Bitrix

Typical breakdown on a heavy site:

On most projects, 60–80% of TTFB comes from SQL queries. Start there.

OPcache: Basic PHP Optimization

PHP without OPcache compiles every file on every request. A full Bitrix load includes 200–500 PHP files. OPcache caches compiled bytecode:

[opcache]
opcache.enable = 1
opcache.memory_consumption = 256
opcache.interned_strings_buffer = 16
opcache.max_accelerated_files = 20000
opcache.validate_timestamps = 0   ; in production — do not check file changes
opcache.revalidate_freq = 0
opcache.fast_shutdown = 1
opcache.enable_cli = 0

validate_timestamps = 0 is critical for speed. OPcache then does not see file changes without a reset. After deployment, clear the cache: opcache_reset() or using CacheTool. Without this setting, OPcache calls stat() for every file on every request — hundreds of system calls. max_accelerated_files = 20000 — a typical Bitrix site with standard modules has 5000–15000 PHP files. If the limit is lower, some files may not be cached. Verify via opcache_get_status()['opcache_statistics']['num_cached_scripts'].

Page and Component Caching

The most effective way to reduce TTFB is to avoid generating the page at all and serve cached HTML. Bitrix supports caching at several levels.

Component caching. The $cache_time parameter in .parameters.php. Standard component bitrix:catalog.section caches for one hour. With proper setup, a repeat request requires 5–20 SQL queries instead of 100–300.

Managed cache / composite. Composite Site technology splits the page into cacheable and dynamic parts. The cacheable part (main column, menu) is served immediately; the dynamic part (basket, notification counter) is loaded via AJAX. Properly configured, TTFB for the main HTML drops to 50–100 ms. Enable it at: Settings → Performance → Composite Site. Components are marked as dynamic via CBitrixComponent::setDynamicMode() or parameter DYNAMIC = Y.

HTML cache via nginx. The fastest option — nginx serves static HTML without running PHP. Implemented via nginx FastCGI cache or Varnish in front of Bitrix. Requires correct invalidation when content updates.

How to Quickly Reduce TTFB Without Risk?

If you need to urgently improve Core Web Vitals, start with three steps:

1. Enable OPcache with the settings above. TTFB reduction: 100–300 ms.
2. Enable composite cache (Composite Site) — TTFB reduction: 300–800 ms.
3. Optimize heavy SQL queries via slow query log. TTFB reduction: 200–1500 ms.

These steps require no changes to business logic and can be done in 1–2 days. We test each stage on a staging environment.

How to Measure TTFB Yourself?

For external measurement, use curl: curl -o /dev/null -s -w "Time to first byte: %{time_starttransfer}s\n" <your-site-url>. Take 3–5 measurements; the first may be with a cold cache. For internal profiling, enable Bitrix's performance panel (/bitrix/admin/perfmon_panel.php). It shows total execution time, SQL query time, component time, and number of file operations.

Database: Connection and Queries

Connection establishment time to MySQL is 1–5 ms for local connections. If the database is on a separate server, it's 5–20 ms for TCP connection. Persistent connections (MYSQL_PCONNECT) reuse connections across requests within a PHP-FPM worker.

In /bitrix/php_interface/dbconn.php, enable:

$DBPersistent = true;

Persistent connections reduce overhead but increase open connections on the MySQL server. max_connections in my.cnf should exceed the number of PHP-FPM workers multiplied by the number of virtual hosts.

Optimizing Prologue and init.php

Every request executes /bitrix/php_interface/init.php. If it includes heavy classes, SQL queries, or third-party libraries, that adds to every request. Check for includes of files needed only in specific controllers, initialization of third-party SDKs (1C integration, payment systems) on every request, or SQL queries in OnPageStart event handlers. Use lazy-loading via Loader::includeModule() — include modules only where needed.

Economic Effect of Reducing TTFB

Reducing TTFB by 600 ms helped one client increase revenue by 15% due to conversion growth and improved behavioral factors. Average ROI for TTFB optimization is 2-3 months. Another project with a catalog of 50,000 products reduced TTFB from 1.2 s to 180 ms, resulting in a 12% conversion increase. Order a speed audit for your project — we will assess current performance and propose a work plan. Contact us for a consultation to get started.

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.