Lỗi unable to please try again after some time năm 2024
The Department of Home Affairs acknowledges the Traditional Custodians of Country throughout Australia and their continuing connection to land, sea and community. We pay our respects to all Aboriginal and Torres Strait Islander peoples, their cultures and to their Elders past and present. Show
Artwork: Protecting Country and People | Luke Penrith, July 2022
From time to time, you might encounter the ‘website took too long to respond’ error when you try to access a particular website. The following images show how the error looks like on Chrome and Firefox respectively: Chrome: Firefox: When trying to access your own site is very concerning, as it shows the site could effectively be down for all users. read on about some common causes, and how to troubleshoot. What does this error mean?The ‘taking too long to respond’ error indicates that there is a communication problem between the target server and the client (your web browser). It means that the targeted server is taking a long time to send a response to the client. The error is usually sent if the client cannot get a response within 30 seconds. The connection attempt is then terminated. What causes the ‘taking too long to respond’ error?Here are several reasons why your browser takes a long time to load: Internet connection problemsA particular website may fail to load if you do not have an internet connection. Check that your device is connected, for example, via a LAN or Wi-Fi. If you use a LAN, you need to check your LAN settings. You also need to make sure that your TCP/ipv4 protocols are correctly configured. We will look at how to fix internet connection problems later on in the article. Your server is overwhelmedIf you are using shared hosting, there is a possibility that there is not enough memory to allow for a connection between your client and server. When using shared hosting, memory allocation is not equally distributed. There might be sites that use a lot of memory, leaving others with little memory available. Talk to your service provider about your memory limit. If you are using Wordpress, you can check your memory limit in the ‘Site Health Tool’ on your dashboard. You may also want to change your hosting plan to a VPS (Virtual Private Server) package, where memory is shared equally among users. There are also other reasons that may cause your site to be overwhelmed, for example, spikes in site traffic, or code and scripts that have not been deferred to load only after your site fully loads. Your antivirus is blocking site accessYour antivirus might block access to some sites or even all of them. You may need to temporarily disable it and see whether the ‘taking too long’ error is resolved. DNS cacheThe DNS (Domain Name System) is what translates domain names to IP addresses. This is because it is easier for browsers to ‘read’ IP addresses (which are made up of 4 sets of digits separated by a period as in the image below), while it is easier for humans to remember text, which is why domain names are made up of text as in www.abc.com DNS results are usually cached in order to make sure that subsequent requests are handled faster. If there was a communication problem between client and server, it may be cached, resulting in the ‘website took too long to respond’ error. Flushing the DNS cache should solve the error. Outdated extensionsExtensions come in handy to add necessary features to help improve your browser’s functionality. However, they may not be as frequently updated for compatibility with web browsers. Outdated extensions may contribute to communication problems between client and server. You also cannot be sure that the extensions will work as intended. On Chrome, virus scanning extensions, for example, Symantec, outdated or not, tend to be ‘heavy’, which slows down your browser. Browsing historyStored data from browsing sessions (saved passwords, cookies, site names, and URLs, as well as cache) can contribute to client-server communication problems. The stored data contains the name and URL of the particular site that you are trying to access. If it had connection issues before, it will refer to the browser history and the client-server connection will fail. Chrome’s default profile folder issuesThere is a folder named ‘Default’ on your local machine which store’s your ‘Chrome Profile’ (your bookmarks, saved passwords, apps, browser settings, and extensions). If there is corrupted content in the folder, it may affect communication between client and server. You may need to edit or rename this file in order to fix ‘taking too long’ issues. The issues that may result in a corrupted default folder include corrupt files that are locally stored in the cache folder or interference from a 3rd party antivirus. Windows hosts fileThe hosts file is what maps domains to IP addresses. If you want to see for example how your site would look if you hosted on a different server, you would need to edit the hosts file. If you have blocked website URLs or IP addresses in your hosts file, they might cause other sites to be blocked too, resulting in the page taking too long to load error. The network adapter is not installed or is out of dateDrivers are necessary for seamless communication between software and hardware. If your network driver is not up to date, or if your device does not have one, it may result in broken client-server communication. Your browser contains corrupted filesYour browser may contain corrupted files. These can affect how the client communicates with the browser. Reinstalling the web browser might solve this problem. Theme incompatibilityIf you are using Wordpress, your theme incompatibility issues could be the reason for the ‘taking too long to respond’ error. The only way to know whether it is your theme that is causing the issues is to change it to a default theme. If the error gets fixed, then you need to reinstall your theme or revert to the latest backup of your site that you have. Too much data in your databaseIf your database contains a lot of data, for example, logs, hundreds or thousands of blog posts, gallery pictures, and entries from themes and plugins, your site may take too long to retrieve all that data from your site. Hardware accelerationHardware acceleration refers to when tasks are ‘redirected’ to hardware that is specialized to handle them. An example is sound cards being used to increase sound quality. By default, the CPU is the hardware designed to handle most tasks on a device. However, other hardware can come in to ‘relieve’ the CPU, allowing faster processing and performance. On a browser, there is a setting called ‘hardware acceleration’ which allows the browser to maximize the usage of your hardware, for example, to load videos and graphics. Enabling hardware acceleration may improve your browser’s performance. This means that the browser will use ‘less CPU’ which in turn will free up more memory for the browser to load your website. On Chrome, hardware acceleration is enabled by default. In order to determine the efficiency of hardware acceleration, you need to check for your browser’s performance when acceleration is enabled and when it is not. If it does not improve your browser performance, then you are better off without it. Connectivity testsAfter encountering the ‘taking too long to load’ error, a great approach is to rule out the most obvious causes, for example, internet connectivity. Check that you do have a functional internet connection and that it works on other sites and devices. The second approach is to run connectivity tests in order to be more precise when fixing the error. While some of these fixes involve running commands from the command line interface, they are simple fixes, and you do not need technical knowledge to implement them. Here are the most common connectivity tests that you can run: NslookupNslookup, ‘name server lookup’ in full, is a tool that you can use to look up your DNS information, for example, your IP addresses, DNS servers that are responding to requests or even compare responses from different DNS servers. If you are using Linux, you can access this tool on the command line. There is also a nslookup online version. PingThis tool allows you to check the availability of a remote server. It helps you check whether your local PC or desktop connects to a remote host. You can easily run the test from your command line. Learn more about how to do a Ping test here. TracertTracert is a tool that traces the route that data packets sent to and from your IP address take, and calculates the amount of time taken. The tracert test helps identify issues that occur during data transfers. An issue that may occur is increased latency. Latency is defined as the time it takes for the client to send a request and receive a response from the server. If you have high latency, you may need to start using a CDN. CDNs (Content Delivery Networks) are distributed servers that decrease the distance of the geographical location of your servers (‘bring your servers nearer’). Instead of having to wait for a response from a server that is in another country, for example, you may have a CDN in your own country. This way, you not only increase your site’s speed but may also solve communication problems between client and server. SEOptimer’s Page Speed ToolSEOptimer has checks built into its website audit tool that tests the responsiveness, and overall load time of your website, in order to get a third-party evaluation of its performance. The server response time is how long it takes for the site to actually respond (if this is very large, this may often directly cause the 'taking too long to respond' issue. You could also use our tool to test your site load time and performance. All you need to do is enter your domain name and get results. If this is very large, this may often directly cause the 'taking too long to respond' issue, and the others give indicators of how slow the site is to load. The “All Page Content Loaded” and “All Page Scripts Complete” will indicate how slow the site is to load itself. Depending on how your site is designed, this could also point to a cause of the ‘took too long to respond issue’. Server response time is how long it takes for the site to actually respond How to fix the website took too long to respond errorAs we mentioned, when it comes to fixing this error, you need to eliminate the most obvious causes first. In this section, we begin by discussing fixes to the most obvious causes of the error, before looking at fixes to the less obvious causes. Check whether you are connected to the internetThe first step that you need to take is to make sure that your device is connected to the internet. To check whether you have a valid internet connection on a wireless network on Windows:
If using LAN, check your settings by:
Test your internet speedOnce you are sure that you have an internet connection, you may want to test the internet speed. If your internet speed is too slow, you may want to try loading the same page using a different provider’s internet. If this solves the problem, then your connection might have a problem. Change devicesTry and access the site using another device. For example, if you are using a PC, you may want to try to access the site on a mobile device. If it works on the other device, then there is a possibility that your device is unable to communicate with the server. After eliminating internet connection issues, it is time to try other fixes. Let’s look at fixes to problems that may arise from your device being unable to communicate with the server. Server troubleshootingThe first step when it comes to identifying server problems is logging in. if the login is slow, it already indicates that there is a problem. You will use the ssh command on your Linux terminal as follows:
You can then use the top utility tool to check CPU usage. You should see something like this: Image source Press 1 to see more details as follows: Image source If us is above the number of CPUs, it means CPU usage is really high, and more CPU horsepower is required. On Windows, you can check the server load for available resources and performance issues. One way to do this is via the Windows Task Manager. To access the windows task manager:
Press Ctrl+Alt+End + Esc while on remote desktop If you have never used it before, you may see the above window. Click ‘more details’ Otherwise, you should see a window with a breakdown of how the server is being used, as in the image below: As you can see, there are different tabs: processes, performance, users, details, and services. Each of these will give you insights into how the server’s resources are being used (processes), and how much uptime the server has been running - uptime (performance). If the uptime is high, then it shows server usage is strained. You then need to find ways to optimize server performance, for example by restarting it (use the sudo reboot command on Linux. On Windows use shutdown / r / t 0 on the command line. DNS server issuesHere, you will carry out a nslookup test. You can use the online version that we mentioned or use your command line on Linux. Here is how to use nslookup on the command line:
Address: 8.8.8.8 53Non-authoritative answer: Name: abc.com Address: 134.170.185.46 Name: abc.com Address: 134.170.188.221 Let’s break it down:
Learn more about DNS server errors and how to fix them from this article. Now that you know the DNS server that is being used, you need to confirm that you do not have IP address conflict or have old DNS information. To do this, release the IP address and renew it. To achieve this on Windows 10:
If all the above does not fix your problem, you may need to contact your network admin or hosting provider so that they can check the server and configuration status of your DNS server. Other fixes:Clear browser cacheTo clear browser cache on Chrome:
Use incognito modeWhen you use incognito mode, your browser does not ‘store’ your activity. To use incognito mode in Chrome:
If you can access your site while it in incognito mode, then you need to check whether your extensions are causing problems. ExtensionsTo disable extensions in Chrome:
Firewall and antivirusTo disable your firewall on Windows 10,
You may also need to uninstall your antivirus if disabling your firewall does not resolve the error. Note that it is not advisable to have your firewall disabled or to have no antivirus on your device. As soon as you resolve the problem, you need to turn firewall on and reinstall your antivirus. Add or update network driversTo access your drivers on Windows:
Hardware accelerationTo turn hardware acceleration on or off in Chrome:
If this approach does not work, you can force it by:
Modifying your ‘hosts’ fileTo modify the hosts file:
Editing the Chrome default profile folderNote that you need to export saved passwords and bookmarks before editing this folder. You could also sync Chrome with a Gmail account. This way, you will get them back as editing this folder resets Chrome, meaning that you will lose all data. To edit the defaults folder:
To fix issues with corrupted files, locate the web data file and delete it. If your site still has a slow response, delete the local State file. Note that this will not result in the loss of any of your data. You can also uninstall any optional tools that come with your antivirus, for example, AVG Toolbar and AVG Secure Search. Do a site clean upYou need to clean out images, posts, and content that you no longer use on your site. These could include posts in drafts, unused images, spam comments, and old user accounts that are no longer in use. You can go a step further and use a plugin like Advanced Database Cleaner to help you clean up your database. Check for plugins and themes that you no longer use too and delete them. Image optimizationYou can also optimize your images using plugins like Jetpack Image CDN, Compress JPEG & PNG Images, and Smush Image Compression and Optimization. It is good to go for a plugin that can optimize images that are currently on your site and those that you will upload later. In conclusionYou now know the options to explore when it comes to fixing ‘website takes too long to respond’ errors. You have an idea of what could be causing the errors, and the areas to check first. |