A visitor comes to your site at night, and the interface blinds them with a white background. If the dark mode toggle is poorly implemented, the user sees a white flash (FOUC) before the theme changes. They leave in under 3 seconds. We configure dark mode for 1C-Bitrix with smooth transitions, saved preferences, and no broken components. We offer a turnkey solution with a 12-month warranty. Get a free consultation — we'll estimate your project in 2 hours.
How we implement dark mode turnkey
The process takes 2–3 days. First, we audit the current template: colors, fonts, images. Then we convert all colors to CSS custom properties. We already have a proven system of 20+ variables for basic elements (background, text, accents, borders). This is faster than building from scratch. On one project with a catalog of 50,000 items, we saved about 30% development time by reusing variables and avoiding selector overrides.
The key feature: the theme detection script loads inline before styles. Without this, FOUC occurs. We insert it into header.php right after <head>:
<head>
<meta charset="UTF-8">
<script>
(function() {
const t = localStorage.getItem('theme')
|| (window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light');
document.documentElement.setAttribute('data-theme', t);
})();
</script>
<?php $APPLICATION->ShowHead(); ?>
</head>
The script instantly sets the data-theme attribute on the root element, and all styles apply without delay. This avoids the characteristic white flash even on slow devices.
Why CSS custom properties instead of classes?
An alternative approach is adding a .dark class on the body and overriding styles via specificity. But that leads to code duplication and complicates maintenance. CSS custom properties work faster (the browser doesn't recalculate selectors) and allow theme changes by simply overriding the values in one place. In our tests, rendering speed improved by 10–15%. The initial cost of implementing with variables is comparable, but long-term maintenance is significantly cheaper.
| Approach |
Speed |
Browser Support |
Migration Complexity |
| CSS custom properties |
High |
Modern (96%+) |
Low (just change values) |
| Class-based |
Medium |
All including IE11 |
High (override every selector) |
| Separate CSS file |
Low |
All |
High (code duplication) |
We recommend CSS custom properties. For IE11, we provide graceful degradation without dark mode. More about CSS custom properties on MDN.
How to avoid FOUC on page load
FOUC is the main issue with dark mode. If dark mode styles load asynchronously or after rendering, the user sees a white flash. Our solution: the inline script in <head> (see above) sets data-theme before CSS loads. All styles use var(--color-xxx) defined for each attribute.
Adapting images and components
Standard Bitrix blocks (.bx-sls, .popup-window-content, authorization form) have their own styles. We override them using selectors with data-theme:
:root[data-theme="dark"] .bx-sls {
background: var(--color-card-bg);
color: var(--color-text);
}
:root[data-theme="dark"] .popup-window-content {
background: var(--color-bg);
border-color: var(--color-border);
}
For images, we use <picture> or CSS filters. It's best to prepare a dark version of the logo and insert it via prefers-color-scheme. Logos with transparency require a separate version. For icons, you can apply a CSS filter invert(1) on a light background, but on dark backgrounds the result may be unreadable. We recommend preparing two sets of icons: light and dark. Background gradients should be overridden via CSS custom properties.
Common mistakes during implementation
First mistake: forgetting about components that render asynchronously (e.g., cart in a popup). Second: not handling images with inline styles. Third: not saving the theme choice in the Bitrix authorized user profile, causing the setting to reset after logout. We cover all these cases during testing.
What is included in the work
- Audit of current styles and components
- Migration of colors to CSS custom properties (main file + components)
- Inline theme detection script (no FOUC)
- Theme toggle button (desktop + mobile)
- Saving choice in localStorage and authorized profile (Bitrix)
- Image adaptation (logos, icons, backgrounds)
- Override of standard components: smart search, popups, authorization
- Testing in Chrome, Firefox, Safari, Edge
- Documentation of variables and API
- Content manager training
Stages and timelines
| Stage |
Time |
| Audit and design |
1–2 h |
| Migration to variables |
6–12 h |
| Script and toggle logic |
2–3 h |
| Image adaptation |
2–4 h |
| Component overrides |
3–6 h |
| Testing and fixes |
2–3 h |
Total 2 to 3 days depending on template complexity. Contact us for a preliminary estimate — it takes less than an hour. Experience with Bitrix: 8+ years, over 50 projects completed. We provide a 12-month warranty on all work. Order dark mode implementation today.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
