6.3 sec in total
1.5 sec
4.5 sec
296 ms
Click here to check amazing Spicers content for Canada. Otherwise, check out these important facts you probably never knew about spicers.ca
Visit spicers.caWe analyzed Spicers.ca page load time and found that the first response time was 1.5 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
spicers.ca performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value9.7 s
0/100
25%
Value7.0 s
32/100
10%
Value480 ms
60/100
30%
Value0.176
68/100
15%
Value10.3 s
24/100
10%
1454 ms
193 ms
512 ms
219 ms
27 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 70% of them (63 requests) were addressed to the original Spicers.ca, 7% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Spicers.ca.
Page size can be reduced by 1.2 MB (32%)
3.7 MB
2.6 MB
In fact, the total size of Spicers.ca main page is 3.7 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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.1 kB or 75% of the original size.
Potential reduce by 741.9 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. Obviously, Spicers needs image optimization as it can save up to 741.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 316.9 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 316.9 kB or 67% of the original size.
Potential reduce by 107.3 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. Spicers.ca needs all CSS files to be minified and compressed as it can save up to 107.3 kB or 89% of the original size.
Number of requests can be reduced by 33 (45%)
73
40
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spicers. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.spicers.ca
1454 ms
language-selector.css
193 ms
style.css
512 ms
spicerscss.css
219 ms
css
27 ms
buttons.js
8 ms
layerslider.css
256 ms
css
14 ms
greensock.js
467 ms
jquery.js
516 ms
jquery-migrate.min.js
215 ms
layerslider.kreaturamedia.jquery.js
505 ms
layerslider.transitions.js
494 ms
jquery.min.js
9 ms
jquery.bxslider.min.js
217 ms
jquery.scrollbox.js
298 ms
functions.js
312 ms
wp-embed.min.js
315 ms
sitepress.js
361 ms
wp-emoji-release.min.js
329 ms
nav-arrow-down.png
203 ms
logo.png
205 ms
ico-nav-arrow-grey.png
201 ms
bg-search.png
205 ms
bg-mag.png
206 ms
2015-07-slide1-captivating.jpg
719 ms
2015-07-slide2-powerful.jpg
888 ms
2015-07-slide3-technology.jpg
881 ms
july4supreme_v2b-1.png
731 ms
CNGlogo.png
208 ms
Actega_Logo.png
278 ms
Catalina_Logo.png
288 ms
Domtar_Logo.png
358 ms
dtec_Logo.png
418 ms
EDGE_Logo.png
486 ms
hubergroup_Logo.png
490 ms
Independent_Logo.png
611 ms
IP_Logo.png
563 ms
ipg_Logo.png
639 ms
Kodak_Logo.png
738 ms
Kruger_Logo.png
715 ms
MACtac_Logo.png
752 ms
Mohawk_Logo.png
772 ms
Neenah_Logo.png
789 ms
Pacesetter_Logo.png
802 ms
RitRAMA_Logo.png
815 ms
Rolland_Logo.png
844 ms
RoyalContainers_Logo.png
932 ms
Sihl_Logo.png
991 ms
Supreme_Logo.png
879 ms
SupremeX_Logo.png
918 ms
Ultraflex_Logo.png
918 ms
Unigraph_Logo.png
926 ms
Verso_Logo.png
944 ms
fostbold-webfont.woff
969 ms
analytics.js
105 ms
getAllAppDefault.esi
1068 ms
skin.css
832 ms
fostmedm-webfont.woff
846 ms
Zebra_Logo.png
847 ms
bg-section5.jpg
847 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
85 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
86 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
87 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
86 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
86 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
86 ms
collect
66 ms
blank.gif
81 ms
skin.png
92 ms
Roboto-Light-webfont.woff
67 ms
Roboto-Thin-webfont.woff
91 ms
Roboto-Regular-webfont.woff
159 ms
Roboto-Medium-webfont.woff
192 ms
Roboto-Bold-webfont.woff
132 ms
Roboto-Black-webfont.woff
139 ms
getSegment.php
14 ms
checkOAuth.esi
11 ms
t.dhj
9 ms
t.dhj
17 ms
cm
57 ms
x35248
208 ms
s-3271.xgi
16 ms
9 ms
hbpix
89 ms
21 ms
xrefid.xgi
17 ms
pixel
17 ms
pixel
25 ms
2981
21 ms
spicers.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
spicers.ca 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
spicers.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spicers.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Spicers.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.
spicers.ca
Open Graph description is not detected on the main page of Spicers. 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: