Tools & Wizards About Us
eleganter.com.au screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

eleganter.com.au

Eleganter Australia | Wholesale Supplier, Distributor & Importer of quality Wooden Toys in Australia

Page Load Speed

6.2 sec in total

First Response

1.2 sec

Resources Loaded

4.5 sec

Page Rendered

472 ms

eleganter.com.au screenshot

About Website

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

Leading Australian distributor of wholesale quality wooden and educational kids toys, baby toys, musical instruments, puzzles and games and craft kits. Our in-house Brands include Kaper Kidz, Calm & B...

Visit eleganter.com.au

Key Findings

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

Performance Metrics

eleganter.com.au performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

www.eleganter.com.au

1202 ms

app.css

37 ms

css

71 ms

style.css

81 ms

font-awesome.min.css

65 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 55% of them (35 requests) were addressed to the original Eleganter.com.au, 11% (7 requests) were made to Cdn.neto.com.au and 8% (5 requests) were made to Widget.reviews.io. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Eleganter.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.7 kB (4%)

Content Size

3.2 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eleganter.com.au main page is 3.2 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 68.2 kB

  • Original 83.1 kB
  • After minification 83.0 kB
  • After compression 15.0 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 68.2 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 74.1 kB

  • Original 3.0 MB
  • After minification 2.9 MB

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. Eleganter images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 364 B

  • Original 119.9 kB
  • After minification 119.9 kB
  • After compression 119.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 1.1 kB

  • Original 30.5 kB
  • After minification 30.5 kB
  • After compression 29.4 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. Eleganter.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (37%)

Requests Now

59

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.eleganter.com.au

www.eleganter.com.au

1202 ms

app.css

app.css

37 ms

css

css

71 ms

style.css

style.css

81 ms

font-awesome.min.css

font-awesome.min.css

65 ms

jquery-ui-1.8.18.custom.css

jquery-ui-1.8.18.custom.css

57 ms

jquery.fancybox.css

jquery.fancybox.css

59 ms

69 ms

js

js

122 ms

dist.js

dist.js

108 ms

dist.js

dist.js

142 ms

dist.css

dist.css

150 ms

style.css

style.css

148 ms

dist.js

dist.js

155 ms

jquery.min.js

jquery.min.js

54 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

55 ms

main.js

main.js

61 ms

bootstrap.min.js

bootstrap.min.js

56 ms

custom.js

custom.js

59 ms

jquery-ui-1.8.18.custom.min.js

jquery-ui-1.8.18.custom.min.js

58 ms

analytics.js

analytics.js

29 ms

gtm.js

gtm.js

61 ms

website_logo.png

website_logo.png

24 ms

70.png

70.png

41 ms

69.jpg

69.jpg

33 ms

58.jpg

58.jpg

38 ms

73.jpg

73.jpg

36 ms

67.jpg

67.jpg

49 ms

72.png

72.png

1966 ms

71.jpg

71.jpg

50 ms

CH10732.jpg

CH10732.jpg

89 ms

PA7038.jpg

PA7038.jpg

97 ms

NG23730.jpg

NG23730.jpg

99 ms

TJ558N.jpg

TJ558N.jpg

188 ms

CY20014.jpg

CY20014.jpg

101 ms

CA3016B.jpg

CA3016B.jpg

189 ms

DD7140.jpg

DD7140.jpg

189 ms

TH428.jpg

TH428.jpg

190 ms

css

css

30 ms

style-cf.css

style-cf.css

102 ms

header-bg.jpg

header-bg.jpg

57 ms

2(1).jpg

2(1).jpg

58 ms

1(1).jpg

1(1).jpg

58 ms

4(1).jpg

4(1).jpg

57 ms

5(1).jpg

5(1).jpg

62 ms

Calm%20%26%20Breezy%20(2).jpg

Calm%20%26%20Breezy%20(2).jpg

58 ms

Calm%20%26%20Breezy%20(1).jpg

Calm%20%26%20Breezy%20(1).jpg

59 ms

13.jpg

13.jpg

97 ms

12.jpg

12.jpg

103 ms

Calm%20%26%20Breezy%20(6).jpg

Calm%20%26%20Breezy%20(6).jpg

97 ms

Calm%20%26%20Breezy%20(4).jpg

Calm%20%26%20Breezy%20(4).jpg

103 ms

Calm%20%26%20Breezy%20(3).jpg

Calm%20%26%20Breezy%20(3).jpg

101 ms

Calm%20%26%20Breezy%20(5).jpg

Calm%20%26%20Breezy%20(5).jpg

102 ms

Website%20HEADING%20on%20PAGES%20FINAL%20(6).jpg

Website%20HEADING%20on%20PAGES%20FINAL%20(6).jpg

101 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

101 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

101 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

43 ms

reviews-widget-icons.ttf

reviews-widget-icons.ttf

42 ms

paymenticons.svg

paymenticons.svg

55 ms

collect

collect

65 ms

fbevents.js

fbevents.js

65 ms

remove.gif

remove.gif

17 ms

addtocart

addtocart

1549 ms

add.gif

add.gif

6 ms

Accessibility Review

eleganter.com.au accessibility score

73

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

eleganter.com.au best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

eleganter.com.au SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Eleganter.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 Eleganter.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

eleganter.com.au

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