Optimizing 1C-Bitrix with HTTP/2

Imagine a Bitrix site loading in 4 seconds, despite a powerful server and caching enabled. The problem is the protocol — HTTP/1.1 opens 6-8 parallel TCP connections and loads resources sequentially. With 40+ files on a page, a queue forms due to head-of-line blocking. HTTP/2 solves this with multiplexing: all requests go over a single TLS connection, and the server responds without connection delays. This reduces TTI (Time to Interactive) by 200–400 ms — real numbers from our projects. We configure HTTP/2 turnkey: audit, configuration, optimization.

Why HTTP/2 is critical for 1C-Bitrix

Bitrix is a system with a huge number of included modules: bitrix.js, core.css, dozens of scripts in /bitrix/js/. With HTTP/1.1, each file requires its own connection and full handshake. HTTP/2 solves this via multiplexing. This is especially important for Bitrix e‑commerce stores with catalogs of 100,000+ items. In our measurements, HTTP/2 speeds up page loading up to 2x compared to HTTP/1.1 with a typical resource set.

How to set up HTTP/2: main steps

1. Install an SSL certificate — browsers require TLS for HTTP/2.
2. Verify Nginx version — 1.9.5+ with http_v2 module. Command: nginx -V 2>&1 | grep http_v2.
3. Modify the virtual host configuration — add http2 to listen 443 ssl http2;.
4. Configure Server Push for critical resources (Bitrix core CSS and JS).
5. Test using curl -I --http2 and Chrome DevTools.

Requirements for HTTP/2

HTTP/2 works over TLS in browsers (h2c is not supported). Therefore, a valid SSL certificate is mandatory. Nginx must be compiled with http_v2 module:

nginx -V 2>&1 | grep "http_v2" # Should output: --with-http_v2_module 

OpenSSL needs version 1.0.2+ for ALPN.

Nginx configuration for HTTP/2

In the virtual host config:

server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name example.ru www.example.ru; ssl_certificate /etc/ssl/certs/example.ru.crt; ssl_certificate_key /etc/ssl/private/example.ru.key; # Modern cipher suites (HTTP/2 forbids obsolete ones) ssl_protocols TLSv1.2 TLSv1.3; ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384; ssl_prefer_server_ciphers off; # HSTS add_header Strict-Transport-Security "max-age=63072000" always; # TLS optimization ssl_session_cache shared:SSL:10m; ssl_session_timeout 1d; ssl_session_tickets off; root /var/www/bitrix/public_html; index index.php; } # HTTP -> HTTPS redirect server { listen 80; server_name example.ru www.example.ru; return 301 https://$host$request_uri; } 

How Server Push works and why it matters for Bitrix

Server Push allows the server to send CSS and JS before the browser requests them. For Bitrix, this makes sense for the main CSS and the core JS bundle. On one project with a 200,000‑item catalog, we reduced TTI from 1.7 s to 0.6 s using Server Push. Configuration in Nginx:

location = / { http2_push /bitrix/templates/.default/styles.css; http2_push /bitrix/js/main/core/core.js; http2_push /bitrix/themes/.default/icons/sm/logo.png; } 

Or via Link headers from PHP with http2_push_preload on enabled.

Recommended Nginx settings for HTTP/2

Checking HTTP/2 operation

curl -I --http2 https://example.ru/ # Expected: HTTP/2 200 

In Chrome DevTools, the Protocol column should show h2.

Typical problem: Mixed Content

After switching to HTTPS + HTTP/2, Bitrix may generate http:// references. These are blocked by the browser. Check dbconn.php:

$_SERVER["HTTPS"] = "on"; define("SITE_SERVER_NAME", "example.ru"); 

And in the main module settings, enable "Use secure connection (https)".

Comparison with HTTP/1.1

HTTP/2 delivers a 2–4x speed improvement when many files are loaded. For Bitrix this is especially relevant: a typical page contains 30–50 resources. With HTTP/2, time to first interactive state drops by 200–400 ms, positively affecting SEO and conversion.

What turnkey HTTP/2 setup includes

• Audit of current server and site configuration (Nginx, PHP, Bitrix).
• Installation or validation of an SSL certificate (including chain).
• Virtual host configuration with HTTP/2, modern cipher suites, and HSTS.
• Server Push optimization for critical resources (core.css, core.js).
• Mixed Content check and link fixes in Bitrix settings.
• Performance testing: TTI measurements before and after.
• Documentation of the configuration and monitoring recommendations.

Timeline: from 1 day to 5 days depending on complexity and number of hosts. Cost is calculated individually after the audit.

Why order HTTP/2 setup from us?

We have configured HTTP/2 for Bitrix projects with loads up to 50,000 visitors per day. Over 5 years of experience and 80+ projects. We guarantee compatibility with all current Nginx and PHP versions. Order an audit — get a consultation and cost estimate within a day. Contact us for details.

RFC 7540 — HTTP/2 HTTP/2 on Wikipedia