Tools & Wizards About Us
otodata.ca screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

otodata.ca

Otodata | Your connection to the internet of things

Page Load Speed

3.8 sec in total

First Response

82 ms

Resources Loaded

3.6 sec

Page Rendered

100 ms

otodata.ca screenshot

About Website

Visit otodata.ca now to see the best up-to-date Otodata content for United States and also check out these interesting facts you probably never knew about otodata.ca

We've raised the bar, so why continue to play catch-up with an ever changing cellular network? Let us show you where the industry is going.

Visit otodata.ca

Key Findings

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

otodata.ca performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.074

95/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

otodata.ca

82 ms

1531 ms

wp-emoji-release.min.js

89 ms

counter.css

97 ms

style.css

96 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 86% of them (32 requests) were addressed to the original Otodata.ca, 5% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Otodata.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.1 kB (57%)

Content Size

904.2 kB

After Optimization

385.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otodata.ca main page is 904.2 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. 30% of websites need less resources to load. Javascripts take 375.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 13.5 kB

  • Original 18.6 kB
  • After minification 17.8 kB
  • After compression 5.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 13.5 kB or 73% of the original size.

Image Optimization

-13%

Potential reduce by 35.4 kB

  • Original 276.7 kB
  • After minification 241.3 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. Obviously, Otodata needs image optimization as it can save up to 35.4 kB 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

-71%

Potential reduce by 264.6 kB

  • Original 375.2 kB
  • After minification 373.7 kB
  • After compression 110.7 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 264.6 kB or 71% of the original size.

CSS Optimization

-88%

Potential reduce by 205.7 kB

  • Original 233.7 kB
  • After minification 157.4 kB
  • After compression 28.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. Otodata.ca needs all CSS files to be minified and compressed as it can save up to 205.7 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (59%)

Requests Now

32

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

otodata.ca

otodata.ca

82 ms

1531 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

89 ms

counter.css

counter.css

97 ms

style.css

style.css

96 ms

jquery.js

jquery.js

126 ms

jquery-migrate.min.js

jquery-migrate.min.js

85 ms

flipcounter.min.js

flipcounter.min.js

143 ms

widgetkit-c44befdb.css

widgetkit-c44befdb.css

142 ms

widgetkit-497513a5.js

widgetkit-497513a5.js

154 ms

theme.css

theme.css

191 ms

custom.css

custom.css

140 ms

uikit.js

uikit.js

165 ms

autocomplete.js

autocomplete.js

167 ms

search.js

search.js

199 ms

tooltip.js

tooltip.js

170 ms

social.js

social.js

179 ms

theme.js

theme.js

205 ms

circlechart.js

circlechart.js

221 ms

entrymetastyle.css

entrymetastyle.css

185 ms

wp-embed.min.js

wp-embed.min.js

196 ms

lightbox.js

lightbox.js

151 ms

mediaelement-and-player.js

mediaelement-and-player.js

189 ms

spotlight.js

spotlight.js

148 ms

css

css

39 ms

embed

embed

241 ms

logo.png

logo.png

68 ms

logo2.png

logo2.png

73 ms

Screenshot%202023-02-08%20at%202.59.24%20PM-da6cf513d7.png

Screenshot%202023-02-08%20at%202.59.24%20PM-da6cf513d7.png

67 ms

Screenshot%202023-02-08%20at%203.00.02%20PM-b7803c5e85.png

Screenshot%202023-02-08%20at%203.00.02%20PM-b7803c5e85.png

97 ms

slideset.js

slideset.js

70 ms

close.png

close.png

46 ms

blank.gif

blank.gif

46 ms

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

20 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

26 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

71 ms

js

js

39 ms

Accessibility Review

otodata.ca accessibility score

79

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.

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

<frame> or <iframe> elements do not have a title

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

otodata.ca best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

otodata.ca SEO score

93

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

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

otodata.ca

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