Corporate Website Development on 1C-Bitrix

Corporate Website Development on 1C-Bitrix

When 200 visitors hit the site, it starts lagging and forms fail to submit? A typical scenario: you chose the "Small Business" edition for a simple one-page site, infoblocks lack indexes, caching is disabled. The result—lost leads and frustration. We develop corporate one-page sites on 1C-Bitrix where every detail is tuned for performance and conversion.

A one-page site on Bitrix is not just a contact page. It's the client's entry point where loading speed and working contact forms decide whether a visitor leaves or submits a request. Below we dive into technical nuances: from license selection to cache configuration, saving up to 30% on hosting costs.

Which Bitrix License to Choose for a One-Page Site?

For a corporate site without a store, the "Start" or "Standard" editions suffice. "Small Business" and "Business" are needed when you plan a catalog with orders. For a one-pager with forms, news, and services—"Standard" covers all needs: multisite, managed cache, web forms.

According to 1C-Bitrix documentation, for projects with up to 5000 daily visitors, "Start" (one site, no web cluster) is enough. The "Start" license costs ~$55/year—optimal for a one-page site. If you need a multilingual project or backups, go with "Standard".

Problems We Solve

1. Slowdowns under peak traffic. 90% of timeouts are due to missing managed cache. We enable HTML cache for static pages and configure Redis for block caching—database load drops by 60%.
2. Forms losing leads. The standard bitrix:main.feedback component processes requests 1.5x slower than a custom AJAX form. We use the latter: JS validation, controller sending with lead creation in CRM. Testing shows conversion increases by 25%.
3. Incorrect SEO markup. Without auto-templates for meta tags, service and news pages aren't indexed properly. We set up templates for title, description, canonical—search visibility doubles.

How to Speed Up a One-Page Site by 2x?

The main boost comes from caching. For a one-pager with up to 1000 unique daily visitors, three steps suffice:

1. Enable managed cache for all components via the admin interface.
2. Use file cache or Redis—set cache_engine in settings.php.
3. Apply HTML cache for the homepage and key pages via bitrix:main.include:

$APPLICATION->IncludeComponent('bitrix:main.include', '.default', [
    'AREA_FILE_SHOW' => 'sect',
    'PATH'           => '/index.php',
    'EDIT_TEMPLATE'  => 'index',
    'CACHE_TYPE'     => 'A',
    'CACHE_TIME'     => 3600,
]);

After these steps, page generation time drops from 2 seconds to 0.3-0.5. Proven on 60+ successful launches. With proper caching, you can save up to $400/year on hosting.

Why Custom AJAX Forms Are Faster?

The standard Bitrix form (bitrix:main.feedback) calls the main module, generating extra SQL queries. A custom AJAX form does it 2-3 times faster. Example handler:

// /local/ajax/contact_form.php
require_once $_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php';

if ($_SERVER['REQUEST_METHOD'] !== 'POST' || !check_bitrix_sessid()) {
    http_response_code(403);
    echo json_encode(['error' => 'Forbidden']);
    exit;
}

$name  = htmlspecialchars(trim($_POST['name'] ?? ''));
$phone = htmlspecialchars(trim($_POST['phone'] ?? ''));
$email = htmlspecialchars(trim($_POST['email'] ?? ''));

if (empty($name) || empty($phone)) {
    echo json_encode(['error' => 'Fill in required fields']);
    exit;
}

if (\Bitrix\Main\Loader::includeModule('crm')) {
    $lead = new \CCrmLead(false);
    $lead->Add([
        'TITLE'      => 'Site lead from ' . $name,
        'NAME'       => $name,
        'PHONE'      => [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']],
        'EMAIL'      => [['VALUE' => $email, 'VALUE_TYPE' => 'WORK']],
        'SOURCE_ID'  => 'WEB',
    ]);
}

$event = new \Bitrix\Main\Mail\Event([
    'EVENT_NAME' => 'CONTACT_FORM_SUBMIT',
    'LID'        => SITE_ID,
    'C_FIELDS'   => ['NAME' => $name, 'PHONE' => $phone, 'EMAIL' => $email],
]);
$event->send();

echo json_encode(['success' => true]);

Such a form can handle up to 1000 daily submissions without increasing server load. Plus—full control over design and logic.

Infoblock Structure

Typical infoblock set for a corporate site:

All under one type CORPORATE. Activate SEO properties at both section and element levels—otherwise meta tags won't fill.

Common Mistakes in One-Page Site Development

• Choosing an edition with excessive functionality (overpaying 2-3x).
• Missing auto-templates for SEO tags—pages not indexed.
• Using the standard feedback form instead of AJAX—lost conversion.
• Ignoring caching—site lags under 100 visitors.
• Not setting up infoblock indexes—slow database queries.

Multilingual Support

When needed, we configure a multisite setup on "Standard"+ license. Each language gets a separate SITE_ID with a folder (/en/, /de/). Content translations via infoblock language properties, interface labels via language files.

What's Included

• Responsive template markup based on your design.
• Infoblock setup (news, services, portfolio, team, reviews, vacancies, partners).
• Custom AJAX contact forms integrated with Bitrix24 CRM.
• Managed cache and Redis configuration for maximum performance.
• SEO meta-tags and auto-templates.
• Integration with external services (as needed).
• Documentation on structure and settings.
• Editor training (2 hours via Zoom).
• 2 weeks of free support after launch.

Process

1. Analysis: Discuss requirements, choose edition, design structure.
2. Design: Create prototypes, agree on infoblock architecture.
3. Implementation: Template markup, component overrides, cache and form setup.
4. Integration: Connect Bitrix24 CRM, configure automated lead creation.
5. Testing: Load testing (up to 5000 requests), mobile device checks.
6. Deployment & Training: Deliver documentation, 2-hour Zoom training for editors, 2 weeks free support.

Estimated Timelines

Ready to Get Started?

We assess each project individually, so the cost is determined after analysis. Contact us for a free engineering consultation and a site ready to grow.

We are a certified 1C-Bitrix partner with extensive experience—60+ successful projects behind us.

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

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:

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.