Split the problem: server or browser
A slow site can mean two different things. Either the server takes a long time to build the page and sends the first byte late, or the page arrives quickly but the browser spends ages loading images, fonts and scripts. The fixes differ, so keep the diagnosis separate.
Server response time shows up in the Network tab of your browser's developer tools. For the browser side, use PageSpeed Insights, and for real visitor data, the Core Web Vitals report in Search Console.
Finding what Bitrix spends time on
Bitrix ships with a performance panel that evaluates your server configuration and shows how quickly pages are generated. The second tool is debug mode. Turn it on for a test copy of a page and you will see how much time and how many database queries each component used.
The picture is usually the same: one or two components eat most of the time. It might be the menu, a product list, a related-products block or the filter. Do not guess; find the culprit with numbers and start there.
Caching and composite mode
Standard components have caching parameters. Check that the cache is on and that its lifetime matches how often the content really changes. A catalog updated once a day does not need rebuilding on every visit. Look closely at custom components, which are often written without any cache, so each page view repeats every query.
Composite mode serves visitors a prepared version of the page and loads dynamic parts, such as the cart or the user's name, separately. For catalogs and content sites the gain is noticeable, but the template has to be compatible. Otherwise the cart or prices may display incorrectly, so test it on a copy first.
Heavy catalog queries
Typical sources of delay in Bitrix online stores:
- product selections with no limit on the number of items per page
- counting products in every section on every page view
- filters with many properties and no suitable database indexes
- agents that run on visitor hits instead of cron
- several carousels and product lists on one page
Images, scripts and third-party widgets
Managers often upload product photos straight from a phone or a supplier, and a single file can weigh several megabytes. Set up automatic resizing on upload, show smaller copies in listings, use modern formats and lazy-load everything below the first screen.
Turn on CSS and JS merging and compression, and remove libraries nobody uses. Check third-party items separately: live chat, pixels, counters, installment widgets. Each is small, but together they add seconds. Common finds are jQuery loaded twice by different modules, fonts in five weights when two are used, and a homepage slider with large images that all load at once.
Hosting and server
Bitrix needs resources. A large catalog on cheap shared hosting will almost always be slow, and template tweaks will not change that. Make sure you run a supported PHP version, bytecode cache is enabled, memory is sufficient, and on busy sites the cache is kept in memory. If your audience is mostly in Uzbekistan, consider where the server physically sits or whether a CDN makes sense.
A working order and how to read PageSpeed
A sensible sequence: measure the key templates (home, category, product page, article), find slow components with debug mode, enable cache and composite, optimize images, trim third-party scripts, then measure again. Change one thing at a time, otherwise you will not know what helped.
A PageSpeed score is a lab measurement of a single load. Field data in Core Web Vitals matters more. If the lab score is low but field data is fine, there is no urgency. If it is the other way round, test on slow phones and mobile internet, which is how many of your customers open the site.
If you cannot tell why your site is slow, the markdev team can audit it as part of SEO optimisation in Uzbekistan and locate the bottleneck. Tell us about your task and we will suggest where to start.
FAQ
Does Bitrix website speed affect SEO?
Yes. Speed is part of page experience, which search engines take into account, and it decides whether a visitor waits for the page at all. It does not replace good content and structure, though.
Where should I start speeding up Bitrix?
Start with diagnosis: decide whether the delay is on the server or in the browser, then use debug mode to find the heaviest components. Proper caching often helps the most.
Do I need to rebuild the site to make it faster?
Usually not. The work is mostly caching, image optimization and fixing a couple of heavy spots. A full rebuild is rarely required.
Is composite mode risky?
If the template is not compatible, the cart or prices can show wrongly. Test it on a copy of the site before switching it on in production.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.