I have a website http://www.masterclean.com/ and some problems in its load speed. any one can guide how to improve its load speed.
Its a cleaning services website from London.

There are many different things that can affect response time from a website. Primarily these are Internet connection, content, internet congestion, and physical distance.

It is also possible that while one person gets a slow load on a site, someone else may not.

Internet connection: Anything on a traceroute that shows something other then a solid connection to a router (or hop) can cause issues with your connection at any point in the data transfer. 

Content: Lots of images, large images, video, lots of general content on a single page. Sometimes to speed up response time, it is better to split content among multiple pages then to have lots of content on a single page.  Having your website load content from other websites can reduce your sites response times.

Internet Congestion: This can be anything from the number of users who are using the same route you are using, routers along the way having issues (each hop on a traceroute is a separate router the data goes through) to other factors such as viruses that are running on the internet. Best analogy is a highway system. You can be the only one on a highway, and get 60mph, however if you hit traffic, you get slowed down. You can get an idea of how the internet traffic is moving as a whole by going to http://www.internettrafficreport.com/

Physical distance: Physical distance from the server hosting a web page is another factor. For example, if you are in Florida or New York you are as far as you can get (while being in the US) from the server. The further you are away, the more systems you the data is having to go through before it reaches the server. This can cause some delays in response time.   (This is one reason why one person can get a slow load, but someone else wont)

Generally, you need to keep in mind the following when determining download speed:

1. location of yourself in relation to the server.
2. location of yourself to nearest ISP hub
3. # of other customers on that hub on at the same time.
4. # of hops between yourself and the server.
5. processor, and Harddrive speeds of your local computer system (minor in most cases, however there very noticeable differences can occur between a Pentium II 350MHz/256 SDRAM and a Pentium 4 2.8GHz/1Gb DDR in relation to download speeds obtained)
6. processes running on the system at the same time.


What would be recommended, is to review your site over a 72 hour period, do traceroutes to the server when you are experiencing slowdowns and when you are not, and then compare the two to see if there are any differences.

Meaning... you send over a large image file, and let HTML scale it down to a smaller size. By itself, it's probably not doing any major damage to your load speed, but in general, you should scale down images ahead of time and only send over what you need (if that's the largest version of that image you'll use). If you use two sizes of an image (say, a thumbnail that's always displayed, and a full size image displayed on demand), consider sending separate files at the proper size.

1) faster transmission of smaller image files
2) the browser doesn't have to spend time resizing the image for you (faster display)
3) the reduced size image will probably be of higher quality if you do it yourself using Photoshop or GIMP

By the way, same comments apply to your logo in the upper left (the raw image file is larger than it needs to be).

One other option is the YSlow firefox addon that will evaluate a site's speed and provide a report.  You can download and install it here @ https://addons.mozilla.org/en-US/firefox/search/?q=YSlow&cat=all&x=0&y=0.  Hope this helps.

Where did you hear that from?

I try to keep track of what google is doing when it comes to rankings, although its hard they change so much, but havent seen/found anything on that.

It is widely accepted that fast-loading pages improve the user experience. In recent years, many sites have started using AJAX techniques to reduce latency. Rather than round-trip through the server retrieving a completely new page with every click, often the browser can either alter the layout of the page instantly or fetch a small amount of HTML, XML, or javascript from the server and alter the existing page. In either case, this significantly decreases the amount of time between a user click and the browser finishing rendering the new content.

However, for many sites that reference dozens of external objects, the majority of the page load time is spent in separate HTTP requests for images, javascript, and stylesheets. AJAX probably could help, but speeding up or eliminating these separate HTTP requests might help more, yet there isn't a common body of knowledge about how to do so.

While working on optimizing page load times for a high-profile AJAX application, I had a chance to investigate how much I could reduce latency due to external objects. Specifically, I looked into how the HTTP client implementation in common browsers and characteristics of common Internet connections affect page load time for pages with many small objects.
For further info on the topic please visit: http://www.die.net/musings/page_load_time/ and
Free Website Performance Tool and Web Page Speed Analysis: http://www.websiteoptimization.com/services/analyze/