Automated media file optimization for 1C-Bitrix

A catalog page loads 40 product images totaling 8 MB. Google PageSpeed flags errors: "Serve images in next-gen formats" and "Properly size images." Bitrix stores originals in /upload/ and creates resized versions via CFile::ResizeImageGet() — but the format remains JPEG/PNG, without automatic WebP conversion. The result is slow loading and lost search rankings. Unoptimized images add 50–100 KB of traffic each. On a page with 40 products, that's 2–4 MB just for images. Search engines consider speed, especially on mobile: a slow site loses up to 20% of conversions. Comprehensive optimization — lossless compression, WebP, lazy loading — reduces page weight by 2–3 times and improves rankings.

We configure end-to-end multi-level optimization: resize, compression, WebP, lazy loading, and CDN delivery. With over 7 years of Bitrix development experience, we guarantee results. We've optimized images for 50+ projects, achieving PageSpeed improvements of 20+ points. Typical savings range from $500 to $2000 per month in bandwidth costs. Get your project evaluated — contact us for a free speed audit.

Impact of image optimization on Bitrix performance

Each unoptimized image adds 50–100 KB of traffic. On a catalog page with 40 items, that's 2–4 MB just for images. Search engines account for load speed, especially on mobile. A slow site loses up to 20% of conversions. Comprehensive optimization — lossless compression, WebP, lazy loading — reduces page weight by 2–3 times and lifts rankings. Compared to JPEG, WebP achieves 25–35% better compression, making it 1.3–1.5 times more efficient. Lazy loading reduces page load time by up to 40% compared to loading all images immediately.

Step-by-step plan for automatic optimization setup

1. Audit current state: measure PageSpeed, analyze file structure in /upload/, estimate volume and formats.
2. Compression on upload: implement OnAfterFileSave handler with ImageOptimizer::compress(). Limit side to 2000px, quality 85% JPEG / 9 PNG, strip EXIF.
3. WebP conversion: set up OnAfterGetResizeImagePath handler to generate WebP copies. Configure Nginx to serve WebP based on Accept.
4. Lazy loading and srcset: modify catalog component templates — add loading="lazy", srcset for responsive resolutions.
5. Mass processing of existing files: run an agent that processes 100 files per step.
6. Testing and monitoring: re-measure PageSpeed, verify WebP delivery, check cache compatibility.

Level 1: resize and compression on upload

The default CFile::ResizeImageGet() creates resized versions on first request and caches them in /upload/resize_cache/. The main problem is that originals are stored uncompressed, and managers upload 5–10 MB photos from their phones. We add an OnAfterFileSave event handler that compresses the file immediately after upload.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'main',
    'OnAfterFileSave',
    function (\Bitrix\Main\Event $event) {
        $file = $event->getParameter('FILE');

        if (!in_array($file['CONTENT_TYPE'], ['image/jpeg', 'image/png', 'image/gif'])) {
            return;
        }

        $path = $_SERVER['DOCUMENT_ROOT'] . $file['SRC'];
        if (!file_exists($path)) {
            return;
        }

        \Local\Media\ImageOptimizer::compress($path, $file['CONTENT_TYPE']);
    }
);

The ImageOptimizer class uses Imagick if available, otherwise GD. It strips EXIF, limits the maximum side to 2000px, and sets quality to 85% for JPEG or compression level 9 for PNG. After compression, the original takes about 30% of its original size on average. To process already uploaded files, we run a mass agent that iterates through 100 files per step.

How to set up WebP conversion in Bitrix?

WebP provides a 25–35% size reduction compared to JPEG at comparable quality. Browser support is 97%+ (all modern ones). Strategy: generate a WebP version alongside the original via the OnAfterGetResizeImagePath event, then let Nginx serve WebP to browsers that support the format.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'main',
    'OnAfterGetResizeImagePath',
    function (\Bitrix\Main\Event $event) {
        $result = $event->getParameter('RESULT');
        $src = $result['src'] ?? '';

        if (!$src || !preg_match('/\.(jpg|jpeg|png)$/i', $src)) {
            return;
        }

        $localPath = $_SERVER['DOCUMENT_ROOT'] . $src;
        $webpPath  = preg_replace('/\.(jpg|jpeg|png)$/i', '.webp', $localPath);

        if (!file_exists($webpPath) && file_exists($localPath)) {
            \Local\Media\WebpConverter::convert($localPath, $webpPath);
        }
    }
);

map $http_accept $webp_suffix {
    default "";
    "~*webp" ".webp";
}

