Cloudflare CDN for 1C-Bitrix: Static Caching & Optimization

Typical situation: a Bitrix site runs slowly at 50–100 RPS. The origin server becomes saturated because Nginx allocates resources to serve static assets. Consider a catalog of 50,000 products with photos of 2 MB each. Without CDN, each visitor loads images from your server, generating 200–300 RPS on static files — Nginx and PHP-fpm are idle, processing requests that could be served from a cheap edge. We solve this problem by connecting Cloudflare CDN. Static files are served from edge servers, while the origin handles only dynamic content. Server load drops by 40–70%, and page load performance increases. Hosting costs decrease by 40–70%. Cloudflare CDN reduces server load by up to 70%, which is 2–3 times better than typical caching solutions.

What to cache and what not

Cloudflare by default caches files by extension: .js, .css, .jpg, .png, .woff2, .svg and others. HTML and PHP are not cached. For Bitrix this is correct — dynamic pages must be generated on the server. We implement static caching Cloudflare to offload origin.

Exceptions are configured via Page Rules or Cache Rules:

Reasons Cloudflare may not cache static files

Common issue: Cloudflare shows DYNAMIC for .js and .css. Reason: server sends Cache-Control: no-store or Set-Cookie. Bitrix may add a session cookie on any request. Solution: configure Nginx so that static files are handled directly, without passing to PHP. Add a separate location:

location ~* \.(js|css|jpg|jpeg|png|gif|ico|svg|woff|woff2|ttf|eot)$ {
    expires 30d;
    add_header Cache-Control "public, immutable";
}

The immutable directive tells the browser that the file will not change — the browser will not send a conditional request (If-Modified-Since). For Bitrix this is correct because the bundler (Vite/webpack) adds a hash to the filename on each build.

Setting up Cloudflare CDN for Bitrix

1. Add your domain to Cloudflare — change NS records to those provided by Cloudflare.
2. Configure DNS — ensure A records point to your server, enable orange cloud for proxy.
3. Configure Page Rules — for paths /upload/* and /bitrix/images/* set Cache Level: Standard and Edge Cache TTL: 1 month. For /bitrix/admin/*, /personal/*, /auth/* — Cache Level: Bypass.
4. Enable optimizations — in Dashboard: Speed → Optimization enable Polish (lossy) and Brotli. Auto Minify for JS and CSS (disable HTML).
5. Verify caching — open developer console and check headers on a static file. Should have cf-cache-status: HIT.

Comparison before and after CDN setup

Minification and optimization

Cloudflare offers Auto Minify for JS, CSS, and HTML. For Bitrix, disable HTML minification — it may break inline <script> tags and inline styles. JS and CSS minification can be kept, but if you already minify at build stage (Vite, webpack), Cloudflare minify adds no benefit and only adds edge delay. Additionally, use Concatenation and Cache Key features for better cache hit ratio. Advanced concepts like origin shielding and edge cache invalidation further optimize performance.

Polish (image optimization) — enable. Compresses JPEG and PNG without quality loss (lossy/lossless). For catalogs with thousands of product photos, traffic savings reach 20–30%. In fact, Cloudflare CDN with Polish reduces image sizes by an additional 20–30% compared to no optimization. It also converts images to WebP automatically where supported, further reducing weight by 25%.

Brotli compression — enable. Cloudflare compresses text responses (HTML, JS, CSS) with Brotli algorithm, which is 15–20% more efficient than gzip. Our experience shows noticeable speedup for users with slow internet. More about Brotli.

Verifying CDN operation

After setup, check response headers for a static file:

• cf-cache-status: HIT — file served from Cloudflare cache.
• cf-cache-status: MISS — file fetched from origin (first request or cache expired).
• cf-cache-status: DYNAMIC — Cloudflare does not cache this resource (HTML, PHP).

If you see DYNAMIC for .js or .css — check if origin sends Cache-Control: no-store or Set-Cookie. Cloudflare does not cache responses with Set-Cookie, and Bitrix may send session cookie on any request. Ensure that for static files, Nginx handles directly without passing to PHP.

What's included in the work

We provide a full scope of work with clear deliverables:

• Documentation: Detailed configuration report with all changes made (Nginx, Page Rules, DNS settings).
• Access: We ensure you have full access to Cloudflare dashboard and explain key settings.
• Training: A 1-hour online session for your team on how to manage CDN settings.
• Support: 30 days of post‑setup support for any issues or adjustments.
• Guarantee: If after our setup CDN works incorrectly, we fix it for free.

Our experience: over 5 years on the market, 200+ projects on Bitrix, certified specialists. Order a site audit — we will prepare a custom proposal.

Get an engineer consultation — we will assess your project within 1 day. As noted in Cloudflare documentation, proper caching configuration boosts performance manifold. Our Cloudflare CDN Bitrix expertise ensures maximum edge cache utilization.

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.