2.6 sec in total
47 ms
956 ms
1.6 sec
Welcome to simons.ca homepage info - get ready to check Simons best content for Canada right away, or after learning these important things about simons.ca
SALE EVENT! Up to 50% Off on the hottest summer trends at Simons and Up to 70% Off on Designers. Fashion for women, men, designers and the home. Easy returns.
Visit simons.caWe analyzed Simons.ca page load time and found that the first response time was 47 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
simons.ca performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value12.8 s
0/100
25%
Value11.3 s
5/100
10%
Value3,200 ms
2/100
30%
Value0.001
100/100
15%
Value22.5 s
1/100
10%
47 ms
87 ms
128 ms
33 ms
85 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Simons.ca, 63% (85 requests) were made to Imarcom.simonscdn.ca and 16% (22 requests) were made to Css.simonscdn.ca. The less responsive or slowest element that took the longest time to load (286 ms) relates to the external source Imc-analytics.com.
Page size can be reduced by 1.5 MB (26%)
5.6 MB
4.2 MB
In fact, the total size of Simons.ca main page is 5.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 80.3 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 80.3 kB or 79% of the original size.
Potential reduce by 123.1 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. Simons images are well optimized though.
Potential reduce by 904.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 904.7 kB or 76% of the original size.
Potential reduce by 376.7 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. Simons.ca needs all CSS files to be minified and compressed as it can save up to 376.7 kB or 75% of the original size.
Number of requests can be reduced by 30 (23%)
131
101
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simons. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
simons.ca
47 ms
www.simons.ca
87 ms
128 ms
simons_head.js
33 ms
simons_head.css
85 ms
css
71 ms
2016-02-23_14-59-11.css
31 ms
2016-02-23_14-59-11.js
57 ms
simons_foot_en.js
9 ms
account.country_preference.js
9 ms
2016-02-23_15-00-03.js
13 ms
2016-02-23_15-00-03.js
79 ms
2016-02-23_15-00-03.js
79 ms
remarketing.js
77 ms
2016-02-23_15-00-03.js
8 ms
dc.js
36 ms
rewards_logo-green.png
12 ms
bag3.png
19 ms
logo_print.png
18 ms
loading.gif
15 ms
logo_simons.png
12 ms
close.png
15 ms
menu-gradient.png
24 ms
designers_women.jpg
14 ms
designers_men.jpg
14 ms
red_flag.png
17 ms
twik.png
14 ms
icone.png
17 ms
contempo.png
19 ms
ifiv5-f.png
16 ms
miiyu.png
21 ms
le31.png
17 ms
djab.png
17 ms
ifiv5-h.png
21 ms
simons_maison.png
20 ms
loupe.png
19 ms
dynamic_scroll_down.png
20 ms
2bb1c3770395bfeb4cda5d4690179648.png
22 ms
976ab393d9a645694576dc4ae09406af.png
21 ms
spacer.gif
23 ms
2689d66cd0212d97fcdc0ce342e7e91e.png
21 ms
home-newsletter-subscribe-bt.png
26 ms
home-newsletter-subscribe-en.png
24 ms
home-return-pub-en-v2.png
23 ms
home-return-pub-en-v4.png
23 ms
footer-bg.png
23 ms
footer-text-a-en.png
24 ms
simons_buttons.png
26 ms
simons-footer-text-en.png
28 ms
footer_share_background.png
26 ms
footer_cards-en.png
27 ms
load_sprites.png
22 ms
TweenLite.min.js
15 ms
CSSPlugin.min.js
22 ms
__utm.gif
219 ms
a-medium.woff
18 ms
fbevents.js
143 ms
activityi;src=4863916;type=invmedia;cat=qa4ahatc;ord=4447663072496.652
168 ms
14.js
177 ms
jStorage.js
286 ms
like.php
222 ms
fancybox.png
121 ms
spacer.gif
97 ms
2bb2b596231d0306444e5c20fb066c47.sprite45.en.png
52 ms
2bb2b596231d0306444e5c20fb066c47.sprite78.en.png
52 ms
4a0ce0e8cf408861f830433d8a4ce86f.sprite42.en.png
49 ms
44f2b292641381970f2f24d4c88a0ccc.sprite35.en.png
49 ms
7e01ef8b46b4428628451f7f520647db.sprite35.en.png
47 ms
10d286ae9d480c6e087685bbf5791619.sprite35.en.png
57 ms
7fe2b786840f63afe43a78ba43542cd9.sprite35.en.png
68 ms
bf3ac7cbb42b231805a6830d897f3fbd.sprite34.en.png
54 ms
31116b5e46bad64a7cc60d1dc05900df.sprite36.en.png
57 ms
4880087e0f100f3270d9f0bf3afa6cae.sprite35.en.png
67 ms
aa315d3b2f7806e7fa4df4f1ce34ecd9.sprite35.en.png
63 ms
53e05f9db431885c5f60d313ed9c1546.sprite35.en.png
66 ms
d40f0dc38960f1f07d58d80a9addd148.sprite36.en.png
68 ms
e7d339b6801ce3082aeca998c5cb1e77.sprite35.en.png
74 ms
f5e6bdae46d3f687d0277880004f9671.sprite31.en.png
73 ms
6153d4924b127f1fc031cb02da0df964.sprite29.en.png
72 ms
ce2ebbdd6e830bcd979b6406c53f9a90.sprite35.en.png
73 ms
f06f30f4901ec2fdb6b01e5caca38fd8.sprite31.en.png
73 ms
0e4cd502b53a9172942ed646ad6798b4.sprite31.en.png
77 ms
1a63fe9009507db27471b05547944616.sprite36.en.png
78 ms
0e772373f3ecfb539bee6891284e4bc3.jpg
81 ms
landing-backtop-en.png
76 ms
2bb2b596231d0306444e5c20fb066c47.en.jpg
89 ms
landing_banner_arrow.png
76 ms
landing-store-arrows.png
93 ms
dot_40.png
47 ms
input_text_left.png
47 ms
input_text_right.png
47 ms
select_left.png
46 ms
select_right.png
63 ms
textarea_tl.png
49 ms
textarea_tm.png
62 ms
textarea_tr.png
61 ms
textarea_ml.png
62 ms
textarea_mr.png
62 ms
textarea_bl.png
60 ms
textarea_bm.png
68 ms
textarea_br.png
69 ms
get_location.php
130 ms
fancybox-x.png
53 ms
fancybox-y.png
50 ms
blank.gif
52 ms
404.html
50 ms
35 ms
adgear.js
4 ms
conversion.js
17 ms
chip=5ed68070f17e0130ae300024e87a30c2.gif
101 ms
14.html
27 ms
45 ms
vpc6VNjRPXV.js
40 ms
LVx-xkvaJ0b.png
40 ms
43 ms
4a0ce0e8cf408861f830433d8a4ce86f.en.jpg
32 ms
chip=91365630fbac0130b50a0024e87a30c2.gif
61 ms
44f2b292641381970f2f24d4c88a0ccc.en.jpg
19 ms
7e01ef8b46b4428628451f7f520647db.en.jpg
16 ms
10d286ae9d480c6e087685bbf5791619.en.jpg
16 ms
7fe2b786840f63afe43a78ba43542cd9.en.jpg
16 ms
bf3ac7cbb42b231805a6830d897f3fbd.en.jpg
18 ms
31116b5e46bad64a7cc60d1dc05900df.en.jpg
33 ms
4880087e0f100f3270d9f0bf3afa6cae.en.jpg
17 ms
aa315d3b2f7806e7fa4df4f1ce34ecd9.en.jpg
31 ms
53e05f9db431885c5f60d313ed9c1546.en.jpg
29 ms
d40f0dc38960f1f07d58d80a9addd148.en.jpg
28 ms
e7d339b6801ce3082aeca998c5cb1e77.en.jpg
47 ms
f5e6bdae46d3f687d0277880004f9671.en.jpg
32 ms
6153d4924b127f1fc031cb02da0df964.en.jpg
30 ms
ce2ebbdd6e830bcd979b6406c53f9a90.en.jpg
27 ms
f06f30f4901ec2fdb6b01e5caca38fd8.en.jpg
31 ms
0e4cd502b53a9172942ed646ad6798b4.en.jpg
27 ms
1a63fe9009507db27471b05547944616.en.jpg
43 ms
d83f4926a10fb674ce1d93bfa2fa749c.en.jpg
28 ms
db05a207258519f3fb6263c7fd30f918.en.jpg
43 ms
simons.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
simons.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
simons.ca 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 uses 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 Simons.ca 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 Simons.ca 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.
simons.ca
Open Graph description is not detected on the main page of Simons. 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: