Bitrix Site Speed: CSS/JS Compression Setup

Optimizing Load: CSS and JS Compression on 1C-Bitrix

Your site loads in 5 seconds, and GTmetrix shows CSS and JS account for 80% of the volume. Typical for an average Bitrix project: source files weigh 500 KB–2 MB, and without compression each megabyte is transferred as-is. Configuring HTTP compression (Gzip or Brotli) reduces the amount of transferred data by 3–7 times for text resources—this is one of the fastest ways to speed up loading without changing code. We configure such solutions on dozens of projects, from simple corporate sites to large catalogs.

Built-in Bitrix Compression Tools

Bitrix includes its own mechanism for minification and merging of CSS/JS, available under Settings → Performance → Compression. It works at the PHP level: collects files included via CMain::AddCSSLink() and CMain::AddHeadScript(), minifies them, and saves them to /bitrix/cache/css/ and /bitrix/cache/js/. The resulting files get a hash in the filename—browsers cache them aggressively.

Important: Bitrix minification only works with files included through the Bitrix API. CSS and JS added directly in the template via <link> and <script> are not processed. On legacy projects, often half the files are included "bypassing" the API. We convert such inclusions to standard methods—this is a mandatory step in our audit.

Why Minification Alone Isn’t Enough for Real Acceleration

Minification reduces file size on disk, but during network transfer, data still goes "as-is." Without HTTP-level compression (gzip/Brotli), you lose 70–80% of potential gain. For example, a minified jQuery UI file might be 150 KB, but with gzip only 40 KB. The difference is noticeable on every request.

How to Set Up gzip on nginx for Bitrix?

The nginx configuration requires just a few directives:

gzip on;
gzip_types text/css application/javascript application/json text/javascript;
gzip_min_length 1024;
gzip_comp_level 5;
gzip_vary on;

gzip_comp_level 5 balances compression ratio and CPU load. Levels 6–9 give minimal gain at significantly higher load. gzip_vary on adds the Vary: Accept-Encoding header, needed for correct caching proxy and CDN operation. Brotli compresses even better—gain up to 20% over gzip. Configuration is similar, but requires the ngx_brotli module.

What Brotli Gives Compared to gzip?

Brotli is 1.2–1.3 times more efficient than gzip in compression ratio. It is preferable for modern browsers but requires an nginx module. Configuration:

brotli on;
brotli_types text/css application/javascript application/json text/javascript;
brotli_comp_level 6;

It's best to keep gzip as a fallback for older clients. Both methods can be combined: gzip_static on for pre-compressed files.

What to Check During Setup

A common mistake: double compression—gzip is enabled in nginx, but PHP-FPM or Bitrix itself also compresses responses. Symptom: the browser gives a decoding error or the file downloads instead of executing. Check with curl -I -H "Accept-Encoding: gzip" https://mysite.ru/bitrix/cache/css/file.css—headers should contain Content-Encoding: gzip.

For minified files with a hash in the name, we recommend configuring static (pre-compressed) compression via gzip_static on—nginx serves a pre-compressed .gz file without real-time CPU load.

Case from Our Practice

A corporate Bitrix site "Standard"—12 CSS and 23 JS files included via API. After enabling Bitrix minification and gzip on nginx: total CSS+JS size dropped from 1.4 MB to 180 KB (minification) → 48 KB (gzip). CSS requests reduced from 12 to 2, JS from 23 to 3. DOMContentLoaded time decreased by 0.8 s on 3G mobile connections.

Comparison of algorithms:

What's Included in the Work

• Audit of resource inclusion: identify "direct" CSS/JS inserts that are not processed by Bitrix.
• Migrate all files to API: AddCSSLink(), AddHeadScript().
• Enable built-in minification and merging in the admin panel.
• Configure gzip/Brotli on the server (nginx/Apache).
• Check for double compression and test on all pages.
• Prepare a before/after report.

Work Process

1. Analysis—study template structure, resource inclusion methods, current server stack.
2. Design—choose the optimal scheme (minification + gzip or Brotli, static compression).
3. Implementation—make changes to nginx config, configure Bitrix, modify templates if needed.
4. Testing—check HTTP headers, load speed (Lighthouse, WebPageTest), ensure no errors.
5. Deployment—apply to production, monitor for one week.

Setup takes from 4 to 8 hours depending on legacy code volume. Order a speed audit—we'll identify bottlenecks and configure compression turnkey. We guarantee stable operation—all changes are reversible. We have over 5 years of experience optimizing Bitrix projects.

Useful links:

• gzip on Wikipedia
• Brotli on Wikipedia

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.