1C-Bitrix Refactoring: Eliminate Technical Debt Without Downtime

Clean Code for 1C-Bitrix: Refactoring Without Risk

Typical scenario: init.php has grown to 3000 lines, direct SQL queries in template.php slow down pages, identical code is copied into 12 components. Adding a new field in the catalog requires edits in 8 places. This is technical debt, which reduces development speed and increases maintenance costs. We perform refactoring without changing external behavior, so the site continues to work the same, but the code becomes clean and maintainable. Our team has over 10 years of experience in 1C-Bitrix development and more than 50 successful refactoring projects.

Technical debt is a metaphor describing the extra costs of code maintenance caused by quick but suboptimal solutions. In Bitrix projects, it accumulates especially fast due to numerous integrations and custom logic. Budget savings on support can reach 60%—on average $5,000 to $15,000 per year for a typical project. For larger projects, savings can exceed $20,000 per year.

Why Refactoring Is Better Than Full Rewrite?

Full rewrite of a Bitrix project is a trap. Business logic accumulated over years in templates and handlers is not documented. Rewriting from scratch guarantees losing edge cases that were caught by hotfixes. The right approach is incremental refactoring: isolate one module, rewrite it, verify identical behavior, move on. Each iteration is a working site. Incremental refactoring is 2x cheaper and 3x faster than full rewrite. Compare:

Which Code Areas Need Refactoring First?

Priority 1 — decomposing init.php. A typical "bad" init.php contains event handlers, custom functions, classes, and direct initialization. The target state: init.php contains only require_once for the autoloader and handler registration. All logic goes into separate classes in /local/php_interface/classes/ or /local/modules/.

Structure of /local/:

/local/
  php_interface/
    init.php          → autoloader + registration
    classes/
      EventHandlers/  → Bitrix event handlers
      Helpers/        → utilities
      Services/       → business logic
  modules/
    project.core/     → custom project module
  components/         → custom components
  templates/          → site templates

Migration to /local/ is a standard Bitrix practice. Everything in /local/ takes precedence over /bitrix/, allowing kernel updates without conflicts. Investment in this stage usually pays back in 2–3 months by reducing time for modifications.

Priority 2 — moving logic out of component templates. A component template (template.php) should contain only HTML output. If it includes CIBlockElement::GetList(), $DB->Query(), or complex calculations, that's a problem. Three levels of refactoring:

1. result_modifier.php — transfer data preparation out of template.php.
2. class.php — create a component class extending CBitrixComponent.
3. Custom component in /local/components/project/ — when the standard component no longer fits requirements.

Priority 3 — replacing direct SQL with D7 ORM. Direct queries via $DB->Query() mean no escaping, database vendor lock-in, and no caching. Switch to D7 ORM or parameterized queries. According to official 1C-Bitrix documentation, D7 ORM enables queries with automatic caching and SQL injection protection.

Priority 4 — eliminating duplication. Use phpcpd to find identical code blocks across different templates. Typical pattern: the catalog.section component has 5 templates with 80% identical code, differing only in CSS classes. Solution: one template with parameters or include files.

How to Refactor Without Downtime?

1. Snapshot — create a backup and commit the current state in git.
2. Testing — write smoke tests for critical pages (HTTP statuses, key elements).
3. Replace — move one block of logic into a class, connect it, verify tests pass.
4. Remove — delete old code after confirming tests pass.
5. Deploy — push to production and monitor errors for 24 hours.

Typical Pitfalls in Refactoring

• Refactoring without VCS. Surprisingly, many Bitrix projects are still not in Git. The first refactoring step is initializing a repository with a correct .gitignore (exclude /bitrix/, /upload/, /vendor/, keep /local/).
• Switching to D7 "all at once." D7 API does not cover everything. Old API (CIBlockElement, CSale*) works and is supported. Only transition code you are refactoring—do not touch working old code for "consistency".
• Refactoring without monitoring. After deploying refactoring, watch b_event_log and server logs. Errors may appear only under certain conditions: specific product type, user group, or browser.

Timeline Estimates

Refactoring is an investment. Its effect is measured not visually, but in subsequent development speed and regression count during updates. To get a consultation and accurate estimate for your project, contact us. Order an audit right now.

Bitrix Site Audit: Find Problems Before They Find You

Imagine: you open a project from a previous team — init.php has 3,000 lines, OnBeforeIBlockElementUpdate handlers are nested, there's a 4GB dump.sql in the site root, and the upload/ directory is larger than the database. We see such projects every week. And this is not an exception — it's the norm for Bitrix after several years of active development without quality control. An audit of a 1C-Bitrix site is the only way to objectively assess the real state of a project before investing in improvements or scaling. It reveals bottlenecks in code, database, server configuration, and security. Most importantly, it shows what to fix to make the site faster and prevent crashes during peak sales. Regular 1C-Bitrix site audit pays off in 2–3 months: hosting savings are substantial, and error fix time is cut by three times compared to a reactive approach.

Why is a Bitrix site audit necessary?

Changing contractors — you take over a project from another team and don't know what "mines" are left in the code. Event handlers in init.php, forgotten scripts, modified kernel files — all can backfire at the worst moment. We once found 47 handlers in one project, 12 of which were dead — information blocks were deleted, but the code kept calling CIBlockElement::GetList() on every hit. For several years of such load — millions of extra queries to the database.

Position drop — technical reasons almost always underlie organic traffic loss: page duplicates, broken canonical, 50,000 junk URLs in the index. An audit will show where Google is losing your traffic. In one typical project, the number of URLs with sorting parameters reached 300,000 — each combination of PAGEN_1=2&sort=price was indexed separately.

Slowness under load — the site goes down right during a sale, when every minute of downtime costs money. We find the reasons: unoptimized queries, lack of cache, heavy agents. For example, one query to b_iblock_element_property without an index can add 3–4 seconds to page generation time.

Suspicion of hacking — spam emails from the server, redirects to casino on mobile traffic, strange files in /bitrix/modules/. A security audit will reveal backdoors and web shells.

Before major improvements — investing in project development without knowing its real state is like building a second floor without checking the foundation. Half of our clients come precisely before starting new functionality.

What hides in init.php and the database?

Most problems on Bitrix are concentrated in three places: init.php, the database, and server configuration. We break down each layer in detail.

init.php and event handlers — the main code dump. There accumulate OnAfterUserLogin, OnBeforeOrderAdd, OnAdminContextMenuShow that no one refactors for years. In one project we found 47 handlers, 12 of which were dead (information blocks deleted, but the code kept calling CIBlockElement::GetList() on every hit). An audit clears out such ballast and reduces server load.

Versions and compatibility. Kernel version — if below 22.0, update is critical (PHP 8.1 not supported). Marketplace modules often conflict after updates. License without an active key — no security updates.

Server configuration. PHP memory_limit < 256M — problems with catalogs of 10,000+ items. OPcache revalidate_freq = 0 in production — CPU overloaded. MySQL innodb_buffer_pool_size should be 70–80% of RAM. On MySQL 8.0+ query_cache is removed, but it remains in old configs — generating errors in logs. Absence of expires for static files in nginx — each page reload downloads JS/CSS again.

Database — the most interesting part. The b_event_log table grows to gigabytes without cleanup settings. In one project it occupied 12 GB, though 500,000 records were written daily. The b_search_content_text table with a full-text index can weigh more than the content itself. Tables from deleted modules (b_forum_*, b_learning_*) take up space and slow down backups. We enable slow query log, wait a day, analyze. One query to b_iblock_element_property without an index can slow the entire site — we recorded delays up to 7 seconds per page.

File system. /upload/resize_cache/ — weighs tens of gigabytes, stores resizes of long-deleted images. Backups in the root — backup_old.tar.gz next to index.php, accessible via direct link. Manually modified kernel files will be overwritten during update, and custom logic will silently disappear.

How does SEO audit remove duplicates and trash from the index?

Filter and sort parameters generate thousands of URLs: /catalog/?PAGEN_1=2, /catalog/?sort=price&order=asc — each indexed as a separate page. Bitrix SEO module can set canonical, but by default it doesn't do it for parameterized URLs. The standard robots.txt blocks /bitrix/, but doesn't block /search/, /personal/, /ajax/ — there are thousands more junk pages. Bitrix's sitemap.xml generator sometimes includes inactive items and 404 pages. Without structured data Schema.org (Product, BreadcrumbList, Organization), snippets in search results are bland. Core Web Vitals: LCP > 2.5s on mobile is common for unoptimized Bitrix — unoptimized images and blocking JS are to blame. On average, after an audit we reduce the index by 60–80% — remove duplicates, set up canonical and proper noindex. Order an SEO audit to get your site the traffic it's losing now.

