1.9 sec in total
24 ms
1.3 sec
653 ms
Click here to check amazing SAIL content for Canada. Otherwise, check out these important facts you probably never knew about sail.ca
Shop the best items from over 600 outdoor brands; men's, women's, kids' clothing, hunting, fishing, camping gear and more. Fast shipping. Shop Now!
Visit sail.caWe analyzed Sail.ca page load time and found that the first response time was 24 ms and then it took 1.9 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.
sail.ca performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value20.0 s
0/100
25%
Value14.6 s
1/100
10%
Value10,250 ms
0/100
30%
Value0
100/100
15%
Value31.6 s
0/100
10%
24 ms
395 ms
90 ms
17 ms
134 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 74% of them (55 requests) were addressed to the original Sail.ca, 7% (5 requests) were made to I.ytimg.com and 3% (2 requests) were made to T.trackedlink.net. The less responsive or slowest element that took the longest time to load (465 ms) relates to the external source T.trackedlink.net.
Page size can be reduced by 747.0 kB (21%)
3.5 MB
2.8 MB
In fact, the total size of Sail.ca main page is 3.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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 96.5 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 96.5 kB or 77% of the original size.
Potential reduce by 185.0 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. SAIL images are well optimized though.
Potential reduce by 256.3 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 256.3 kB or 62% of the original size.
Potential reduce by 209.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. Sail.ca needs all CSS files to be minified and compressed as it can save up to 209.3 kB or 84% of the original size.
Number of requests can be reduced by 17 (26%)
66
49
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAIL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
sail.ca
24 ms
www.sail.ca
395 ms
nwayo-dependencies.js
90 ms
10329674951db9cbc9f2d0a01e5ad718.css
17 ms
e3f37a41704b63bf8eb1a9c19c05bb59.js
134 ms
246e3f9a6dff65ff9172121188485a71.css
133 ms
c9e8ae7946ce548a5048412279842ff0.js
64 ms
addthis_widget.js
25 ms
_dmpt.js
298 ms
gtm.js
181 ms
player_api
145 ms
bg-degnoir.png
84 ms
logo-v2.png
84 ms
icon_sprite.png
83 ms
An_469x400_menubox_femme_1.png
100 ms
An_469x400_menubox_homme.png.png
82 ms
An_469x400_menubox_junior.png
183 ms
An_469x400_menubox_chaussure.png
138 ms
An_469x400_menubox_orientation_1.png
176 ms
Hiver_clipA_V03.jpg
238 ms
HERO_FINAL_CLEARANCE_Fev20162_1.png
133 ms
EN-MINIBOX_VIP.jpg
173 ms
MINIBOX_Snowshoes_WinterPromotion_Jan20162.jpg
172 ms
EN-MINIBOX_SKIDEFOND_JAN2016.jpg
180 ms
Arcteryx_logo.png
190 ms
Berkley_logo.png
191 ms
Browning_logo.png
191 ms
Bushnell_logo.png
191 ms
Columbia_logo.png
190 ms
CUDA_logo.png
196 ms
Eureka_logo.png
211 ms
Garmin_logo.png
211 ms
Humminbird_logo.png
214 ms
Keen_logo.png
213 ms
Marmot_logo.png
213 ms
Merrel_logo.png
229 ms
Orage_logo.png
228 ms
Osprey_logo.png
227 ms
Rapala_logo.png
227 ms
Salomon_logo.png
227 ms
Shimano_logo.png
234 ms
TheNorthFace_logo_1.png
236 ms
An_469x303_bigbox_femme.png
256 ms
An_469x303_bigbox_femme_1.png
257 ms
An_469x400_menubox_chaussure_2.png
286 ms
An_469x303_bigbox_homme_2.png
302 ms
28C0CD_D_0.woff
232 ms
_dmpt.js
465 ms
fbevents.js
15 ms
analytics.js
23 ms
28C0CD_A_0.woff
211 ms
28C0CD_4_0.woff
227 ms
28C0CD_9_0.woff
226 ms
logo-150px.png
221 ms
127 ms
146 ms
www-widgetapi.js
87 ms
logo-youtube.png
226 ms
collect
20 ms
collect
104 ms
Spartan_an-300x219.jpg
199 ms
blog_camping_winter-003-300x219.jpg
189 ms
Cover-Photo-002-300x219.jpg
158 ms
lebon-300x219.jpg
158 ms
logo-footer.png
157 ms
vip-modal-bg.jpg
169 ms
lightbox-title-en.png
157 ms
playlistItems
134 ms
ga-audiences
42 ms
mqdefault.jpg
58 ms
mqdefault.jpg
67 ms
mqdefault.jpg
79 ms
mqdefault.jpg
84 ms
maxresdefault.jpg
135 ms
sail.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
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
sail.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
sail.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sail.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 Sail.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.
sail.ca
Open Graph data is detected on the main page of SAIL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: