livemap-small

Your Results:

Download HARShare Result

Performance grade

C

72

Page size

1.6 MB

Load time

8.55 s

Requests

100

Improve page performance

Grade

Suggestion

F0

Make fewer HTTP requests

Decreasing the number of components on a page reduces the number of HTTP requests required to render the page, resulting in faster page loads. Some ways to reduce the number of components include: combine files, combine multiple scripts into one script, combine multiple CSS files into one style sheet, and use CSS Sprites and image maps.

F0

Use cookie-free domains

When the browser requests a static image and sends cookies with the request, the server ignores the cookies. These cookies are unnecessary network traffic. To workaround this problem, make sure that static components are requested with cookie-free requests by creating a subdomain and hosting them there.

F0

Add Expires headers

Web pages are becoming increasingly complex with more scripts, style sheets, images, and Flash on them. A first-time visit to a page may require several HTTP requests to load all the components. By using Expires headers these components become cacheable, which avoids unnecessary HTTP requests on subsequent page views. Expires headers are most often associated with images, but they can and should be used on all page components including scripts, style sheets, and Flash.

D67

Compress components with gzip

Compression reduces response times by reducing the size of the HTTP response. Gzip is the most popular and effective compression method currently available and generally reduces the response size by about 70%. Approximately 90% of today's Internet traffic travels through browsers that claim to support gzip.

B90

Reduce DNS lookups

The Domain Name System (DNS) maps hostnames to IP addresses, just like phonebooks map people's names to their phone numbers. When you type URL www.yahoo.com into the browser, the browser contacts a DNS resolver that returns the server's IP address. DNS has a cost; typically it takes 20 to 120 milliseconds for it to look up the IP address for a hostname. The browser cannot download anything from the host until the lookup completes.

A100

Avoid empty src or href

You may expect a browser to do nothing when it encounters an empty image src. However, it is not the case in most browsers. IE makes a request to the directory in which the page is located; Safari, Chrome, Firefox 3 and earlier make a request to the actual page itself. This behavior could possibly corrupt user data, waste server computing cycles generating a page that will never be viewed, and in the worst case, cripple your servers by sending a large amount of unexpected traffic.

A100

Put JavaScript at bottom

JavaScript scripts block parallel downloads; that is, when a script is downloading, the browser will not start any other downloads. To help the page load faster, move scripts to the bottom of the page if they are deferrable.

Response codes

Response Code

Responses

Indicates that the request has succeeded.

200OK

100

Content size by content type

Content Type

Percent

Size

Script

34.14%

563.2 KB

Image

24.79%

408.9 KB

Font

21.06%

347.4 KB

CSS

18.44%

304.1 KB

HTML

1.53%

25.2 KB

XHR

0.03%

564.0 B

Total

100.00%

1.6 MB

Requests by content type

Content Type

Percent

Requests

Script

39.39%

39

CSS

28.28%

28

Image

22.22%

22

Font

6.06%

6

HTML

3.03%

3

XHR

1.01%

1

Total

100.00%

99

Content size by domain

Content Type

Percent

Size

tcpcs.com.au

94.30%

1.5 MB

assist.zoho.com

1.84%

29.8 KB

www.googletagmanager.com

1.60%

25.8 KB

www.google-analytics.com

1.07%

17.3 KB

fonts.gstatic.com

0.86%

13.9 KB

js.zohostatic.com

0.34%

5.5 KB

fonts.googleapis.com

0.00%

0.0 B

Total

100.00%

1.6 MB

Requests by domain

Content Type

Percent

Requests

tcpcs.com.au

89.00%

89

assist.zoho.com

4.00%

4

fonts.googleapis.com

2.00%

2

www.google-analytics.com

2.00%

2

fonts.gstatic.com

1.00%

1

www.googletagmanager.com

1.00%

1

js.zohostatic.com

1.00%

1

Total

100.00%

100

File requests

Nobody Likes a Slow Website

We built this Website Speed Test to help you analyze your website load speed.

The test is designed to help make your site faster by identifying what about a webpage is fast, slow, too big, and so on.

We have tried to make it useful both for experts and novices alike.
In short, we wanted it to be an easy-to-use tool built to help webmasters and web developers everywhere optimize their website performance.

About Pingdom

Pingdom offers cost-effective and reliable uptime and performance monitoring for your website.

We use more than 70 global polling locations to test and verify our customers' websites 24/7, all year long.

With Pingdom you can monitor your websites' uptime, performance, and interactions for a better end-user-experience.

Your customers will thank you.

State Colors

The following colors are used in the chart bars to indicate the different stages of a request.

DNS

Web browser is looking up DNS information

SSL

Web browser is performing an SSL handshake

Connect

Web browser is connecting to the server

Send

Web browser is sending data to the server

Wait

Web browser is waiting for data from the server

Receive

Web browser is receiving data from the server

Blocked

Web browser is not ready to send

Content Types

The following icons are used to indicate different content types.

HTML

HTML Document

JavaScript

JavaScript file

CSS

CSS file

Image

Image file

Text/Plain

Plain text document

Other

Any other unknown content type

Warning

The request got a 4XX, 5XX response or couldn’t be loaded

Redirect

The request got a 3XX response and was redirected

Server Response Codes

To make it easy for you to differentiate between the HTTP response codes in the chart, we’ve added color-coded dots beside each URL.

2xx

The server responded with a successful code

3xx

The request was redirected to another target

4xx

A client error occurred, for example 404 page not found

5xx

A server error occurred, for example 500 internal server error