Common causes of poor performance
Review the complete request chain: browser, network, web server, PHP, Bitrix Framework, cache, database and integrations. High server response time and slow visual rendering are different problems and require different diagnostics.
- Insufficient CPU, memory or disk performance
- Unsupported or inefficient PHP configuration
- Disabled or incorrectly configured caching
- Heavy custom components and repeated SQL queries
- Large catalogues and complex filters
- Unoptimised images, scripts and third-party widgets
- Resource-intensive imports and CRM or 1C integrations
- Accumulated technical debt
What to check first
Measure server response time, inspect resource usage during the slowdown, review the Bitrix performance monitor and browser network waterfall, and compare fast and slow sections. Make changes only after a reproducible bottleneck has been identified.
A safe optimisation sequence
- Create a backup and record baseline metrics.
- Separate backend latency from frontend loading time.
- Find expensive components, requests or scheduled jobs.
- Fix the root cause and validate caching.
- Repeat measurements under comparable conditions.
Will more expensive hosting always solve the problem?
No. Extra resources may hide inefficient code temporarily, but a measured diagnosis is required.
Should database indexes be added immediately?
No. Indexes should be based on actual slow queries and their execution plans.