Tools & Wizards About Us
sterling.ca screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

sterling.ca

Sterling Marking Products Inc

Page Load Speed

4.4 sec in total

First Response

91 ms

Resources Loaded

3.3 sec

Page Rendered

969 ms

sterling.ca screenshot

About Website

Welcome to sterling.ca homepage info - get ready to check Sterling best content for Canada right away, or after learning these important things about sterling.ca

Visit sterling.ca

Key Findings

We analyzed Sterling.ca page load time and found that the first response time was 91 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

sterling.ca performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.759

6/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

sterling.ca

91 ms

www.sterling.ca

253 ms

js

128 ms

icon

108 ms

jquery-3.5.1.min.js

86 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 32% of them (27 requests) were addressed to the original Sterling.ca, 22% (19 requests) were made to Static.xx.fbcdn.net and 13% (11 requests) were made to Static.licdn.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Sterling.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (14%)

Content Size

13.9 MB

After Optimization

12.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sterling.ca main page is 13.9 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. 75% 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 13.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 37.9 kB

  • Original 50.0 kB
  • After minification 47.3 kB
  • After compression 12.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 37.9 kB or 76% of the original size.

Image Optimization

-13%

Potential reduce by 1.7 MB

  • Original 13.4 MB
  • After minification 11.7 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. Obviously, Sterling needs image optimization as it can save up to 1.7 MB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 98.0 kB

  • Original 380.2 kB
  • After minification 375.6 kB
  • After compression 282.2 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 98.0 kB or 26% of the original size.

CSS Optimization

-85%

Potential reduce by 56.9 kB

  • Original 67.1 kB
  • After minification 17.9 kB
  • After compression 10.2 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. Sterling.ca needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (65%)

Requests Now

78

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sterling.ca

sterling.ca

91 ms

www.sterling.ca

www.sterling.ca

253 ms

js

js

128 ms

icon

icon

108 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

86 ms

mui.min.css

mui.min.css

302 ms

mui.min.js

mui.min.js

463 ms

flickity.min.css

flickity.min.css

123 ms

flickity.pkgd.js

flickity.pkgd.js

288 ms

fullscreen.css

fullscreen.css

299 ms

newsite.css

newsite.css

78 ms

modernizr.custom.64700.js

modernizr.custom.64700.js

120 ms

260161.js

260161.js

285 ms

horizontal-slim-10_7.css

horizontal-slim-10_7.css

118 ms

sdk.js

sdk.js

117 ms

cmsmiscpage.js

cmsmiscpage.js

283 ms

miscpages.css

miscpages.css

354 ms

classic-061523.css

classic-061523.css

119 ms

mc-validate.js

mc-validate.js

284 ms

flickity.min.css

flickity.min.css

185 ms

flickity.pkgd.js

flickity.pkgd.js

19 ms

fullscreen.css

fullscreen.css

38 ms

fullscreen.js

fullscreen.js

22 ms

33dc94665fca31d3eb78f28be.js

33dc94665fca31d3eb78f28be.js

592 ms

fbevents.js

fbevents.js

38 ms

285b8f14b5910e2ed6a83f9e3.js

285b8f14b5910e2ed6a83f9e3.js

725 ms

phoneWhite.svg

phoneWhite.svg

38 ms

emailWhite.svg

emailWhite.svg

154 ms

instagramLogo2024.svg

instagramLogo2024.svg

152 ms

facebookLogo2024.svg

facebookLogo2024.svg

150 ms

twitterXLogo2024.svg

twitterXLogo2024.svg

152 ms

linkedinwhite.svg

linkedinwhite.svg

181 ms

sterlingLogo.svg

sterlingLogo.svg

191 ms

F244E71B-DB4E-7C70-3B1B3AED7BF14D9D.jpg

F244E71B-DB4E-7C70-3B1B3AED7BF14D9D.jpg

487 ms

5869403E-E64F-785B-0BD6279B4F6E720B.png

5869403E-E64F-785B-0BD6279B4F6E720B.png

978 ms

F38E8775-C171-DDAE-C1F42ACBB6FD2B7C.jpg

F38E8775-C171-DDAE-C1F42ACBB6FD2B7C.jpg

486 ms

863A34C1-0CAD-7CF4-EE461866976C4978.png

863A34C1-0CAD-7CF4-EE461866976C4978.png

906 ms

BF7D5CAE-CEAF-5DA8-DE8D3A100AEA2612.jpg

BF7D5CAE-CEAF-5DA8-DE8D3A100AEA2612.jpg

2126 ms

586A9737-AE69-5C5B-FC0946F8FBB0AD33.png

