Tools & Wizards About Us
highteaperth.com.au screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

highteaperth.com.au

highteaperth.com.au

Page Load Speed

9.1 sec in total

First Response

1.9 sec

Resources Loaded

6.8 sec

Page Rendered

350 ms

highteaperth.com.au screenshot

About Website

Visit highteaperth.com.au now to see the best up-to-date Highteaperth content and also check out these interesting facts you probably never knew about highteaperth.com.au

Hello and welcome to High Tea Perth. Here you will find the very best reviews of venues and locations who cater for High Tea In Perth Western Australia. Find photos, prices, reviews and more here at H...

Visit highteaperth.com.au

Key Findings

We analyzed Highteaperth.com.au page load time and found that the first response time was 1.9 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

highteaperth.com.au performance score

0

Network Requests Diagram

www.highteaperth.com.au

1914 ms

normalize.css

452 ms

style.css

906 ms

prettyPhoto.css

680 ms

grid.css

457 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 60% of them (41 requests) were addressed to the original Highteaperth.com.au, 7% (5 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Highteaperth.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 381.3 kB (29%)

Content Size

1.3 MB

After Optimization

919.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Highteaperth.com.au main page is 1.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 756.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 23.7 kB

  • Original 33.1 kB
  • After minification 31.4 kB
  • After compression 9.4 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.7 kB or 72% of the original size.

Image Optimization

-3%

Potential reduce by 19.5 kB

  • Original 756.5 kB
  • After minification 736.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Highteaperth images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 267.0 kB

  • Original 426.9 kB
  • After minification 357.8 kB
  • After compression 159.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 267.0 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 71.0 kB

  • Original 83.8 kB
  • After minification 61.1 kB
  • After compression 12.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Highteaperth.com.au needs all CSS files to be minified and compressed as it can save up to 71.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (58%)

Requests Now

65

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Highteaperth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.highteaperth.com.au

www.highteaperth.com.au

1914 ms

normalize.css

normalize.css

452 ms

style.css

style.css

906 ms

prettyPhoto.css

prettyPhoto.css

680 ms

grid.css

grid.css

457 ms

css

css

25 ms

css

css

37 ms

st.css

st.css

468 ms

pagenavi-css.css

pagenavi-css.css

468 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

1356 ms

modernizr-2.0.js

modernizr-2.0.js

1133 ms

superfish.js

superfish.js

701 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

946 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1129 ms

easyTooltip.js

easyTooltip.js

946 ms

jquery.loader.js

jquery.loader.js

1127 ms

swfobject.js

swfobject.js

1169 ms

jquery.cycle.all.js

jquery.cycle.all.js

1636 ms

audio.js

audio.js

1350 ms

custom.js

custom.js

1375 ms

maxheight.js

maxheight.js

1375 ms

adsbygoogle.js

adsbygoogle.js

9 ms

all.js

all.js

71 ms

comment-reply.min.js

comment-reply.min.js

1186 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

660 ms

analytics.js

analytics.js

5 ms

collect

collect

40 ms

body-tail.gif

body-tail.gif

230 ms

tail-top.png

tail-top.png

228 ms

splash.png

splash.png

469 ms

logo.png

logo.png

680 ms

nav-current.png

nav-current.png

236 ms

nav-divider.png

nav-divider.png

229 ms

slider-shadow.png

slider-shadow.png

456 ms

slider-bg.gif

slider-bg.gif

2045 ms

loading.gif

loading.gif

455 ms

slide02.jpg

slide02.jpg

2113 ms

slide04.jpg

slide04.jpg

1812 ms

content-bg.gif

content-bg.gif

1175 ms

title-decoration2.png

title-decoration2.png

702 ms

like-this-page.png

like-this-page.png

905 ms

perth_high_tea-300x200.jpg

perth_high_tea-300x200.jpg

937 ms

ca-pub-8152025709093191.js

ca-pub-8152025709093191.js

151 ms

zrt_lookup.html

zrt_lookup.html

148 ms

show_ads_impl.js

show_ads_impl.js

101 ms

widget-footer-tail.gif

widget-footer-tail.gif

1073 ms

widget-footer-top-tail.gif

widget-footer-top-tail.gif

1112 ms

title-decoration1.png

title-decoration1.png

1299 ms

list-divider.png

list-divider.png

1345 ms

155 ms

ping

ping

179 ms

xd_arbiter.php

xd_arbiter.php

67 ms

xd_arbiter.php

xd_arbiter.php

132 ms

ads

ads

310 ms

osd.js

osd.js

10 ms

like.php

like.php

131 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

158 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

169 ms

m_js_controller.js

m_js_controller.js

23 ms

abg.js

abg.js

38 ms

favicon

favicon

1185 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

43 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

28 ms

s

s

16 ms

x_button_blue2.png

x_button_blue2.png

20 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

4 ms

nivo-caption.png

nivo-caption.png

229 ms

ui

ui

29 ms

SEO Factors

highteaperth.com.au SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Highteaperth.com.au can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Highteaperth.com.au main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

highteaperth.com.au

Open Graph description is not detected on the main page of Highteaperth. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: