You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/web_cloud/web_hosting/diagnostic_slownesses/guide.en-asia.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "My website is slow. What to do?"
3
-
excerpt: "Identify the cause of your website's slowdowns and find out how to resolve this situation"
4
-
updated: 2025-11-20
3
+
excerpt: "Identify the cause of your website's slowdowns and find out how to improve this situation"
4
+
updated: 2025-11-17
5
5
---
6
6
7
7
## Objective
@@ -27,7 +27,7 @@ In rare cases, the slow display may also be caused by your Internet service prov
27
27
>
28
28
> Users share the resources of the web hosting infrastructure their websites are using. If one of them overloads the shared infrastructure, this can have consequences for the other hosting services on the same infrastructure.
29
29
>
30
-
> Our shared hosting plans do not have a Service Level Agreement (SLA).
30
+
> Our web hosting plans do not have a Service Level Agreement (SLA).
31
31
>
32
32
> If you need a service with a guaranteed availability rate higher than 99%, we recommend that you consider using a [Virtual Private Server (VPS)](/links/bare-metal/vps) or a [Dedicated Server](/links/bare-metal/bare-metal).
33
33
>
@@ -44,7 +44,7 @@ In rare cases, the slow display may also be caused by your Internet service prov
44
44
> [!warning]
45
45
>
46
46
> OVHcloud provides services that you are responsible for with regard to their configuration and management. It is therefore your responsibility to ensure that they function properly.
47
-
>
47
+
>
48
48
> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist provider](/links/partner) or reach out to the OVHcloud community if you encounter any difficulties. We will not be able to assist you with issues **not caused by the relevant hosting infrastructure itself**. You can find more information in the [Go further](#go-further) section of this guide.
49
49
50
50
> [!success]
@@ -89,13 +89,13 @@ All diagnostics in step 1 must be performed **without exception** to determine w
89
89
90
90
#### 1.1 - Check the status of your OVHcloud services
91
91
92
-
To ensure that your services (shared hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
92
+
To ensure that your services (web hosting **and** database) are not undergoing maintenance or an incident, retrieve the cluster and filer information of your web hosting as well as the general information relating to your database. You can then check their status at [status.ovhcloud.com](https://web-cloud.status-ovhcloud.com/).
93
93
94
-
To find out the cluster and filer where your shared hosting is located, refer to our guide "[Web hosting - How to know your cluster and filer](/pages/web_cloud/web_hosting/how_to_know_cluster_and_filer)".
94
+
To find out the cluster and filer where your web hosting is located, refer to our guide "[Web hosting - How to know your cluster and filer](/pages/web_cloud/web_hosting/how_to_know_cluster_and_filer)".
95
95
96
96
> [!success]
97
97
>
98
-
> If an incident or maintenance is reported on the infrastructure on which your shared hosting is located, wait until they are resolved by our administrators. **No further action is required on your side**.
98
+
> If an incident or maintenance is reported on the infrastructure on which your web hosting is located, wait until they are resolved by our administrators. **No further action is required on your side**.
99
99
>
100
100
> You can subscribe to the incident or maintenance updates with your email address, in order to receive an email notification of the progress of the operations.
101
101
>
@@ -109,7 +109,7 @@ Test your website from another device/computer, then from another Internet acces
109
109
110
110
#### 1.3 - Test the hosting with a file independent from your website
111
111
112
-
Place a file called **phpinfo.php** at the root of your website in the [FTP storage space on your shared hosting](/pages/web_cloud/web_hosting/ftp_connection).
112
+
Place a file called **phpinfo.php** at the root of your website in the [FTP storage space on your web hosting](/pages/web_cloud/web_hosting/ftp_connection).
113
113
114
114
In this file, insert the following code:
115
115
@@ -121,24 +121,26 @@ phpinfo();
121
121
122
122
> [!warning]
123
123
>
124
-
> In some cases, the "**.htaccess**" files in the upstream directories/folders or at the same level as where you placed your "**phpinfo.php**" file may affect the display of the **phpinfo.php** in an Internet browser.
124
+
> In some cases, the **.htaccess** files in the upstream directories/folders or at the same level as where you placed your **phpinfo.php** file may affect the display of the **phpinfo.php** in an Internet browser.
125
125
>
126
-
> Changes to a "**.htaccess**" file may affect your website’s display. Contact a [specialist provider](/links/partner) if you have difficulty in doing the following.
126
+
> Changes to a **.htaccess** file may affect your website’s display. Contact a [specialist provider](/links/partner) if you have difficulty in doing the following.
127
127
>
128
-
> If it does not appear and **only for informed users**, rename your files "**.htaccess**" to "**.htaccess_OLD**" so that the server does not run them for your test. Rename them correctly after your diagnostic.
128
+
> If it does not appear and **only for informed users**, rename your files **.htaccess** to **.htaccess_OLD** so that the server does not run them for your test. Rename them correctly after your diagnostic.
129
129
130
-
**Example**: if your website’s domain name is “domain.tld” and the file “**phpinfo.php**” has been placed in the root directory of your website, you can access it via the following URL: `http://domain.tld/phpinfo.php` (or `https://domain.tld/phpinfo.php`).
130
+
**Example**: if your website’s domain name is “domain.tld” and the file **phpinfo.php** has been placed in the document root folder of your website, you can access it via the following URL: `http://domain.tld/phpinfo.php` (or `https://domain.tld/phpinfo.php`).
131
131
132
132
> [!primary]
133
133
>
134
-
> If the call to the file **phpinfo.php*** displays a **instantly** configuration table, this means that the slowdowns do not come from the shared hosting where your website is located. Otherwise, this file will appear as slowly as your other pages.
134
+
> If the call to the file **phpinfo.php*** displays a configuration table **instantly**, this means that the slowdowns do not come from the web hosting where your website is located. Otherwise, this file will appear as slowly as your other pages.
135
135
>
136
-
> In other words, if the delays are only present on some pages or content of your website, this means that the shared hosting **is not the cause of the delays** encountered on your website.
136
+
> In other words, if the delays are only present on some pages or content of your website, this means that the web hosting **is not the cause of the delays** encountered on your website.
137
137
138
-
#### 1.4 - Test your database connectivity:
138
+
#### 1.4 - Test your database connectivity
139
139
140
140
Log in to your database by following **step 3** in our guide on [web hosting databases](/pages/web_cloud/web_hosting/sql_create_database).
141
141
142
+
If you are using a database of a **Web Cloud Databases** solution, please refer to our guide on [Web Cloud Databases databases](/pages/web_cloud/web_cloud_databases/connecting-to-database-on-database-server).
143
+
142
144
If the connection is successful, you will land on the following interface:
@@ -180,11 +182,11 @@ Below, you will find the actions you need to take to identify the source(s) of t
180
182
181
183
Check the PHP engine, PHP version and runtime environment used on your Web Hosting plan, using our guide to [configuring your Web Hosting plan](/pages/web_cloud/web_hosting/configure_your_web_hosting).
182
184
183
-
If you are using an outdated PHP version on your web hosting plan, the "**PHP CGI**" engine and/or the "**legacy**" environment, and **if your website is compatible**, you should use the "**PHP**" engine (PHP FPM), the "**stable**" environment, or "**stable64**" with the most recent PHP version possible.
185
+
If you are using an outdated PHP version on your web hosting plan, the **PHP CGI** engine and/or the **legacy** environment, and **if your website is compatible**, you should use the **PHP** engine (PHP FPM), the **stable**or **stable64** environment, with the most recent PHP version possible.
184
186
185
-
To compare the available PHP versions depending on the runtime environment you are using, see **Step 2** in the guide on [configuring the PHP version on your hosting system](/pages/web_cloud/web_hosting/configure_your_web_hosting).
187
+
To compare the available PHP versions depending on the runtime environment you are using, see **Step 2** in the guide on [configuring the PHP version on your web hosting](/pages/web_cloud/web_hosting/configure_your_web_hosting).
186
188
187
-
Using a recent PHP version, the "**stable**" or "**stable64**" runtime environment with the "**PHP**" engine (PHP FPM) makes your website much smoother and faster. As a guide, the "**PHP**" engine (PHP FPM) can be up to 50 times more efficient than the "**PHP CGI**" engine to perform its tasks.
189
+
Using a recent PHP version, the **stable** or **stable64** runtime environment with the **PHP** engine (PHP FPM) makes your website much smoother and faster. As a guide, the **PHP** engine (PHP FPM) can be up to 50 times more efficient than the **PHP CGI** engine to perform its tasks.
188
190
189
191
#### 2.2 - Analyse outgoing connections / TCP connections made by your web hosting plan
190
192
@@ -196,8 +198,6 @@ To analyse outgoing connections to your hosting plan, please read its **OUT** lo
196
198
197
199
If you notice that there are a lot of outgoing connections on your hosting, compare your **OUT** logs with your **WEB** logs by using their timestamps. This will help you identify the script(s) responsible for this situation.
198
200
199
-
If you notice that there are a lot of outgoing connections on your hosting, compare your **OUT** logs with your **WEB** logs by using their timestamps. This will help you identify the script(s) responsible for this situation.
200
-
201
201
If you are using a Content Management System (CMS) such as WordPress, Joomla!, PrestaShop or Drupal, identify the plugin(s) and/or theme generating this outgoing connection stream.
202
202
203
203
#### 2.3 - Analyse the flow of HTTP requests made to your web hosting plan
@@ -231,7 +231,7 @@ To reduce the flow of requests each time your pages load, you can also set up a
231
231
>
232
232
> OVHcloud offers several [CDN options](/links/web/hosting-options). If you would like to use or activate one for your web hosting plan, log in to your [OVHcloud Control Panel](/links/manager) then read our guide on [Using the OVHcloud CDN](/pages/web_cloud/web_hosting/cdn_how_to_use_cdn).
0 commit comments