When a site is slow, the first thought is usually "bad hosting". Sometimes that is right, but very often the slowness comes from the site itself: uncompressed images, dozens of plugins, heavy database queries on every page, or third-party scripts. Switching plans or providers without knowing which side is at fault wastes time and money. A few simple tests separate the two quite reliably.
Two kinds of slow
Split a page load into two parts. The first is the server response: the time from the request until the first byte arrives, during which the server runs PHP, queries the database and builds the HTML. The second happens in the browser: images, CSS, JavaScript and fonts load and the page renders. If the first part is long, the cause lives on the server or in the site code. If the server answers quickly but the page still feels slow, the issue is almost always front-end and has little to do with hosting.
Compare a static file with a PHP page
A static file such as robots.txt is served without PHP or a database. If even that is slow, the network or server is the problem. If it is fast and the homepage is slow, the time goes into code and queries. curl breaks down each phase:
curl -o /dev/null -s -w "dns: %{time_namelookup} connect: %{time_connect} tls: %{time_appconnect} ttfb: %{time_starttransfer} total: %{time_total}\n" https://example.uz/robots.txt
curl -o /dev/null -s -w "dns: %{time_namelookup} connect: %{time_connect} tls: %{time_appconnect} ttfb: %{time_starttransfer} total: %{time_total}\n" https://example.uz/
Values are in seconds. connect and tls will be similar for both because they depend on the network; the difference shows in ttfb. If robots.txt takes 0.1 s and the homepage 3 s, nearly all of that is PHP and database work. Repeat at different times of day, since one measurement can be a fluke.
See what the browser loads
Press F12 in Chrome or Firefox, open the Network tab and reload without cache. The first row, the HTML document, reflects the server response; the rest often reveal the real culprit: a 4 MB hero banner, dozens of JavaScript files, a chat widget or fonts from a distant server. Lighthouse and PageSpeed Insights help too, but run them several times rather than trusting a single result.
Typical causes inside the site
- Too many or poorly written plugins, especially ones calling external APIs on every page.
- No page cache, so every visit rebuilds the page from scratch.
- Database clutter such as thousands of revisions or expired transients.
- An outdated PHP version; newer releases generally run the same code faster.
Use a diagnostic plugin like Query Monitor, or disable plugins one by one and re-measure ttfb. Tedious, but reliable.
Check the PHP version and OPcache
When the server response is slow, find out which PHP version the site runs and whether OPcache is enabled. OPcache keeps compiled PHP code in memory instead of parsing it on every request, which noticeably cuts response time. Create a temporary file in the site root, open it in the browser and look at the PHP version and the opcache section:
<?php phpinfo();
Delete the file right after checking, because it exposes a lot of server configuration. You can switch the PHP version in the ISPmanager site settings, but confirm the site is compatible first.
Signs the hosting is at fault
If static files are slow too, if slowdowns appear at certain hours and vanish, or if the panel shows you regularly hitting CPU, memory or process limits, the server or plan is short on capacity. Location matters as well: for an audience in Uzbekistan, a local server cuts network latency, especially for users on Tas-IX.
Example: a hotel in Bukhara
The owner of a small Bukhara hotel site complained of 8-second loads and planned to switch hosts. curl showed a 0.4 s server response, while the Network tab revealed six 5 MB photos uploaded straight from a phone into the homepage slider. After compressing them and converting to WebP, the page weight dropped tenfold and the site became fast without changing hosting. If your tests do point at the server, contact support from the sayt.uz cabinet and include your curl results with timestamps.