Tools & Wizards About Us
krylon.ca screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

krylon.ca

ColorMaster, Dual Paint & Primer, Glitter Blast & Rust Protector | Krylon

Page Load Speed

1.2 sec in total

First Response

66 ms

Resources Loaded

915 ms

Page Rendered

267 ms

krylon.ca screenshot

About Website

Visit krylon.ca now to see the best up-to-date Krylon content for Canada and also check out these interesting facts you probably never knew about krylon.ca

Trust Krylon spray paints like ColorMaster, Dual Paint & Primer, Glitter Blast and Rust Protector for your craft or DIY spray paint project. View products now.

Visit krylon.ca

Key Findings

We analyzed Krylon.ca page load time and found that the first response time was 66 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

krylon.ca performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

krylon.ca

66 ms

canadian-products

177 ms

ruxitagentjs_ICA7NVfqrux_10297240712040816.js

36 ms

ruxitagentjs_ICANVfqru_10295240705110949.js

83 ms

Bootstrap.js

22 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Krylon.ca, 59% (24 requests) were made to Krylon.com and 12% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (375 ms) relates to the external source Krylon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.3 kB (16%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Krylon.ca main page is 2.0 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. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 54.6 kB

  • Original 65.6 kB
  • After minification 54.6 kB
  • After compression 11.0 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 11.0 kB, which is 17% 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 54.6 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 50.2 kB

  • Original 1.5 MB
  • After minification 1.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. Krylon images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 221.5 kB

  • Original 408.9 kB
  • After minification 408.9 kB
  • After compression 187.4 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 221.5 kB or 54% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.8 kB
  • After minification 59.8 kB
  • After compression 59.8 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. Krylon.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (70%)

Requests Now

30

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krylon. 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.

Network Requests Diagram

krylon.ca

krylon.ca

66 ms

canadian-products

canadian-products

177 ms

ruxitagentjs_ICA7NVfqrux_10297240712040816.js

ruxitagentjs_ICA7NVfqrux_10297240712040816.js

36 ms

ruxitagentjs_ICANVfqru_10295240705110949.js

ruxitagentjs_ICANVfqru_10295240705110949.js

83 ms

Bootstrap.js

Bootstrap.js

22 ms

clientlib-base.min.css

clientlib-base.min.css

64 ms

css2

css2

33 ms

clientlib-site.min.css

clientlib-site.min.css

24 ms

clientlib-base.min.css

clientlib-base.min.css

74 ms

clientlib-site.min.css

clientlib-site.min.css

123 ms

skiptomaincontent.min.css

skiptomaincontent.min.css

71 ms

clientlib-site.min.js

clientlib-site.min.js

167 ms

container.min.js

container.min.js

120 ms

clientlib-base.min.js

clientlib-base.min.js

168 ms

clientlib-site.min.js

clientlib-site.min.js

166 ms

clientlib-base.min.js

clientlib-base.min.js

166 ms

site.js

site.js

40 ms

gtm.js

gtm.js

104 ms

HP8SE-EUBBG-QA8KX-3GK7K-LRAHV

HP8SE-EUBBG-QA8KX-3GK7K-LRAHV

136 ms

wBXPzB9HzYk

wBXPzB9HzYk

120 ms

krylon-logo-lozenge-rgb.png

krylon-logo-lozenge-rgb.png

56 ms

krylon-canada-m3.jpg

krylon-canada-m3.jpg

57 ms

krylon-canadian-hero-d.jpg

krylon-canadian-hero-d.jpg

375 ms

krylon-logo-lozenge-rgb.png

krylon-logo-lozenge-rgb.png

374 ms

IBMPlexSans-Light.ttf

IBMPlexSans-Light.ttf

34 ms

AvenirNextLTPro-Medium.ttf

AvenirNextLTPro-Medium.ttf

56 ms

GeorgiaPro-CondBlack.ttf

GeorgiaPro-CondBlack.ttf

33 ms

AvenirNextLTPro-Bold.ttf

AvenirNextLTPro-Bold.ttf

34 ms

AvenirNextLTPro-Regular.ttf

AvenirNextLTPro-Regular.ttf

33 ms

GeorgiaPro-Bold.ttf

GeorgiaPro-Bold.ttf

59 ms

IBMPlexSans-Regular.ttf

IBMPlexSans-Regular.ttf

168 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

56 ms

config.json

config.json

253 ms

ad_status.js

ad_status.js

133 ms

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

L24uOtqvNfFRO5TOxiIOVgM50wph5QKjT82e9pNVgC0.js

98 ms

embed.js

embed.js

36 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

45 ms

id

id

20 ms

Accessibility Review

krylon.ca accessibility score

63

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

[role]s do not have all required [aria-*] attributes

High

ARIA IDs 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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

Missing source maps for large first-party JavaScript

SEO Factors

krylon.ca SEO score

75

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

Crawling and Indexing

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

Impact

Issue

High

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

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

krylon.ca

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