Why check Bitrix security?

SQL injections via $_REQUEST in custom components — previous developers don't always use $DB->ForSql(). XSS when outputting user input without htmlspecialcharsbx(). Custom file upload forms that don't check MIME type and extension — upload .php as an "image" and get a web shell. Typical findings: disabled "Proactive Protection" module (WAF not working, intrusion log empty), admin panel without IP restriction (/bitrix/admin/ open to the world), adminer.php or phpMyAdmin in the root — forgotten after migration, obfuscated code in .htaccess with mobile traffic redirect via RewriteCond %{HTTP_USER_AGENT}, modified kernel files with eval(base64_decode(...)) inserts. In one project we found 23 such files — the site had been distributing spam content via AMP for months. Read more about SQL injection and cross-site scripting. Contact us for a security check of your project — we will find vulnerabilities that scanners miss.

How do we improve performance?

We profile using Blackfire or Tideways — see which functions consume CPU. A frequent candidate is CIBlockElement::GetList() in a loop (classic N+1). We check hit rate of OPcache, Memcached, Bitrix managed cache. If composite site cache invalidates on every order, it's useless — we once reduced invalidations from 80% to 2% by proper tag configuration. Bitrix agents — if agents_use_crontab is not enabled, they execute on user hits; a heavy agent = slow for random visitor. Load testing: base RPS, degradation at 2× and 5× load, behavior when limit exceeded (graceful degradation or 502 Bad Gateway?). On one project we found peak RPS was 12, and after optimization became 150 — a 12.5x increase.

What do we look for in code?

We assess custom developments of previous teams: do they use D7 ORM or just $DB->Query() bypassing everything. PSR-12, autoloading, module structure — or everything in one file. N+1 — GetList() inside while($arItem = $rsItems->Fetch()) — classic. Modified kernel files (bitrix/modules/sale/lib/) with manual edits — updates will break everything. "Temporary" solutions living for three years — // TODO: redo from last year. On average, we find 15–25 problems in code per project, half of them with potential data loss.

Report format

Each problem is described by scheme: what we found → where → how it affects → how to fix → effort. We deliver the report in PDF and Google Docs for collaboration. Five signs that a Bitrix site needs an audit: init.php has grown over 2,000 lines; database exceeds 5 GB, and b_event_log table over 1 GB; pages load longer than 3 seconds on mobile; Search Console shows tens of thousands of pages in index with errors; you found files with suspicious content in /bitrix/modules/. If at least one point matches — time to order an audit.

How do we conduct an audit?

1. Access — Bitrix panel, SSH, database, Yandex.Webmaster, Search Console.
2. Automation — Bitrix "Quality Monitor", Screaming Frog, GTmetrix, security scanners. Catch 60% of problems.
3. Manual analysis — the remaining 40%. Architecture, code, business logic, configuration — only hands-on. Each audit is led by a senior developer with 10+ years of experience.
4. Report with priorities.
5. Discussion — meeting with you, answering questions, agreeing on a remediation plan.

Average time for a full cycle — 5 business days for technical audit, up to 3 weeks for comprehensive. We guarantee confidentiality of results and safety of your data.

What is included in deliverables?

• Documented report with description of each problem and fix recommendations.
• Checklist of critical vulnerabilities and their priority.
• List of performance optimization suggestions with impact assessment.
• Post-audit consultation — review of results, task prioritization.
• Access to test results (screenshots, profiling logs, raw data).

Types of audit and timelines

We have conducted 50+ audits of Bitrix projects — from online stores to corporate portals. Our experience shows: on average, an audit pays off within 2–3 months by reducing hosting costs and cutting error fix time (3 times faster than reactive approach). Regular audit is the best way to extend project life.

Result — not a stack of papers, but a guide to action with concrete tasks and priorities. Need an audit of your Bitrix site? Get a consultation today — contact us, and we will assess your project for free within 1 business day. Order a comprehensive audit to get the full picture before serious investments.