We have been developing custom slider Bitrix solutions for over 4 years. Our custom component loads 3 times faster than the standard advertising module. During this time, we have accumulated experience that allows us to create performant and easy-to-manage bespoke slider components. The standard bitrix:advertising.banner component does not meet modern requirements: responsiveness, video backgrounds, lazy loading, WebP. Instead, we use information blocks and tailored components, giving the marketer full control via the admin panel and the frontend fast rendering. The limitations of the advertising module become critical when developing a full-screen slider on the homepage or a dynamic banner grid in the catalog. For example, a manager cannot replace an image without knowing HTML, and the mobile version looks like a scaled-down copy of the desktop. Our approach solves these problems, saves the client's budget on refinements, and speeds up page loading by 30-50%.
Custom Slider and Banner Development: Key Solutions
Why the Standard Advertising Module Is Not Suitable
The advertising module in 1С-Битрикс stores banners in the b_adv_banner table. Each banner is HTML code in the MESSAGE field. Drawbacks:
- The editor is a textarea; a manager without layout skills cannot change the content.
- No slider: each banner is independent, no ordering.
- No responsive images: one banner for all screens.
- No support for modern formats (WebP, AVIF) and lazy loading.
All these limitations are solved by custom development using information blocks.
How We Do It: Information Block + Component
A practical solution is a separate information block called "Sliders and Banners". Each element is one slide, sections are placement zones (hero-slider, catalog-banner, etc.). Property structure:
| Property |
Type |
Purpose |
| IMAGE_DESKTOP |
File |
Image for desktop |
| IMAGE_MOBILE |
File |
Image for mobile |
| VIDEO_BG |
File |
Video background (MP4) |
| TITLE |
String |
Title |
| SUBTITLE |
String |
Subtitle |
| BUTTON_TEXT |
String |
Button text |
| BUTTON_LINK |
String |
Link |
| BG_COLOR |
String |
Background color |
| TEXT_COLOR |
List |
light / dark |
| SORT |
Number |
Order |
The component local:banner.slider accepts parameters: IBLOCK_ID, SECTION_CODE, SLIDER_ENGINE (swiper, splide, native), AUTOPLAY, LAZY_LOAD, CACHE_TIME. In class.php, active elements are selected, WebP versions are generated, and a <picture> with <source> is output.
Example component configuration
$APPLICATION->IncludeComponent(
"local:banner.slider",
"",
array(
"IBLOCK_ID" => 25,
"SECTION_CODE" => "hero",
"SLIDER_ENGINE" => "splide",
"AUTOPLAY" => "Y",
"AUTOPLAY_SPEED" => 5000,
"LAZY_LOAD" => "Y",
"CACHE_TIME" => 36000000,
"CACHE_TYPE" => "A",
"USE_WEBP" => "Y",
)
);
A custom slider on information blocks runs 1.5-2 times faster due to tagged caching and image optimization. As stated in the official documentation: "Tagged caching allows you to reset only the cache of those components whose data has changed." More about caching can be found in the 1С-Битрикс documentation.
Choosing a Slider Library
Swiper is the de facto standard at 140 KB, supporting touch, lazy loading, and parallax. Splide is a lightweight alternative (30 KB) with no dependencies. Native CSS uses scroll-snap-type with zero JS for basic scrolling. We recommend Splide for typical projects, Swiper for complex ones, and native for minimalistic ones.
How to Optimize Slider Loading?
The slider on the homepage is the first element affecting LCP. Key rules:
- First slide without lazy load:
loading="eager", fetchpriority="high".
- Preload the first image in
<head> via addString().
- WebP versions: desktop 1920x600 in WebP weighs 80-150 KB vs 200-400 KB JPEG.
- Video background: H.264, 1280x720, 1-2 Mbps, duration up to 10 s. Replaced with a static image on mobile.
These measures reduce the volume of downloaded data by up to 30%, positively impacting LCP and overall load budget. We have optimized over 60 sliders for our clients.
Management for Marketers
The manager works in the information block interface: creates an element, uploads images, fills in texts, sets dates. Preview is available through a custom template. Sorting is done via drag-and-drop or the SORT field. No HTML required.
What's Included in Development
- Designing the information block structure according to the task
- Developing a component with support for the chosen library
- Responsive layout (desktop, tablet, mobile)
- WebP/AVIF generation, preload, lazy loading
- Video background integration
- Cache configuration
- Documentation for the marketer
Work Process
- Analysis — we study requirements, layouts, prototypes.
- Design — we define the information block structure and component parameters.
- Development — we write the component, layout, integration.
- Testing — we check on all devices and browsers.
- Deployment and handover — we install on the production server and train the manager.
Estimated Timeline
| Variant |
Scope |
Duration |
| Single slider |
Information block, component, Splide, responsiveness, WebP |
3-5 days |
| Banner system |
Multiple zones, video backgrounds, preload, analytics |
8-12 days |
Development cost starts at $1,200 for a single slider. Our clients save an average of $400 per month on CDN costs after switching to WebP. Order development of three or more sliders and receive a 10% discount.
Our Experience and Guarantees
We have been developing on 1С-Битрикс for over 4 years and have completed more than 50 projects with custom sliders. With over 95% client satisfaction, we guarantee code quality and prompt support. We use only proven libraries and approaches.
Contact us to order custom slider and banner development.
1C-Bitrix Module Development and Setup
The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.
Why is init.php the worst place for business logic?
Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.
Standard Modules: Typical Problems and Solutions
Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.
e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.
Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.
Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.
Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.
How to Design Infoblocks for Performance?
We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.
Custom Module Development
Each module follows the structure /local/modules/vendor.modulename/:
-
install/index.php — setup class, create tables via $DB->RunSQLBatch()
-
lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
-
admin/ — administrative pages using CAdminList, CAdminForm
-
include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
- REST API endpoints via
\Bitrix\Rest\RestManager
The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.
Examples of implemented tasks:
- Campaign management — visual condition builder via
CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
- Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
- Booking system — real-time calendar, locking via
$DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook
Components and Composite Cache
Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.
Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.
What to Check Before Installing a Marketplace Module?
Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.
Migration to D7
When upgrading PHP or switching to a new edition — refactor outdated calls:
-
CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
-
CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
-
CModule::IncludeModule() → Bitrix\Main\Loader::includeModule()
Testing on staging, rollback via git on issues.
According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.
Comparison: Init.php vs Module
| Criterion |
Init.php |
Module with D7 ORM |
| Performance |
Executes on every hit |
Executes only on event |
| Testability |
No autoloading, tests impossible |
Full PHPUnit support |
| Maintainability |
Codebase grows uncontrollably |
Isolated structure, versioning |
| Migrations |
None |
Custom tables, managed via install |
| Caching |
Does not support auto-invalidation |
Tagged caching, event-based clearing |
Module Development Scope and Cost
What is included in module development?
- Technical specification and architectural plan
- Code following PSR-4 and Bitrix code style
- Unit tests (PHPUnit) for business logic
- Integration tests for events and REST API
- Installation, configuration, and API documentation
- Repository and documentation access
- Administrator training for module usage
- 6-month warranty support
Estimated timelines and complexity:
| Complexity |
Examples |
Timeline |
| Simple |
Callback widget, banner system, simple calculator |
3–5 days |
| Medium |
Booking system, product configurator, review module with moderation |
1–2 weeks |
| Complex |
Multi-regionality, custom loyalty program, ERP integration |
2–4 weeks |
| Enterprise |
Marketplace platform, complex business processes with multiple roles |
1–3 months |
Cost is calculated individually — contact us for a project estimate.
Module Testing
Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.
Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.
Practical Examples
Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.
Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.
Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.
We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.
