Tools & Wizards About Us
drawelry.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

drawelry.com

Drawelry-Personalized Jewelry-Create Your Own Jewelry

Page Load Speed

3 sec in total

First Response

93 ms

Resources Loaded

1 sec

Page Rendered

1.8 sec

drawelry.com screenshot

About Website

Welcome to drawelry.com homepage info - get ready to check Drawelry best content for Hong Kong right away, or after learning these important things about drawelry.com

Drawelry-Personalized Jewelry-Create Your Own Jewelry

Visit drawelry.com

Key Findings

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

Performance Metrics

drawelry.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value4,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

www.drawelry.com

93 ms

5d8cad961bdc730f.css

24 ms

d98cf543673b1d0f.css

43 ms

a62e89ab83a9e687.css

35 ms

c8cec7a72168f22c.css

39 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 90% of them (45 requests) were addressed to the original Drawelry.com, 4% (2 requests) were made to Res2022.drawmade.com and 4% (2 requests) were made to Images.drawelry.com. The less responsive or slowest element that took the longest time to load (753 ms) relates to the external source Res2022.drawmade.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.1 kB (49%)

Content Size

430.0 kB

After Optimization

219.9 kB

  • HTML
  • Images

In fact, the total size of Drawelry.com main page is 430.0 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. 70% of websites need less resources to load. HTML takes 235.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 210.1 kB

  • Original 235.2 kB
  • After minification 235.2 kB
  • After compression 25.1 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 210.1 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 42 (88%)

Requests Now

48

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.drawelry.com

www.drawelry.com

93 ms

5d8cad961bdc730f.css

5d8cad961bdc730f.css

24 ms

d98cf543673b1d0f.css

d98cf543673b1d0f.css

43 ms

a62e89ab83a9e687.css

a62e89ab83a9e687.css

35 ms

c8cec7a72168f22c.css

c8cec7a72168f22c.css

39 ms

d4289091b9aac1bb.css

d4289091b9aac1bb.css

37 ms

cfa90d09d93e2e33.css

cfa90d09d93e2e33.css

95 ms

931d12294f224f73.css

931d12294f224f73.css

40 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

43 ms

8987-c25c88fe666e3ba7.js

8987-c25c88fe666e3ba7.js

76 ms

25675-7a94c9577814b2cd.js

25675-7a94c9577814b2cd.js

77 ms

16518-55214b11a211d391.js

16518-55214b11a211d391.js

74 ms

22546-9596c360769df9ad.js

22546-9596c360769df9ad.js

73 ms

91036-fce64380680a10b0.js

91036-fce64380680a10b0.js

81 ms

25715-4e4e5501f586dd0e.js

25715-4e4e5501f586dd0e.js

78 ms

88045-b4faea7b605b8e7d.js

88045-b4faea7b605b8e7d.js

85 ms

13593-7e1503122f2e0681.js

13593-7e1503122f2e0681.js

86 ms

71217-14049c8dc55b6edd.js

71217-14049c8dc55b6edd.js

86 ms

9624-5989b00276b87c09.js

9624-5989b00276b87c09.js

139 ms

45644-633e4af6f0190d0e.js

45644-633e4af6f0190d0e.js

140 ms

58907-04bf2f8539e4b1f3.js

58907-04bf2f8539e4b1f3.js

92 ms

21159.2611c906ae50b7e4.js

21159.2611c906ae50b7e4.js

92 ms

63575.3306f09e75034e82.js

63575.3306f09e75034e82.js

91 ms

48119-25e6c251adbb4a47.js

48119-25e6c251adbb4a47.js

143 ms

27315-df111a785d99c626.js

27315-df111a785d99c626.js

148 ms

5577-499ec64cc8f7e1cb.js

5577-499ec64cc8f7e1cb.js

147 ms

50030.8405eceab1471817.js

50030.8405eceab1471817.js

141 ms

56461.079a18fedcfe3d39.js

56461.079a18fedcfe3d39.js

141 ms

20750.22839b88d4daa7fa.js

20750.22839b88d4daa7fa.js

145 ms

21998.e67fc298fed4d8c6.js

21998.e67fc298fed4d8c6.js

152 ms

40296-ad7106616971d6ea.js

40296-ad7106616971d6ea.js

154 ms

7687.a54da8aff98f84ed.js

7687.a54da8aff98f84ed.js

170 ms

20183.16d9cc9d04be31ee.js

20183.16d9cc9d04be31ee.js

157 ms

22529.6214ec391f9ca00f.js

22529.6214ec391f9ca00f.js

155 ms

52963.7586c52ddb2ee994.js

52963.7586c52ddb2ee994.js

154 ms

webpack-64be3fa24f80c518.js

webpack-64be3fa24f80c518.js

158 ms

64b78273498b0.png

64b78273498b0.png

142 ms

9.png

9.png

71 ms

TOP-Banner.jpg

TOP-Banner.jpg

218 ms

framework-f8115f7fae64930e.js

framework-f8115f7fae64930e.js

148 ms

main-4f8dab6f0148b85d.js

main-4f8dab6f0148b85d.js

140 ms

_app-b36bf353d806cb16.js

_app-b36bf353d806cb16.js

134 ms

49990-9163a20148fecb4e.js

49990-9163a20148fecb4e.js

129 ms

9912-f5fe8e3a70b9937f.js

9912-f5fe8e3a70b9937f.js

131 ms

12626-f92504dd6f08bcf6.js

12626-f92504dd6f08bcf6.js

132 ms

index-eaee41bebfb16986.js

index-eaee41bebfb16986.js

134 ms

_buildManifest.js

_buildManifest.js

100 ms

_ssgManifest.js

_ssgManifest.js

98 ms

63b678a34fbc3.gif

63b678a34fbc3.gif

753 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

1 ms

Accessibility Review

drawelry.com accessibility score

83

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.

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

drawelry.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

drawelry.com SEO score

99

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 Drawelry.com 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 Drawelry.com 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

drawelry.com

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