586A9737-AE69-5C5B-FC0946F8FBB0AD33.png

1120 ms

E4DDC799-B7B5-61C0-C2B9A5C904026396.png

E4DDC799-B7B5-61C0-C2B9A5C904026396.png

1470 ms

58961F85-EFEB-9205-5B5AC1DD40A67F81.jpg

58961F85-EFEB-9205-5B5AC1DD40A67F81.jpg

975 ms

BFDCF1F6-BF8E-FA21-A05192B940C0D765.jpg

BFDCF1F6-BF8E-FA21-A05192B940C0D765.jpg

2501 ms

1E3343EE-D963-6DB1-B06134FB1E3DEDB4.png

1E3343EE-D963-6DB1-B06134FB1E3DEDB4.png

1151 ms

4F3B3840-C667-BAF0-A8DA6172FA500B60.png

4F3B3840-C667-BAF0-A8DA6172FA500B60.png

1083 ms

SterlingLogoAllWhite.svg

SterlingLogoAllWhite.svg

1166 ms

ISO_2015c.png

ISO_2015c.png

1309 ms

urn:li:ugcPost:7118267736400527360

urn:li:ugcPost:7118267736400527360

470 ms

F2C65E5A-9CD3-2928-F9FDCE18EFC74A79.jpg

F2C65E5A-9CD3-2928-F9FDCE18EFC74A79.jpg

1406 ms

sdk.js

sdk.js

18 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

159 ms

insight.min.js

insight.min.js

82 ms

page.php

page.php

141 ms

insight_tag_errors.gif

insight_tag_errors.gif

276 ms

eOzOzediAge.css

eOzOzediAge.css

35 ms

cuPjK18RJ2t.css

cuPjK18RJ2t.css

36 ms

CAfgKYFpIyM.css

CAfgKYFpIyM.css

39 ms

VWDhCULazb5.js

VWDhCULazb5.js

46 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

42 ms

5xOV5e9oy4e.js

5xOV5e9oy4e.js

44 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

41 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

43 ms

p55HfXW__mM.js

p55HfXW__mM.js

42 ms

k_PjgALRjoR.js

k_PjgALRjoR.js

44 ms

YEtUGb-ToKw.js

YEtUGb-ToKw.js

88 ms

XKFYjgE7mEh.js

XKFYjgE7mEh.js

94 ms

g2XPN2wRGmV.js

g2XPN2wRGmV.js

87 ms

E6qR0C8WEpl.js

E6qR0C8WEpl.js

110 ms

kgAz0TBWoYE.js

kgAz0TBWoYE.js

120 ms

DPxpTcknHiI.js

DPxpTcknHiI.js

92 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

122 ms

417160287_865721655556477_5693701901935447962_n.jpg

417160287_865721655556477_5693701901935447962_n.jpg

72 ms

u2HYktv2mdq.js

u2HYktv2mdq.js

24 ms

277570411_395578102570837_1942842682469134619_n.jpg

277570411_395578102570837_1942842682469134619_n.jpg

49 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

18 ms

bcx4beo10riihklw4yz9ixck6

bcx4beo10riihklw4yz9ixck6

45 ms

eh08muqvrde4h3hc6koyij5ti

eh08muqvrde4h3hc6koyij5ti

86 ms

98zyzym0uwq9e7pvgq4vk1j9t

98zyzym0uwq9e7pvgq4vk1j9t

103 ms

51paimf5863zz4wq4efe56why

51paimf5863zz4wq4efe56why

34 ms

3g68cnardz6vbv25s4xdglixo

3g68cnardz6vbv25s4xdglixo

42 ms

469pk4qwqr71px3afmm9prany

469pk4qwqr71px3afmm9prany

59 ms

7frb88uumrn0jl7oiyofxthci

7frb88uumrn0jl7oiyofxthci

57 ms

73lwy6uyd30a5j4qmibmkeu3u

73lwy6uyd30a5j4qmibmkeu3u

61 ms

6q2ztc8el1ffd1w46cwwgr95d

6q2ztc8el1ffd1w46cwwgr95d

55 ms

c0tu4fqjzwahww3f3kaxjvd1e

c0tu4fqjzwahww3f3kaxjvd1e

44 ms

47d6m6cqlp1rwpmpk2rodukxv

47d6m6cqlp1rwpmpk2rodukxv

60 ms

Accessibility Review

sterling.ca accessibility score

75

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

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

High

<html> element does not have a [lang] attribute

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

sterling.ca SEO score

72

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sterling.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 Sterling.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

sterling.ca

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