Tools & Wizards About Us
sanco.ca screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

sanco.ca

Welcome to Sanco Supplies!

Page Load Speed

2.8 sec in total

First Response

419 ms

Resources Loaded

2.1 sec

Page Rendered

234 ms

sanco.ca screenshot

About Website

Welcome to sanco.ca homepage info - get ready to check Sanco best content right away, or after learning these important things about sanco.ca

Visit sanco.ca

Key Findings

We analyzed Sanco.ca page load time and found that the first response time was 419 ms and then it took 2.4 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.

Performance Metrics

sanco.ca performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

sanco.ca

419 ms

default.aspx

1038 ms

bootstrap.min.css

94 ms

jquery-ui.css

78 ms

jquery-3.6.0.min.js

92 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 35% of them (28 requests) were addressed to the original Sanco.ca, 23% (18 requests) were made to Images.jmcatalog.com and 10% (8 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Sanco.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 563.4 kB (17%)

Content Size

3.4 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sanco.ca main page is 3.4 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 150.1 kB

  • Original 179.7 kB
  • After minification 125.3 kB
  • After compression 29.6 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. This page needs HTML code to be minified as it can gain 54.4 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 150.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 152.2 kB

  • Original 2.6 MB
  • After minification 2.4 MB

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. Sanco images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 102.1 kB

  • Original 300.5 kB
  • After minification 300.5 kB
  • After compression 198.5 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 102.1 kB or 34% of the original size.

CSS Optimization

-52%

Potential reduce by 159.0 kB

  • Original 304.1 kB
  • After minification 298.0 kB
  • After compression 145.0 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. Sanco.ca needs all CSS files to be minified and compressed as it can save up to 159.0 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (46%)

Requests Now

70

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sanco.ca

sanco.ca

419 ms

default.aspx

default.aspx

1038 ms

bootstrap.min.css

bootstrap.min.css

94 ms

jquery-ui.css

jquery-ui.css

78 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

92 ms

jquery-ui.min.js

jquery-ui.min.js

87 ms

bootstrap.min.js

bootstrap.min.js

90 ms

bootbox.min.js

bootbox.min.js

79 ms

all.min.css

all.min.css

160 ms

main.min.css

main.min.css

158 ms

navbar.min.css

navbar.min.css

159 ms

items.min.css

items.min.css

179 ms

overall_Custom.min.css

overall_Custom.min.css

171 ms

navbar_top_Custom.min.css

navbar_top_Custom.min.css

179 ms

navbar_category_Custom.min.css

navbar_category_Custom.min.css

179 ms

st_Default.css

st_Default.css

179 ms

CombinedBaseSkinClassic.css

CombinedBaseSkinClassic.css

91 ms

FormDecorator.Default.css

FormDecorator.Default.css

85 ms

Ajax.Default.css

Ajax.Default.css

90 ms

WebForms.js

WebForms.js

139 ms

MicrosoftAjax.js

MicrosoftAjax.js

131 ms

MicrosoftAjaxWebForms.js

MicrosoftAjaxWebForms.js

137 ms

Core.js

Core.js

130 ms

ShortCutManagerScripts.js

ShortCutManagerScripts.js

140 ms

MaterialRippleScripts.js

MaterialRippleScripts.js

140 ms

RadFormDecorator.js

RadFormDecorator.js

140 ms

Ajax.js

Ajax.js

139 ms

jQueryExternal.js

jQueryExternal.js

139 ms

OverlayScript.js

OverlayScript.js

140 ms

owl.carousel.min.css

owl.carousel.min.css

116 ms

owl.theme.default.min.css

owl.theme.default.min.css

101 ms

animate.min.css

animate.min.css

107 ms

item_sections.min.css

item_sections.min.css

102 ms

owl.carousel.min.js

owl.carousel.min.js

94 ms

css2

css2

105 ms

css

css

37 ms

header-logo.png

header-logo.png

103 ms

XYN200-20043.JPG

XYN200-20043.JPG

207 ms

SCA400217.JPG

SCA400217.JPG

239 ms

XYN200-60043.JPG

XYN200-60043.JPG

238 ms

NORTHRBV150.JPG

NORTHRBV150.JPG

239 ms

SCA105065.JPG

SCA105065.JPG

237 ms

KAIKV17501.JPG

KAIKV17501.JPG

238 ms

KIM004007.JPG

KIM004007.JPG

217 ms

KAIAUTOVACBATTS.JPG

KAIAUTOVACBATTS.JPG

237 ms

NORTH904111.JPG

NORTH904111.JPG

239 ms

SCA121204.JPG

SCA121204.JPG

240 ms

SCA160090.JPG

SCA160090.JPG

241 ms

ARMS42365.JPG

ARMS42365.JPG

240 ms

SCA12024402.JPG

SCA12024402.JPG

240 ms

M2PMWSC16B.JPG

M2PMWSC16B.JPG

242 ms

SANCOCSSL3038R1BE.JPG

SANCOCSSL3038R1BE.JPG

242 ms

CERTC12504.JPG

CERTC12504.JPG

243 ms

SCAHB1995A.JPG

SCAHB1995A.JPG

249 ms

WAYNE15I-700PF.JPG

WAYNE15I-700PF.JPG

250 ms

header-logo-small.png

header-logo-small.png

62 ms

Tork.jpg

Tork.jpg

449 ms

Kaivac_2.png

Kaivac_2.png

507 ms

Edgewood.jpg

Edgewood.jpg

309 ms

Machine_Fix_2.png

Machine_Fix_2.png

214 ms

Free_Shipping_2.jpg

Free_Shipping_2.jpg

272 ms

Vendor_Spotlight.jpg

Vendor_Spotlight.jpg

287 ms

M2.png

M2.png

302 ms

Tork.jpg

Tork.jpg

290 ms

Grime_Eater.png

Grime_Eater.png

324 ms

Frost.jpg

Frost.jpg

363 ms

Kaivac.png

Kaivac.png

335 ms

Certainty.png

Certainty.png

342 ms

Dustbane.png

Dustbane.png

356 ms

Xynyth.jpg

Xynyth.jpg

350 ms

Nacecare.png

Nacecare.png

375 ms

footerlogo.png

footerlogo.png

363 ms

WwkQxPq1DFK04uqieVo.ttf

WwkQxPq1DFK04uqieVo.ttf

126 ms

fa-brands-400.ttf

fa-brands-400.ttf

150 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNRwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNRwaA.ttf

118 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFRwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexaFRwaA.ttf

131 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1RwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexc1RwaA.ttf

132 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1WwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexU1WwaA.ttf

132 ms

1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRWwaA.ttf

1Ptyg83HX_SGhgqO0yLcmjzUAuWexXRWwaA.ttf

131 ms

Accessibility Review

sanco.ca accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

sanco.ca 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sanco.ca SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Sanco.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 Sanco.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.

Social Sharing Optimization

sanco.ca

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