Bitrix sites often load slowly on mobile devices, especially with heavy JS and CSS. Google's AMP technology offers a solution, but implementing it on Bitrix is tricky: you can't use jQuery, BX.ajax, or standard components. AMP requires a separate template with strict constraints. Our team specializes in setting up AMP for Bitrix turnkey, ensuring your mobile pages load under a second while maintaining functionality like 54-FZ compliance.
What problems does AMP solve on Bitrix?
The main problem is mobile load speed. A typical Bitrix page can weigh 2-3 MB and take 5-6 seconds to load. AMP, through Google's cache (google.com/amp/s/...) and strict restrictions, cuts that time to 0.5-1 second, improving Core Web Vitals. For news sites and blogs on Bitrix, AMP boosts LCP by 30-50%. For e-commerce, AMP is suitable only for informational pages — cart and checkout are not supported.
How does AMP affect load speed?
AMP technology accelerates pages by caching on Google CDN and forcibly eliminating blocking JS. In our projects, LCP dropped from 4.2 seconds to 0.8 seconds, and First Contentful Paint to 0.5 seconds. This reduces bounce rates by 20-30% and increases organic traffic by 25%.
How we configure an AMP template (turnkey)?
The process includes four stages:
-
Analytics: audit of current pages planned for AMP conversion. Identify typical components: catalog, detail card, articles, forms.
-
Design: create AMP template, rework CSS (max 75KB), replace JS components with AMP equivalents. Use tagged caching to minimize load.
-
Implementation: HTML/CSS layout with amp-components, integration with information blocks, HL-blocks, Bizproc. Write separate components 2.0 for AMP.
-
Test and deploy: verification via AMP Validator, Google Search Console, A/B speed tests. Deploy to production.
What's included in AMP setup?
| Stage |
Actions |
Result |
| Audit |
Analyze 20+ pages, identify bottlenecks |
Report with recommendations |
| Template |
Create AMP template based on current design |
Responsive template with amp-html tags |
| Components |
Rewrite catalog, article, form components |
Working pages without JS errors |
| Images |
Replace <img> with <amp-img> with size calculation |
Optimized media with layout="responsive" |
| Forms |
Set up amp-form with CORS headers |
Functional callback and subscription forms |
Comparison: normal page vs AMP
| Parameter |
Normal page |
AMP version |
| Load time (LCP) |
3-5 sec |
0.5-1.2 sec |
| CSS size |
200+ KB inline |
up to 75 KB |
| JavaScript |
jQuery, BX.ajax |
amp-components |
| Cache |
no |
Google CDN |
| Form support |
yes (with JS) |
through amp-form |
Why AMP is still relevant for Bitrix?
Despite Google removing AMP lightning from search results, the technology remains useful for SEO. AMP pages are cached on Google CDN, giving speed priority. Additionally, AMP simplifies meeting Core Web Vitals requirements, especially for content-heavy sites. In practice, AMP pages load 2-3 times faster than regular ones, as confirmed by our projects — over 10 successful implementations for news portals and corporate blogs.
AMP validation details
After deployment, each page is verified using the AMP Validator (Google tool). We also track status in Google Search Console under "Accelerated Mobile Pages". Errors are fixed within 24 hours.
Canonical and AMP page relationship
The regular page includes a link to AMP, and the AMP page includes a link to the canonical. Without this pair, Google will not use the AMP page as an accelerated version. Check via Google Search Console → "Accelerated Mobile Pages".
<link rel="amphtml" href="https://example.com/catalog/product/?amp=1">
<link rel="canonical" href="https://example.com/catalog/product/">
Example implementation on Bitrix
AMP page is served via the same URL with ?amp=1 parameter or on a separate subdomain. The first option is simpler — one site template, switching in the prologue:
// /bitrix/templates/ШАБЛОН/header.php
if (!empty($_GET['amp'])) {
define('IS_AMP', true);
// Подключить AMP-шаблон
include __DIR__ . '/amp_header.php';
return;
}
AMP requires a specific <html ⚡> or <html amp> and a set of mandatory tags:
<!doctype html>
<html ⚡ lang="ru">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
<link rel="canonical" href="<?= $canonicalUrl ?>">
<script async src="https://cdn.ampproject.org/v0.js"></script>
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both}...</style>
<noscript><style amp-boilerplate>body{-webkit-animation:none}</style></noscript>
<style amp-custom>
/* Весь CSS страницы — не более 75KB */
</style>
</head>
Images and media via amp-img. In AMP, you cannot use the <img> tag — only <amp-img>. Attributes width and height are mandatory. In the catalog.element template for AMP:
$img = \CFile::GetFileArray($arResult['DETAIL_PICTURE']);
$w = $img['WIDTH'] ?: 800;
$h = $img['HEIGHT'] ?: 800;
?>
<amp-img src="<?= absoluteImageUrl($img['SRC']) ?>"
width="<?= $w ?>" height="<?= $h ?>"
alt="<?= htmlspecialcharsEx($arResult['NAME']) ?>"
layout="responsive">
</amp-img>
Forms in AMP. Standard Bitrix forms (JS submission, AJAX) do not work in AMP. For a callback or subscription form, you need amp-form:
<script async custom-element="amp-form"
src="https://cdn.ampproject.org/v0/amp-form-0.1.js"></script>
<form method="POST" action="/local/ajax/amp-subscribe.php"
action-xhr="/local/ajax/amp-subscribe.php">
<input type="email" name="email" placeholder="Email" required>
<button type="submit">Subscribe</button>
<div submit-success><template type="amp-mustache">Thank you!</template></div>
<div submit-error>Error, try again</div>
</form>
The handler /local/ajax/amp-subscribe.php must return JSON with required fields and set CORS headers for the ampproject.org domain.
Timeline and cost
AMP setup timeline depends on page volume and integration complexity. Expect a range from 5 days for a typical blog to 3 weeks for a catalog with 1C and 54-FZ. Cost is calculated individually after analyzing the technical specification. Savings on mobile development can reach 40% compared to adaptive version. AMP investment pays back within 3-4 months through improved SEO and higher mobile conversion. Get a consultation on AMP setup — contact us. Order an AMP compatibility audit for your site.
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.
