I am wondering, why is my Domain taking long time to load?
As per Gtmetrix timeline, first domain name propagation takes up to 953ms:

Blocking - 53 ms
Waiting - 843 ms
Receiving - 57 ms

Sometimes its takes up to even 2 seconds.

Below is response from Header:

Server              Apache/2.2
Vary                Accept-Encoding
Cache-Control       no-cache
Content-Type        text/html; charset=utf-8
Content-Encoding    gzip
Date                Wed, 22 Jan 2014 02:45:14 GMT
Pragma              no-cache
Connection          Keep-Alive
Set-Cookie          X-Mapping-alncmkhk=EDDD5D603AF7261BACF2EBF3FC8185A8; path=/
ed2f1641e2a81373908380a3799b0d29=59n2seqdchc1j6lvl48lepevg0; path=/
Content-Length      7806

Request Headers    
Host                www.mycarhelpline.com
User-Agent          Mozilla/5.0 (X11; Linux i686 on x86_64; rv:25.0) Gecko/20100101 Firefox/25.0
Accept              text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language     en-US,en;q=0.5
Accept-Encoding     gzip, deflate
Connection          keep-alive

Any advice - what to do correctly to decrease this substantially by over 90%?

  • What kind of page is this? Should it always be 'fresh'? If not I recommend enabling caching. This can easily be set in your htaccess
    – S..
    Jan 22, 2014 at 8:22
  • Hello Sam - Thanks - okay i have enabled Cache and there's a substantial improvement. However site is build on joomla and when enabled system cache plugin - the new entries which are now been added are not shown in front-end of the site. Guess - the cache page is been shown. How much time will it take to show new entries. Jan 22, 2014 at 18:36
  • It depends on your caching plugin, there are many and I'm not familiar with Joomlas caching plugins. I recommend you start a new question along the lines of "How can I optimise a Joomla website to be faster". As a pointer, use a caching plugin with options for the home page that allow you not to cache it, or cache it but have it updated each time a page is saved. Shared hosting will always be slow due to available resources being split between websites. Googles page speed test will give you hints for client side optimisation. By Caching I actually met client side: no-cache Connection
    – S..
    Jan 22, 2014 at 19:08
  • The site mycarhelpline.com needs caching turned off for the actual pages as they need to be up to date to show the latest changes. The images, stylesheets and javascript should be cached - but they are not the cause of the initial delays
    – Geezer68
    Jan 22, 2014 at 21:09

1 Answer 1


The Waiting time is the big problem here. This is the time your web server takes to generate the HTML page once it has received the request. Long waiting times are generally a result of the server needing to do a lot of processing to create the page - for example fetching information from a database or from an external web service.

EDIT: You need to find out whether the delays are caused by plugins or are due to your hosting company. You should put your police detective hat on and do some investigating:) Start by creating a very basic page and taking the timings for it to load. Then add plugins and turn on features one at a time until you discover what is taking so much time. If a very simple page with no plugins enabled is taking way too long then you may need to change your web hosting company. You can use the developer tools (press F12) in modern browsers to get the loading times shown in a Network tab, and it is the Waiting time for the very first request of each page that you need to inspect.

I'm guessing that the "Ask A Question Forum" section pulls its data from somewhere every time the page is requested and this is causing the delay. If so you will need to find ways to optimize the time this takes and/or to use some kind of caching strategy. Personally I would get the server to grab the necessary data in the background at maybe 5 minute intervals and store it in memory. Then when the server needs to generate the page it can just include the data from memory which is super mega quick. You may be able to get the server to update this cached data every time the forum is updated so its available almost instantly.

If you are calling a database then I would also spend some time optimizing the queries used - proper indexing can make a massive speed difference. Also if your database is at a different location to your web server then you will have extra delays from sending/receiving data between the two. This makes it even more important to only read from the database when you really need to. Also only fetch the exact data you need - make sure you are not bringing back every record and every column in that record, the query results should only contain the minimum information that you need.

  • The waiting time is not just the time it takes for their code (page to execute), but the time to it also. If on cheap shared hosting for example, there may be a delay before a page request can be processed due to lots of other websites requests.
    – S..
    Jan 22, 2014 at 8:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.