server {
    location ~* ^(/upload/resize_cache/.+)\.(jpg|jpeg|png)$ {
        set $img_path $1.$2;
        set $webp_path $1.webp;

        if ($webp_suffix = ".webp") {
            add_header Vary Accept;
            try_files $webp_path $img_path =404;
        }

        try_files $img_path =404;
        expires 30d;
        add_header Cache-Control "public, immutable";
    }
}

Why is lazy loading critical for SEO?

Lazy loading defers loading of off-screen images, reducing time to interactive. In the catalog component template, we add loading="lazy" and srcset for responsive resolutions.

<?php
$img  = \CFile::ResizeImageGet($element['PREVIEW_PICTURE'], ['width' => 300, 'height' => 300]);
$img2 = \CFile::ResizeImageGet($element['PREVIEW_PICTURE'], ['width' => 600, 'height' => 600]);
?>
<img
    src="<?= htmlspecialchars($img['src']) ?>"
    srcset="<?= htmlspecialchars($img['src']) ?> 300w, <?= htmlspecialchars($img2['src']) ?> 600w"
    sizes="(max-width: 768px) 300px, 600px"
    loading="lazy"
    width="300"
    height="300"
    alt="Automated image compression and WebP optimization for 1C-Bitrix"
>

Image format comparison

Automatic conversion to WebP offers the best balance of compatibility and size savings. We use quality 82% (visually lossless). Proper image cache configuration ensures that optimized versions are served quickly. For mass upload optimization, our agent processes files in batches. Bitrix agent optimization reduces server load during bulk operations.

Common optimization issues

If WebP is not served, check the Accept header or Nginx location. EXIF data can be preserved if needed by disabling stripping in the optimizer. Lazy loading requires explicit width and height to prevent layout shifts.

What's included in media file optimization setup

• Compression on upload: OnAfterFileSave handler, EXIF removal, resize to 2000px, JPEG quality 85% / PNG compression level 9.
• WebP conversion: OnAfterGetResizeImagePath event + Nginx configuration for WebP delivery.
• Lazy loading and srcset: modification of catalog component templates.
• Mass optimization of existing files: agent with 100-file step.
• Testing: PageSpeed measurement, WebP delivery verification, cache compatibility check.
• Documentation: description of all changes, settings for support.

How long does the setup take?

• Basic package (compression + WebP + lazy loading) — 1–2 business days.
• Mass optimization of existing files — additional 4–8 hours.
• Integration with CDN or additional formats (AVIF) — discussed separately.

We guarantee completion within agreed timelines. Order the setup — we'll evaluate your project for free and propose the optimal solution. Contact us for a consultation and get up to 60% traffic savings.

80% of Bitrix sites slow down due to one table

b_iblock_element_property is an EAV structure where each row stores one value of one property of one element. A catalog of 50,000 products with 30 properties yields 1.5 million rows. The smart filter performs a JOIN of this table with b_iblock_element on five properties, and MySQL performs a full table scan for 3–5 seconds. Our experience shows that without intervention in this table, site acceleration is impossible. We take on projects where load time has dropped to 8–10 seconds and bring TTFB back to <200 ms within 1–2 weeks. Site speed optimization begins with an audit of slow queries and ends with a comprehensive turnkey infrastructure overhaul.

Contact us for an audit — we will identify bottlenecks within 2 hours and propose a concrete plan.

How to achieve TTFB below 200 ms?

Server optimization is the first step. Nginx configuration goes beyond simple gzip. Specifically:

• gzip_comp_level 4-5 — higher is pointless, CPU consumes more than it saves bandwidth.
• brotli on with brotli_static on for precompressed files.
• HTTP/2 with http2_max_concurrent_streams 128.
• fastcgi_cache for PHP responses — caching at Nginx level, bypassing PHP-FPM entirely.
• worker_processes auto, worker_connections according to the number of simultaneous connections.

PHP-FPM tuning: choose between pm = dynamic and pm = static. Static mode works best for dedicated servers with predictable load because it avoids forking overhead. Dynamic saves RAM under low traffic. Calculate pm.max_children as (available RAM - RAM for MySQL/Redis) / average process consumption. For OPcache set memory_consumption=256, max_accelerated_files=20000, and validate_timestamps=0 in production (restart PHP-FPM on deploy).

MySQL/MariaDB: the main bottleneck is almost always the database. Enable slow_query_log with a threshold of 0.5 sec and analyze every query via EXPLAIN. Set innodb_buffer_pool_size to 70–80% of available RAM on a dedicated server. Create composite indexes for faceted search: (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) on b_iblock_element_property. Run OPTIMIZE TABLE b_iblock_element_property after mass operations.

How to configure three-level caching?

