Tools & Wizards About Us
jewlr.com.au screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

jewlr.com.au

Personalised Jewellery | Custom Gemstones & Engravings | Jewlr

Page Load Speed

3.9 sec in total

First Response

57 ms

Resources Loaded

1.7 sec

Page Rendered

2.2 sec

jewlr.com.au screenshot

About Website

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

Jewlr specialises in selling high quality personalised jewellery, made just for you. Create the perfect gift or personalise something for yourself. Enjoy Free Shipping and 99-Day Returns!

Visit jewlr.com.au

Key Findings

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

Performance Metrics

jewlr.com.au performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value4,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

jewlr.com.au

57 ms

1507 ms

gtm.js

149 ms

jewlr.gif

48 ms

functionpro-book-webfont.woff

80 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Jewlr.com.au, 63% (34 requests) were made to Cdn.jewlr.com and 20% (11 requests) were made to Cms.jewlr.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Jewlr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 458.9 kB (31%)

Content Size

1.5 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Jewlr.com.au main page is 1.5 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. 35% of websites need less resources to load. Javascripts take 733.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 458.5 kB

  • Original 512.9 kB
  • After minification 512.4 kB
  • After compression 54.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 458.5 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 245.7 kB
  • After minification 245.7 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. Jewlr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 432 B

  • Original 733.5 kB
  • After minification 733.5 kB
  • After compression 733.1 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.

Requests Breakdown

Number of requests can be reduced by 27 (55%)

Requests Now

49

After Optimization

22

  • Images
  • JavaScript

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

Network Requests Diagram

jewlr.com.au

jewlr.com.au

57 ms

1507 ms

gtm.js

gtm.js

149 ms

jewlr.gif

jewlr.gif

48 ms

functionpro-book-webfont.woff

functionpro-book-webfont.woff

80 ms

functionpro-light-webfont.woff

functionpro-light-webfont.woff

91 ms

functionpro-medium-webfont.woff

functionpro-medium-webfont.woff

108 ms

2024_Jewlr_Logo-751b8a764f80286444b8.svg

2024_Jewlr_Logo-751b8a764f80286444b8.svg

64 ms

desktop_ca_a_2x_4c65546209.jpg

desktop_ca_a_2x_4c65546209.jpg

107 ms

cta_e5c4ca41cc.svg

cta_e5c4ca41cc.svg

60 ms

JWL_0515_959b5ac0e0.jpg

JWL_0515_959b5ac0e0.jpg

91 ms

JWL_0124_26d85a084c.jpg

JWL_0124_26d85a084c.jpg

261 ms

JWLN_0720_9925fb8ac9.jpg

JWLN_0720_9925fb8ac9.jpg

92 ms

JWLNK_0049_0e3455a04c.jpg

JWLNK_0049_0e3455a04c.jpg

79 ms

JWLN_0483_1_4a54a8588f.jpg

JWLN_0483_1_4a54a8588f.jpg

98 ms

JWLMP_0096_7827aebcf9.jpg

JWLMP_0096_7827aebcf9.jpg

124 ms

JWL_1017_15_RD_R7_fc1a876acf.jpg

JWL_1017_15_RD_R7_fc1a876acf.jpg

124 ms

JWL_0849_57bf4dd024.jpg

JWL_0849_57bf4dd024.jpg

125 ms

pendant_1-b3c51fc2e9540e06ba98.svg

pendant_1-b3c51fc2e9540e06ba98.svg

33 ms

arrow_left.svg

arrow_left.svg

20 ms

arrow_right.svg

arrow_right.svg

37 ms

JWLP_0698_cf02dd961f.jpg

JWLP_0698_cf02dd961f.jpg

148 ms

ring_3-0e789ec923626bc7d2c0.svg

ring_3-0e789ec923626bc7d2c0.svg

32 ms

ring_4-e528304285c166f7dfaf.svg

ring_4-e528304285c166f7dfaf.svg

32 ms

