Tools & Wizards About Us
wheredidyougetthat.com.au screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wheredidyougetthat.com.au

Childrens clothes | Kids clothes | Toys | Puzzles

Page Load Speed

10.7 sec in total

First Response

1 sec

Resources Loaded

9.4 sec

Page Rendered

334 ms

wheredidyougetthat.com.au screenshot

About Website

Welcome to wheredidyougetthat.com.au homepage info - get ready to check Wheredidyougetthat best content right away, or after learning these important things about wheredidyougetthat.com.au

Where did you get that? is based in Adelaide Hills, South Australia. The products we sell are unique, boutique children's and mother's products from all around the world.

Visit wheredidyougetthat.com.au

Key Findings

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

Performance Metrics

wheredidyougetthat.com.au performance score

0

Network Requests Diagram

wheredidyougetthat.com.au

1004 ms

www.wheredidyougetthat.com.au

5458 ms

ga.js

10 ms

_8f78e8e37b5d951fe438a4d68f8d67f7.css

478 ms

_d44c6219a0ead7ff2dc94786461c9369.js

1202 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 89% of them (24 requests) were addressed to the original Wheredidyougetthat.com.au, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Wheredidyougetthat.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.0 kB (42%)

Content Size

760.2 kB

After Optimization

442.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 18.4 kB

  • Original 22.6 kB
  • After minification 19.4 kB
  • After compression 4.2 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. This page needs HTML code to be minified as it can gain 3.2 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.4 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 35.2 kB

  • Original 362.7 kB
  • After minification 327.6 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. Wheredidyougetthat images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 264.4 kB

  • Original 374.6 kB
  • After minification 327.0 kB
  • After compression 110.2 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 264.4 kB or 71% of the original size.

CSS Optimization

-20%

Potential reduce by 50 B

  • Original 245 B
  • After minification 238 B
  • After compression 195 B

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. Wheredidyougetthat.com.au needs all CSS files to be minified and compressed as it can save up to 50 B or 20% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wheredidyougetthat. According to our analytics all requests are already optimized.

Network Requests Diagram

wheredidyougetthat.com.au

wheredidyougetthat.com.au

1004 ms

www.wheredidyougetthat.com.au

www.wheredidyougetthat.com.au

5458 ms

ga.js

ga.js

10 ms

_8f78e8e37b5d951fe438a4d68f8d67f7.css

_8f78e8e37b5d951fe438a4d68f8d67f7.css

478 ms

_d44c6219a0ead7ff2dc94786461c9369.js

_d44c6219a0ead7ff2dc94786461c9369.js

1202 ms

func.js

func.js

489 ms

__utm.gif

__utm.gif

14 ms

collect

collect

66 ms

backgroundqmark.gif

backgroundqmark.gif

238 ms

HomebannerLittleGifts1.jpg

HomebannerLittleGifts1.jpg

707 ms

hp-djecopuzzles.jpg

hp-djecopuzzles.jpg

954 ms

HABA-Sand-table-296x285.jpg

HABA-Sand-table-296x285.jpg

478 ms

contigo296x247banner.jpg

contigo296x247banner.jpg

472 ms

Le-Toy-Van-Home-Page-Choc-chino.jpg

Le-Toy-Van-Home-Page-Choc-chino.jpg

707 ms

Automoblox%20Police%20296x247.jpg

Automoblox%20Police%20296x247.jpg

707 ms

Uncle-Goose-296x247.jpg

Uncle-Goose-296x247.jpg

946 ms

menu_bar_left.gif

menu_bar_left.gif

716 ms

spacer.gif

spacer.gif

942 ms

wdygt_logo.png

wdygt_logo.png

1176 ms

facebook_icon.png

facebook_icon.png

944 ms

twitter_icon.png

twitter_icon.png

955 ms

pinterest_icon.png

pinterest_icon.png

1177 ms

tree_subdir_plus.gif

tree_subdir_plus.gif

1155 ms

menu_bar_right.gif

menu_bar_right.gif

1156 ms

line2_background.png

line2_background.png

1169 ms

go.gif

go.gif

1170 ms

footer_brands.png

footer_brands.png

1621 ms

SEO Factors

wheredidyougetthat.com.au SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wheredidyougetthat.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 Wheredidyougetthat.com.au main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

wheredidyougetthat.com.au

Open Graph description is not detected on the main page of Wheredidyougetthat. 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: