Tools & Wizards About Us
cavr.ca screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

cavr.ca

CAVR - Canadian VR Company | Virtual and Augmented Reality Production in Toronto

Page Load Speed

4.1 sec in total

First Response

1.1 sec

Resources Loaded

2.3 sec

Page Rendered

601 ms

cavr.ca screenshot

About Website

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

Visit cavr.ca

Key Findings

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

Performance Metrics

cavr.ca performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

Network Requests Diagram

cavr.ca

1144 ms

magnific-popup.min.css

102 ms

core.min.css

103 ms

css

31 ms

style.min.css

67 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 43% of them (26 requests) were addressed to the original Cavr.ca, 45% (27 requests) were made to Cavr.maximkhasiev.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Cavr.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.1 kB (8%)

Content Size

4.0 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cavr.ca main page is 4.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. 70% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 218.3 kB

  • Original 253.5 kB
  • After minification 247.4 kB
  • After compression 35.2 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 218.3 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 109.3 kB

  • Original 3.5 MB
  • After minification 3.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. CAVR images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 217.3 kB
  • After minification 217.3 kB
  • After compression 214.1 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

-1%

Potential reduce by 291 B

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

Requests Breakdown

Number of requests can be reduced by 24 (45%)

Requests Now

53

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAVR. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cavr.ca

cavr.ca

1144 ms

magnific-popup.min.css

magnific-popup.min.css

102 ms

core.min.css

core.min.css

103 ms

css

css

31 ms

style.min.css

style.min.css

67 ms

css

css

13 ms

cavr_logo_contrast2.png

cavr_logo_contrast2.png

348 ms

main_page_top_100bqs.png

main_page_top_100bqs.png

616 ms

Frame-4795.png

Frame-4795.png

569 ms

Frame-1321314811.png

Frame-1321314811.png

568 ms

sharelogo.png

sharelogo.png

418 ms

mercedes-2.jpg

mercedes-2.jpg

414 ms

redbull.jpg

redbull.jpg

417 ms

tricon.png

tricon.png

417 ms

ibm.jpg

ibm.jpg

420 ms

bayer.jpg

bayer.jpg

421 ms

absolut.jpg

absolut.jpg

421 ms

jimbeam.jpg

jimbeam.jpg

448 ms

VK_Compact_Logo_2021-present.svg-150x150.png

VK_Compact_Logo_2021-present.svg-150x150.png

448 ms

mobweb03.png

mobweb03.png

566 ms

1-1-1-1024x864-1.png

1-1-1-1024x864-1.png

627 ms

stacked1.png

stacked1.png

568 ms

web-icon-light-bulb.png

web-icon-light-bulb.png

568 ms

web-icon-design.png

web-icon-design.png

569 ms

web-icon-adjust.png

web-icon-adjust.png

569 ms

web-icon-code.png

web-icon-code.png

570 ms

headset-tablet-metaverse-technology-concept-3d-rendering-1-2.png

headset-tablet-metaverse-technology-concept-3d-rendering-1-2.png

610 ms

1923819283-2.png

1923819283-2.png

624 ms

cavr_logo.png

cavr_logo.png

611 ms

slick.min.css

slick.min.css

34 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

139 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

165 ms

jquery.min.js

jquery.min.js

166 ms

jquery-migrate.min.js

jquery-migrate.min.js

166 ms

magnific-popup.js

magnific-popup.js

198 ms

main.min.js

main.min.js

210 ms

dtq-default-vb.js

dtq-default-vb.js

221 ms

scripts.min.js

scripts.min.js

241 ms

jquery.fitvids.js

jquery.fitvids.js

220 ms

easypiechart.js

easypiechart.js

220 ms

salvattore.js

salvattore.js

230 ms

frontend-bundle.min.js

frontend-bundle.min.js

254 ms

common.js

common.js

258 ms

slick.min.js

slick.min.js

268 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

385 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

268 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

274 ms

motion-effects.js

motion-effects.js

387 ms

et-divi-dynamic-3977-late.css

et-divi-dynamic-3977-late.css

245 ms

web-dev-03.png

web-dev-03.png

534 ms

web-dev-05.png

web-dev-05.png

535 ms

web-dev-24.png

web-dev-24.png

545 ms

main_bg.jpg

main_bg.jpg

553 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

59 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

92 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

93 ms

modules.ttf

modules.ttf

249 ms

style.min.css

style.min.css

73 ms

Accessibility Review

cavr.ca accessibility score

86

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

cavr.ca best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cavr.ca SEO score

84

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

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

cavr.ca

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