Managed component cache. Set TTL individually for each component. Catalog — 3600 sec, news feed — 300 sec, banners — 86400. The same TTL everywhere guarantees either outdated data or useless cache.

Composite cache. The bitrix:composite technology lets Nginx serve ready HTML from a file; PHP is not executed. Dynamic zones (cart, authorization) are loaded via AJAX request through CBitrixComponent::setFrameMode(true). TTFB drops below 50 ms. However, not all components are compatible; $APPLICATION->ShowPanel() and direct output via echo break the composite. We check every page through the panel 'Performance → Composite Site'. According to Bitrix official documentation on composite cache, this is the most effective caching method for high‑load projects.

Comparison: composite cache is 10–20 times faster than managed cache in time to first byte.

Memcached / Redis. Transfer cache from the file system: sessions go to Redis (session.save_handler = redis) — 10–50 times faster than files, plus cluster support. Component cache goes to Memcached via .settings.php: 'cache' => ['type' => 'memcache']. Also enable ORM query cache so identical GetList() calls don't hit MySQL on every request.

What is the fastest way to optimize Bitrix database?

Default MySQL settings are insufficient. Indexes — composite for faceted search, covering for frequent queries. MySQL responds from the index without accessing the data. Partial indexes (MariaDB) for filtering by ACTIVE = 'Y'. Audit unused indexes — each slows down INSERT/UPDATE.

Partitioning. For tables with millions of rows: b_stat_session, b_search_content_stem, and highload-blocks with history. Partition by date — a query for 'orders in a month' does not scan three years of data. Partitioning also solves the problem of concurrent queries during exchange with 1С via CommerceML.

Real case: a catalog of 200,000 products, 50 properties. Filtering by 10 properties took 12 seconds. After creating composite indexes on (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) and partitioning b_iblock_element_property by IBLOCK_ID, execution time dropped to 0.3 seconds. MySQL load decreased by 40 times.

Cleanup. Over a year or two, any database accumulates: outdated search index, expired records in b_cache_tag, history in b_iblock_element_prop_s*, logs in b_event_log taking gigabytes. We set up regular cleanup via agents.

Frontend and CDN

Images account for 60–80% of page weight. Convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + conversion. Use srcset + sizes — never load a 3000px image into a 400px block. Add loading="lazy" for everything below the fold. AVIF offers another 20–30% savings vs WebP.

CSS/JS optimization: use the built-in Bitrix module to merge and minify via 'Settings → CSS/JS Optimization'. Apply PurgeCSS / UnCSS — in a typical Bitrix project, 60–70% of CSS is unused. Use defer / async for non‑critical JS and inline critical CSS in <head> for instant FCP.

Fonts: add <link rel="preload" as="font" crossorigin> for the main font. Set font-display: swap — text visible immediately. Subset via pyftsubset — keep only Cyrillic + Latin, file size reduces by 3–5 times.

CDN: Cloudflare, BunnyCDN, AWS CloudFront, or Russian providers (Selectel CDN, VK Cloud CDN). Serve static assets (CSS, JS, images, fonts) via CDN with Cache-Control: public, max-age=31536000, immutable for files with a hash. Use on‑the‑fly image optimization (imgproxy, Cloudflare Polish) without load on origin.

Why is load testing necessary?

Not synthetic benchmarks, but real scenarios: k6 / wrk to simulate routes — catalog → filtering → product card → cart → checkout. Measure RPS, response time (p50, p95, p99), error rate. Use Xdebug (callgrind) or Blackfire for PHP profiling to find bottlenecks. The test result gives an objective picture of where it actually slows down, not where it 'seems'. After optimization, run again to record improvements.

Results

What is included in the work?

1. Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
2. Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
3. Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
4. Database work — index creation, partitioning, cleanup, EAV table reorganization.
5. Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
6. CDN — connection, caching rule setup.
7. Load testing — real user scenarios, metric report.
8. Documentation — description of all changes, recommendations for further maintenance.
9. Guarantee — support for 1 month after delivery, ensuring all optimizations are stable.

Monitoring

Without monitoring, everything degrades in six months. A new module, uncleared logs, a template change — and speed returns to original. Use web-vitals API for Real User Monitoring from actual visitors. Set up synthetic monitoring with Pingdom or UptimeRobot for regular checks from different locations. Configure alerts — TTFB > 500 ms or LCP > 3 sec triggers notification.

Timelines and cost

Cost is calculated individually after the audit. Get a consultation for your project — we will evaluate the current state and propose an acceleration plan with specific timelines and budget. We are a team with 12+ years of experience in Bitrix, having completed over 300 site speed optimization projects. Contact us to start the performance audit today.