Optimizing 1C-Bitrix Page Rendering: Diagnosis & Solutions

We've encountered cases where PageSpeed Insights scores 38 with an LCP of 4.2 seconds. TTFB is 1.8 s, and the full content is already in the HTML. The issue isn't the network or client-side JS—the page is slow to generate on the server. Bitrix's diagnostic tools exist but are rarely used correctly. TrueTech has 10+ years of Bitrix experience and has completed 50+ optimization projects. Our experience shows that in 80% of cases, the bottleneck is suboptimal caching or N+1 queries in templates. Catalog pages with hundreds of products are especially vulnerable—SQL queries can exceed 400. Without a systematic approach, fixing one bottleneck may have no effect if caching isn't enabled at all levels. Optimizing 1C-Bitrix page rendering requires a comprehensive audit and sequential actions. One client saved $500/month in server costs after optimization.

Why Is 1C-Bitrix Page Rendering Slow?

Main causes:

• Components working with inconsistent caching mode (CACHE_TYPE=N).
• Loops in templates generating N+1 SQL queries.
• Tagged caching disabled.
• Composite mode not configured.
• Bitrix agents not optimized.

How to Diagnose Slow Bitrix Page Rendering?

A four-step diagnostic algorithm:

1. Enable the debug panel: constants SHOW_PAGE_EXEC_TIME and SHOW_SQL_STAT in dbconn.php.
2. Analyze SQL query count and execution time—normal is up to 100 queries in 0.5 s.
3. Identify components without cache or with CACHE_TYPE=N.
4. Check for N+1 queries in templates (e.g., GetByID calls inside loops).

Diagnosis via standard Bitrix tools

Enable the debug panel:

$_GET["show_page_exec_time"] or constant:
define('SHOW_PAGE_EXEC_TIME', true);
define('SHOW_SQL_STAT', true);

The panel in the page footer shows:

• total execution time
• SQL query count and total time
• memory consumption

Typical problematic page: 400+ SQL queries, 1.5–2.5 s on SQL vs 0.3 s on PHP. Components run with inconsistent caching modes. 1C-Bitrix documentation recommends tagged caching to speed up pages.

What are N+1 queries and how to eliminate them?

The most common cause of 400+ queries is a loop over results with an inner query. This is known as the N+1 query problem.

// Bad: query per item
foreach ($arResult['ITEMS'] as &$item) {
    $item['SECTION'] = \CIBlockSection::GetByID($item['IBLOCK_SECTION_ID'])->GetNext();
}

Fix with an aggregated query before the loop:

$sectionIds = array_unique(array_column($arResult['ITEMS'], 'IBLOCK_SECTION_ID'));
$sections = [];
$res = \CIBlockSection::GetList([], ['ID' => $sectionIds], false, ['ID', 'NAME', 'CODE']);
while ($s = $res->GetNext()) {
    $sections[$s['ID']] = $s;
}
foreach ($arResult['ITEMS'] as &$item) {
    $item['SECTION'] = $sections[$item['IBLOCK_SECTION_ID']] ?? null;
}

Which profiling tools to use?

Bitrix lacks a built-in component-level profiler. The simplest way is to install the Bitrix Performance Monitor module from Marketplace. Alternatively, use xhprof/Tideways with a custom wrapper. For a quick estimate, you can add a handler in init.php that outputs the 10 slowest components, but this requires caution. For advanced profiling, consider using APCu or Redis for caching to improve Bitrix SQL optimization.

How to configure composite mode?

Composite mode is a built-in Bitrix mechanism that caches entire pages and replaces dynamic blocks (cart, auth) via AJAX. It gives TTFB of 50–100 ms for authorized users. However, composite requires template adaptation—it cannot be enabled with a button without component adjustments. We recommend it for projects with high speed requirements.

Composite setup step-by-step:

1. Enable composite in the admin panel: "Settings" → "Product Settings" → "Composite Site".
2. Ensure all dynamic blocks (cart, login form) are moved to deferred functions or AJAX widgets.
3. Configure exceptions for pages that should not be cached (e.g., checkout page).
4. Test with composite enabled for administrators.

Optimizing Bitrix LCP acceleration involves focusing on server-side rendering. Bitrix agents can also cause delays if not configured properly.

Caching type comparison

Reasons for slow component performance

Component with no cache or with NONE cache

$APPLICATION->IncludeComponent('bitrix:catalog', '.default', [
    'CACHE_TYPE' => 'N', // <- performance killer
]);

Change to:

'CACHE_TYPE' => 'A',  // auto according to site settings
'CACHE_TIME' => 3600, // seconds

For user-dependent components (cart, personal area), component-level caching doesn't work—use an AJAX approach: serve the template from cache, load personal data separately.

Disabled caching in composite component

A composite component (e.g., bitrix:catalog) manages caching of its children. If the section settings have "Do not cache", caching is disabled for the entire tree, including product listing sections. Check in site settings: Settings → Product Settings → Caching. Tagged caching (Bitrix Cache Engine) is 3 times faster than standard file caching—use it.

Template optimization

Minification of PHP templates. Bitrix assembles pages from dozens of includes. Each include is a filesystem call. On HDD servers, this takes 5–15 ms per file. Solution: OPcache with opcache.validate_timestamps=0 in production (manual cache invalidation after deployment).

Move heavy blocks to AJAX. Widgets like "similar products", "recently viewed", "popular in category" are candidates for AJAX. The main page renders quickly, widgets load in parallel.

Example result

An online store of building materials with 180,000 SKUs. Before optimization: TTFB 2.1 s, 380 SQL per category page. After: disabled CACHE_TYPE=N in three components, eliminated two N+1 queries, enabled OPcache with validate_timestamps=0. Result: TTFB 420 ms, 38 SQL queries, LCP 1.9 s. Server load reduction allowed significant savings on VPS rental ($500/month).

Optimization stages

Deliverables include: documentation of changes, access to profiling tools, developer training, and 30-day performance warranty.

Request a performance audit of your site—we find bottlenecks in one day. Or get a consultation on rendering optimization. Contact us for diagnosis.

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.