Client pain point: slow filter, zero counters, page freezes
A client reports: 'The smart filter on the catalog is sluggish, counters don't update, and selecting multiple properties freezes the page for 10 seconds.' The catalog has 200,000 products; the filter cannot cope—managers complain, buyers leave. We have configured faceted search for dozens of projects and know the solution takes 4–8 hours without rewriting the core. Typical setup cost starts at $500, with savings up to $2,000 compared to a full solution replacement (40% budget reduction). Conversion increase of 15% after filter optimization is not uncommon. Our team specializes in bitrix development and filter optimization bitrix for trade catalogs of any size.
How the faceted index works
Faceted index is a precomputed table that stores, for each property value (color, size, brand), the product count. It uses an inverted index structure to precompute aggregates, similar to a star schema in data warehousing. Without the index, every smart filter query triggers heavy JOIN queries on b_iblock_element_property, causing timeouts for catalogs of 100,000+ products. With the index, the query becomes a lightweight SELECT on pre-prepared data from b_iblock_facet_* and b_iblock_facet_data_* tables. Response time drops from 10 seconds to 0.3 seconds—a 30x improvement. More about faceted search can be found at Wikipedia. Official documentation: component bitrix:catalog.smart.filter.
Quick Faceted Search Setup for Existing Catalog
Step-by-step instruction
- Attach the
bitrix:catalog.smart.filter component to the catalog section page.
- Specify
IBLOCK_ID, PRICE_CODE, and the list of properties for filtering (e.g., COLOR, SIZE, BRAND).
- Set
AJAX_MODE = Y and SEF_MODE = Y.
- Configure SEF-URL templates.
- Rebuild the faceted index.
Example minimal configuration:
$APPLICATION->IncludeComponent('bitrix:catalog.smart.filter', '', [
'IBLOCK_ID' => 5,
'IBLOCK_TYPE' => 'catalog',
'PRICE_CODE' => ['BASE'],
'PROPERTY_CODE' => ['COLOR', 'SIZE', 'BRAND'],
'FILTER_VIEW_MODE' => 'POPUP',
'AJAX_MODE' => 'Y',
'SEF_MODE' => 'Y',
'SECTION_ID' => $arResult['ID'],
'SECTION_CODE' => $arResult['CODE'],
]);
Note: AJAX_MODE = Y is mandatory; otherwise the page reloads completely. SEF_MODE = Y produces human-readable URLs like /catalog/obuv/color-chernyj/.
Zero Counters in Faceted Search: Causes and Fixes
The most common cause: the faceted index is not rebuilt after a mass import. You loaded 10,000 products via CommerceML, but the index is still old. Solution:
- Go to the admin panel:
Shop → Catalog → More → Rebuild smart filter.
- Or run programmatically:
\CIBlockCatalogTools::ReIndexFacets($iblockId);
For catalogs over 50,000 products, we recommend running reindex via an agent during night hours to avoid load on the main application. This reduces server load by 40% during peak hours.
Which properties to include in the faceted filter?
Not all properties are needed. The common mistake of beginners is to include everything. Selection rules:
- Include: color, size, brand, material, category, price range—those actually used for search.
- Do not include: unique identifiers, SKUs, descriptions—they are not part of filtering.
- Properties of type 'List' and 'Link to elements' index faster than 'String'.
Configuration: Content → Infoblocks → [infoblock] → Properties → [property] → Participate in smart filter.
How to set up SEF mode for the filter?
In SEF mode, filter URLs look like /catalog/obuv/color-chernyj/size-42/. For proper operation, SEF templates in the catalog component and in the smart filter must be coordinated. Detailed documentation is available at dev.1c-bitrix.ru. If SEF is not configured, the filter works via GET parameters, which is worse for SEO. To enable SEF filter bitrix, set SEF_MODE=Y in both components.
Checklist for slow filter optimization
| Problem |
Check |
Solution |
| Slow loading |
EXPLAIN queries on b_iblock_facet_* |
Add indexes — 2–3x speedup |
| Large table size |
Size of b_iblock_facet_data_* |
Limit properties to 10–12 |
| Cache not working |
USE_CACHE = Y in parameters |
Enable tagged caching |
| Outdated index |
Last rebuild date |
Run reindex weekly |
Performance comparison before and after
| Parameter |
Before |
After |
| Page load time |
10 s |
0.3 s |
| Server load |
High |
Low |
| Conversion |
2% |
3.5% |
What's included in our turnkey faceted search setup
We provide:
- Audit of current smart filter configuration and performance.
- Faceted index setup with optimal property selection.
- Enable and configure SEF mode.
- Query optimization using EXPLAIN plans and indexing.
- Caching optimization with tagged cache.
- Administrator training on filter usage.
- Written documentation of settings.
Why trust us with the setup?
10+ years of experience with 1C-Bitrix, 40+ projects implemented, including large e-commerce stores with catalogs up to 500,000 products. We guarantee the filter will work fast and without failures. For comprehensive filter optimization bitrix, contact us for an audit — get a consultation and timeline estimate.
Timeline
Smart filter setup with required properties and SEF mode — from 4 to 8 hours. Full performance optimization for large catalogs — from 1 to 2 business days. Timeline is discussed individually after analyzing your project.
To evaluate the scope of work, request a free audit of the current filter state — we will suggest the optimal solution.
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.
