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

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.