1.9 sec in total
118 ms
1.7 sec
61 ms
Welcome to hazellily.com homepage info - get ready to check Hazel Lily best content right away, or after learning these important things about hazellily.com
A luxury designer consignment shop online and in Toronto Find your favourite pre-loved designer pieces at a fraction of the price Shipping across North America
Visit hazellily.comWe analyzed Hazellily.com page load time and found that the first response time was 118 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
hazellily.com performance score
name
value
score
weighting
Value2.5 s
65/100
10%
Value30.5 s
0/100
25%
Value18.0 s
0/100
10%
Value5,920 ms
0/100
30%
Value0.023
100/100
15%
Value29.5 s
0/100
10%
118 ms
32 ms
31 ms
30 ms
183 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hazellily.com, 57% (42 requests) were made to Static.wixstatic.com and 22% (16 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 763.0 kB (59%)
1.3 MB
537.1 kB
In fact, the total size of Hazellily.com 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. 30% of websites need less resources to load. HTML takes 917.0 kB which makes up the majority of the site volume.
Potential reduce by 757.7 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 757.7 kB or 83% of the original size.
Potential reduce by 2.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. Hazel Lily images are well optimized though.
Potential reduce by 2.7 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.
Number of requests can be reduced by 10 (18%)
57
47
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hazel Lily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.hazellily.com
118 ms
minified.js
32 ms
focus-within-polyfill.js
31 ms
polyfill.min.js
30 ms
thunderbolt-commons.a475be57.bundle.min.js
183 ms
main.1438a05e.bundle.min.js
169 ms
lodash.min.js
167 ms
react.production.min.js
164 ms
react-dom.production.min.js
168 ms
siteTags.bundle.min.js
183 ms
wix-perf-measure.umd.min.js
197 ms
5fd9a5_43b1cd8ecec4447bb7b35a62fe9af679~mv2_d_3300_1258_s_2.png
314 ms
bundle.min.js
84 ms
5fd9a5_f74fe6a342b34b13b39b521fcc69c883~mv2.jpg
482 ms
5fd9a5_da02510d6d814c28850a2501ded34786~mv2.jpg
431 ms
5fd9a5_bc6232957faf4e03bdec97adbf0f19a9~mv2.jpg
485 ms
5fd9a5_c5b908c9ea894068899e262d7b69b392~mv2.jpeg
433 ms
5fd9a5_55b8c3da321b4118a76897030c2094f6~mv2.jpeg
325 ms
5fd9a5_3944dd54b0de4700be31ddea51926681~mv2.jpeg
413 ms
5fd9a5_3d625fb1eda84975a259d9d59e3b4e4f~mv2.jpeg
436 ms
5fd9a5_09562e3d0f9646cdaf8ae7b9d8a3a529~mv2.jpg
522 ms
5fd9a5_b5c042dccfed43268905fc666ec9f6e4~mv2.jpg
614 ms
5fd9a5_7ade07d16c6e42d8abddc8b89097a39d~mv2.jpeg
534 ms
5fd9a5_5437b6a947124f9fb6ce2ddb75de8598~mv2.jpeg
545 ms
5fd9a5_a12f3043a46e49288e331ab3110f55a2~mv2.jpeg
586 ms
5fd9a5_88eef230dd72404caa15b1e4a30623ad~mv2.jpeg
593 ms
5fd9a5_bb15318f7eb8442e89eb4808c1f3eaa2~mv2.jpeg
614 ms
5fd9a5_f8a41d38f977443d8e71c45ef2609261~mv2.jpeg
717 ms
5fd9a5_a58e7c5d5a87425eb38f8c575debcfb9~mv2.jpeg
721 ms
5fd9a5_57b2bb75b7f34bc88a2d08ddea6912ed~mv2.jpeg
706 ms
5fd9a5_b92104207d684da79b10c5cbe4fb7e9f~mv2.jpeg
689 ms
5fd9a5_5efc05d6d8bd460eae4fc21644fd099b~mv2.jpg
702 ms
5fd9a5_a0ebe7b039874ef8b608081bef26d775~mv2.jpeg
750 ms
5fd9a5_f298d2c6ff08482e9a6e2bec4106b12f~mv2.jpeg
805 ms
5fd9a5_20f60f0d0d0b4ccb9db1875d5b40f2db~mv2.jpeg
809 ms
5fd9a5_9f742979a72044dbb6aff51b0c6932ab~mv2.jpeg
810 ms
5fd9a5_836c0b736da3445c8efc1cf99218520d~mv2.jpeg
832 ms
5fd9a5_a1d1f0ac301f40d2970ba5a6683c0f07~mv2.jpeg
854 ms
5fd9a5_9cdf70d7899d4a5890f8fe488caa729a~mv2.jpeg
939 ms
5fd9a5_c266972f14be481a9edb4126b9b66eab~mv2.jpeg
1001 ms
5fd9a5_67ec2f4bef0b42b1902060d318c2924d~mv2.jpeg
955 ms
5fd9a5_e3e0b5fdebce442cb21c5d0b855f30ad~mv2.jpeg
1001 ms
5fd9a5_f683f6ee483244e08ed39262a6dfe769~mv2.jpeg
964 ms
5fd9a5_dff6ef34bfd44acc8461a1f8fc40f0f2~mv2.jpeg
986 ms
5fd9a5_e992da24775e47cd889b30887d73f4f0~mv2.jpeg
1056 ms
5fd9a5_1b86d10eb14d4a6983cad8220f2e082e~mv2.jpeg
1051 ms
5fd9a5_f0b9def488d54ca28221443144105521~mv2.jpg
1126 ms
5fd9a5_f13e4ef3d6b244549a270384904fb816~mv2.jpeg
1066 ms
169 ms
135 ms
161 ms
161 ms
160 ms
156 ms
170 ms
197 ms
194 ms
194 ms
191 ms
188 ms
e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff
26 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
39 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
39 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
38 ms
5fd9a5_079abc74803949799e05844313aaf5bf~mv2.png
897 ms
5fd9a5_fc500dfc84bb4541951b9b9e89862745~mv2.png
846 ms
5fd9a5_5e5364eaff7f46669b6c38149d863617~mv2.png
835 ms
5fd9a5_9bd03c6e8dd341b5a41c1fa8501ec241~mv2.jpeg
874 ms
5fd9a5_6b21d5dacb4a4a469fe354068740e958~mv2.jpg
896 ms
5fd9a5_b3a1c6fb9ade4ab7bc11238dba36c64c~mv2.jpg
825 ms
deprecation-en.v5.html
7 ms
bolt-performance
21 ms
deprecation-style.v5.css
8 ms
right-arrow.svg
6 ms
hazellily.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
hazellily.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hazellily.com SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hazellily.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 Hazellily.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.
hazellily.com
Open Graph data is detected on the main page of Hazel Lily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: