Tools & Wizards About Us
w-r.ca screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

w-r.ca

Western Refrigeration – & Beverage Equipment Ltd.

Page Load Speed

4.1 sec in total

First Response

38 ms

Resources Loaded

3.7 sec

Page Rendered

392 ms

w-r.ca screenshot

About Website

Click here to check amazing W R content. Otherwise, check out these important facts you probably never knew about w-r.ca

Since 1946 Western Refrigeration and Beverage Equipment Ltd. has been a leading Canadian Commercial Foodservice Equipment Distributor. Our National distribution network includes warehousing both in We...

Visit w-r.ca

Key Findings

We analyzed W-r.ca page load time and found that the first response time was 38 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

w-r.ca performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.2 s

75/100

10%

Network Requests Diagram

w-r.ca

38 ms

wr.ca

375 ms

webfont.js

15 ms

style.css

88 ms

theme.css

86 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original W-r.ca, 43% (23 requests) were made to Wr.ca and 17% (9 requests) were made to Fonts.wp.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source I2.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.7 kB (14%)

Content Size

642.4 kB

After Optimization

549.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of W-r.ca main page is 642.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 388.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 60.7 kB

  • Original 76.4 kB
  • After minification 74.7 kB
  • After compression 15.7 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 60.7 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 23.2 kB

  • Original 388.1 kB
  • After minification 364.8 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. W R images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 6.0 kB

  • Original 121.4 kB
  • After minification 121.4 kB
  • After compression 115.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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 2.7 kB

  • Original 56.5 kB
  • After minification 56.5 kB
  • After compression 53.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. W-r.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (73%)

Requests Now

41

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

w-r.ca

w-r.ca

38 ms

wr.ca

wr.ca

375 ms

webfont.js

webfont.js

15 ms

style.css

style.css

88 ms

theme.css

theme.css

86 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

140 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

141 ms

themicons.css

themicons.css

104 ms

style.css

style.css

115 ms

css

css

157 ms

jetpack.css

jetpack.css

113 ms

jetpack.css

jetpack.css

120 ms

jquery.min.js

jquery.min.js

140 ms

jquery-migrate.min.js

jquery-migrate.min.js

144 ms

fitie.js

fitie.js

134 ms

bilmur.min.js

bilmur.min.js

147 ms

image-cdn.js

image-cdn.js

133 ms

appendaround.js

appendaround.js

134 ms

wp-nav-menus.js

wp-nav-menus.js

142 ms

main.js

main.js

141 ms

header.js

header.js

141 ms

e-202410.js

e-202410.js

144 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

137 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

140 ms

wp-polyfill.min.js

wp-polyfill.min.js

143 ms

index.min.js

index.min.js

140 ms

index.min.js

index.min.js

143 ms

index.min.js

index.min.js

143 ms

index.min.js

index.min.js

144 ms

wp-custom-header.min.js

wp-custom-header.min.js

140 ms

index.min.js

index.min.js

147 ms

view.js

view.js

146 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

146 ms

css

css

149 ms

WEBSITE-HEADER-2.jpg

WEBSITE-HEADER-2.jpg

76 ms

WEBSITE-SLIDE-1_REACH-INS-1.jpg

WEBSITE-SLIDE-1_REACH-INS-1.jpg

81 ms

WR-Website-Footer2-1.jpg

WR-Website-Footer2-1.jpg

3110 ms

WEBSITE-SLIDE-2_ICE-MACHINES-1.jpg

WEBSITE-SLIDE-2_ICE-MACHINES-1.jpg

51 ms

WEBSITE-SLIDE-3_BEVERAGE-1.jpg

WEBSITE-SLIDE-3_BEVERAGE-1.jpg

79 ms

WEBSITE-SLIDE-4_COOLERS-1.jpg

WEBSITE-SLIDE-4_COOLERS-1.jpg

77 ms

WEBSITE-SLIDE-5_ICE-CREAM-1.jpg

WEBSITE-SLIDE-5_ICE-CREAM-1.jpg

78 ms

WEBSITE-SLIDE-6_ATOSA-1.jpg

WEBSITE-SLIDE-6_ATOSA-1.jpg

78 ms

WEBSITE-SLIDE-7_FREEZERS-1.jpg

WEBSITE-SLIDE-7_FREEZERS-1.jpg

76 ms

WEBSITE-SLIDE_LAST-1.jpg

WEBSITE-SLIDE_LAST-1.jpg

75 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

81 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf

85 ms

j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw4iZmqXNRA.ttf

j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw4iZmqXNRA.ttf

102 ms

j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw7FYWqXNRA.ttf

j8_96_fAw7jrcalD7oKYNX0QfAnPcbzNEEB7OoicBw7FYWqXNRA.ttf

102 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf

101 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf

100 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDc.ttf

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDc.ttf

100 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18E.ttf

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18E.ttf

99 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

103 ms

themicons.woff

themicons.woff

32 ms

Accessibility Review

w-r.ca accessibility score

90

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

w-r.ca best practices score

92

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

Page has valid source maps

SEO Factors

w-r.ca SEO score

100

Search Engine Optimization Advices

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

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 W-r.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 W-r.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

w-r.ca

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