ring_1-11675d6454960cd9cf66.svg

ring_1-11675d6454960cd9cf66.svg

21 ms

ring_2-a11f80a1e0cab61776e4.svg

ring_2-a11f80a1e0cab61776e4.svg

20 ms

bracelet_1-9bd05f2e604b6421b152.svg

bracelet_1-9bd05f2e604b6421b152.svg

30 ms

runtime-db312aa31e4b8fc71bd4.js

runtime-db312aa31e4b8fc71bd4.js

17 ms

6347-1d991110d98f3cf48278.js

6347-1d991110d98f3cf48278.js

19 ms

4574-1d81bd8c911bc4d693c0.js

4574-1d81bd8c911bc4d693c0.js

36 ms

8037-709bf5730253edde2848.js

8037-709bf5730253edde2848.js

28 ms

9792-e448e6cf27e116a96345.js

9792-e448e6cf27e116a96345.js

31 ms

share-7fc87445d08eac1674e6.js

share-7fc87445d08eac1674e6.js

33 ms

146-40ca9c5f114ea683ff79.js

146-40ca9c5f114ea683ff79.js

37 ms

6550-105f1dd5171209f76a0f.js

6550-105f1dd5171209f76a0f.js

52 ms

9087-8fb5acd142e66f3451ee.js

9087-8fb5acd142e66f3451ee.js

65 ms

3342-cc2fc9889cdfd7fc69f1.js

3342-cc2fc9889cdfd7fc69f1.js

55 ms

2765-1a30a1405b426335f222.js

2765-1a30a1405b426335f222.js

54 ms

1309-cf590a8868d43fddfcc6.js

1309-cf590a8868d43fddfcc6.js

94 ms

JewlrApp-4c595b1017889bd8b9c7.js

JewlrApp-4c595b1017889bd8b9c7.js

54 ms

6609-00cfb740c171cdd3544a.chunk.js

6609-00cfb740c171cdd3544a.chunk.js

82 ms

982-c715afd3ea7022a159a8.chunk.js

982-c715afd3ea7022a159a8.chunk.js

73 ms

3358-6aff3ae03ac6f195fff4.chunk.js

3358-6aff3ae03ac6f195fff4.chunk.js

80 ms

8980-0f511348b209bdec28bd.chunk.js

8980-0f511348b209bdec28bd.chunk.js

78 ms

7632-126d73703b6edbd437cc.chunk.js

7632-126d73703b6edbd437cc.chunk.js

83 ms

9598-7cb2615cb19536cb2d23.chunk.js

9598-7cb2615cb19536cb2d23.chunk.js

85 ms

441-2e640644c312614eb1dc.chunk.js

441-2e640644c312614eb1dc.chunk.js

99 ms

8769-952835f168e008029298.chunk.js

8769-952835f168e008029298.chunk.js

98 ms

areas-collection-load-collection-70e401cd47a0698421fa.chunk.js

areas-collection-load-collection-70e401cd47a0698421fa.chunk.js

102 ms

homepage-banner-f8137443833af73cad76.chunk.js

homepage-banner-f8137443833af73cad76.chunk.js

98 ms

components-landing-row-94a4a0138046d53cd657.chunk.js

components-landing-row-94a4a0138046d53cd657.chunk.js

106 ms

4538-e24c982ae6151ed07e39.chunk.js

4538-e24c982ae6151ed07e39.chunk.js

118 ms

elements-landing-carousel-block-e26bc39c2a768c1233c3.chunk.js

elements-landing-carousel-block-e26bc39c2a768c1233c3.chunk.js

130 ms

components-landing-feature-grid-9c75d0f2d136009b4597.chunk.js

components-landing-feature-grid-9c75d0f2d136009b4597.chunk.js

115 ms

Accessibility Review

jewlr.com.au accessibility score

91

Accessibility Issues

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

jewlr.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jewlr.com.au SEO score

96

Search Engine Optimization Advices

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

jewlr.com.au

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