Media Website on 1C-Bitrix: Architecture, Development, Optimization

Developing a media website on 1C-Bitrix is one of the most demanding areas in web development. Our company has over 10 years of Bitrix expertise and more than 50 completed media projects, delivering robust solutions. Thousands of daily publications, millions of page views during peak hours, dozens of editors working simultaneously. In one project, we encountered a situation: during the morning news feed launch, the server crashed due to unoptimized infoblock queries, and editors waited 30 seconds to save an article. The audit revealed that caching was not configured, and database queries were unindexed. To avoid this, a solid architecture from the start is essential. We offer a proven solution: proper data structure, composite cache configuration, and CDN integration.

Our expertise in media website development on 1C-Bitrix for news portals ensures optimal composite cache configuration. Typical development cost for a high-load news portal ranges from $20,000 to $50,000 depending on features. With over 10 years of Bitrix expertise and more than 50 completed media projects, we have developed solution patterns for high-traffic news portals. Composite cache, CDN, tagged caching, and a properly configured editorial workflow are the basics without which a media site cannot survive. Our certified engineers know how to extract maximum performance from the platform. Infrastructure optimization can reduce server costs by up to 40% (from $2000 to $1200 per month on average), and proper caching can lower load times to 10 ms—a 95% improvement over typical 200 ms.

Composite cache delivers static content directly via nginx without loading PHP. This is a key performance element for media sites. AMP pages load 4x faster than standard mobile pages, significantly improving user engagement and SEO.

Why Bitrix for News Portals

The platform handles high load effectively when configured correctly. The composite cache serves static content bypassing PHP, CDN offloads the server, and tagged cache is automatically cleared when a new post is published. It supports REST API for integration with external services and business processes for content versioning. In comparison, a generic PHP site may serve pages in 200-500 ms, while Bitrix with composite cache achieves 10-30 ms — up to 20x faster.

How We Design Content Architecture

The foundation is infoblocks with a well-thought-out structure.

The main infoblock "Publications" contains all materials: news, articles, interviews, reports. The material type is a dictionary property, not a separate infoblock, so the common content stream can be displayed on the main page without merging multiple sources.

Categories are infoblock sections (politics, economy, society, sports, culture, technology). Nesting is single-level — deep trees complicate navigation and dilute SEO.

Tags are a multiple property linked to a Highload block of tags. This normalizes tags (avoids duplicates), stores SEO descriptions, and tracks popularity.

Special projects have a separate infoblock with a link to publications via the "Related materials" property. Authors are a Highload block with fields: name, photo, position, bio, social media links.

How to Set Up an Editorial Workflow

In a newsroom, 3–5 people work on a single piece: correspondent, editor, managing editor, proofreader, photo editor. The workflow is built on infoblock statuses and user group permissions.

Statuses: draft, under editing, under proofreading, ready for publication, published, unpublished. Access rights are configured for groups: correspondents (create, change to "Under editing"), section editors (edit all in their section), managing editors (publish), editor-in-chief (full access).

Notifications via the OnAfterIBlockElementUpdate event handler — email or Telegram bot. Versioning is enabled through infoblock business processes. This guarantees transparency of every change.

RSS, AMP, Turbo Pages

RSS — the rss.out component with a configurable number of items (50–100 latest), separate feeds for each category.

Yandex Turbo pages are generated via a dedicated RSS channel with XSLT transformation and turbo:content. AMP (Accelerated Mobile Pages) — via an alternative site template under the /amp/ prefix. The AMP template uses amp-img, amp-video, amp-carousel, and forms via amp-form.

Advertising Blocks

The Bitrix advertising module works for simple rotation, but for a large media site we integrate Google Ad Manager via the gpt.js tag. Containers are placed with lazy-loading — this improves Core Web Vitals. Native advertising is a separate infoblock section labeled "Partner Material" in compliance with advertising regulations.

Performance Under High Load

A news portal with millions of page views per day requires a different infrastructure. Composite cache delivers static content directly via nginx — response time drops to 10–30 ms. Configuration: enable it in the admin panel, exclude pages with POST forms and personalization.

How to Configure Composite Cache in 4 Steps

1. Enable composite cache in the admin section: "Settings" → "Performance" → "Composite mode".
2. Set exclusions: for pages with forms, cart, personal account use the EXCLUDE_BY_GET and EXCLUDE_BY_POST parameters.
3. Set caching time: for news lists 5 minutes, for the main page 60 seconds.
4. Verify operation via browser inspector: the response should contain the X-Bitrix-Composite: ok header.

More about composite cache: Composite cache splits the page into static (HTML) and dynamic fragments (AJAX). Static content is served by nginx without loading PHP. Tagged cache is automatically cleared when a new post is added. This is the foundation of fast loading.

CDN — static files (CSS, JS, images) are served via CDN with a 30-day TTL. Component caching: for news lists CACHE_TIME = 5 minutes, for the main page — 60 seconds, for archives — 24 hours.

Server architecture: Nginx, PHP-FPM, MySQL/MariaDB with master-slave replication, Memcached or Redis (preferred), Elasticsearch for full-text search. Monitoring: Bitrix Performance module, Grafana + Prometheus, Sentry.

Comparison: Built-in Search vs Elasticsearch

What's Included in the Work?

Stages of News Portal Development

Total duration — from 20 weeks. Content migration often turns out to be the most unpredictable stage: the old CMS may store data in non-standard formats, and redirects from old URLs are critical for preserving search traffic.

Get a consultation — we'll assess your project and propose the optimal architecture. Contact us to discuss details. Order news portal development with a quality guarantee.

How to properly design infoblocks?

When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.

Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.

Why 1C-Bitrix outperforms most CMS for business

The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.

What highload blocks are and how they speed up the catalog

Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.

From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.

What integrations are critical for 1C-Bitrix stores

Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.

What's included in 1C-Bitrix website development

Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.

• Technical specification – user stories, infoblock diagrams, integration schemas.
• Source code in Git – with commit history, release tags, branching rules.
• Administrative documentation – description of custom components, deployment instructions, list of agents and events.
• Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
• Access to staging during development – test before production deployment.
• Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).

Our process and technologies

Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.

Process:

1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
2. Design – UI/UX with design system. Components are reusable.
3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
5. Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.

Multilingual support and redesign

Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.

Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.

Guarantee and support

We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.