Tools & Wizards About Us
oto.ai screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

oto.ai

OTO Systems | AI-powered Voice Intelligence

Page Load Speed

990 ms in total

First Response

79 ms

Resources Loaded

820 ms

Page Rendered

91 ms

oto.ai screenshot

About Website

Click here to check amazing OTO content for Mexico. Otherwise, check out these important facts you probably never knew about oto.ai

OTO Systems - DeepTone™ understands key human behaviors and sounds in real-time providing you with a rich acoustic map of your voice data.

Visit oto.ai

Key Findings

We analyzed Oto.ai page load time and found that the first response time was 79 ms and then it took 911 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

oto.ai performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

oto.ai

79 ms

www.oto.ai

235 ms

oto-current.webflow.183871e49.min.css

103 ms

webfont.js

48 ms

api.js

64 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Oto.ai, 22% (4 requests) were made to Uploads-ssl.webflow.com and 17% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (235 ms) belongs to the original domain Oto.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 317.0 kB (33%)

Content Size

956.0 kB

After Optimization

639.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oto.ai main page is 956.0 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. 25% of websites need less resources to load. Javascripts take 697.9 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 7.0 kB

  • Original 10.5 kB
  • After minification 10.1 kB
  • After compression 3.5 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 7.0 kB or 67% of the original size.

Image Optimization

-3%

Potential reduce by 6.5 kB

  • Original 197.1 kB
  • After minification 190.7 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. OTO images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 303.5 kB

  • Original 697.9 kB
  • After minification 697.9 kB
  • After compression 394.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 303.5 kB or 43% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 50.5 kB
  • After minification 50.5 kB
  • After compression 50.5 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. Oto.ai has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (58%)

Requests Now

12

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oto.ai

oto.ai

79 ms

www.oto.ai

www.oto.ai

235 ms

oto-current.webflow.183871e49.min.css

oto-current.webflow.183871e49.min.css

103 ms

webfont.js

webfont.js

48 ms

api.js

api.js

64 ms

stub.js

stub.js

64 ms

iubenda_cs.js

iubenda_cs.js

72 ms

jquery-3.5.1.min.dc5e7f18c8.js

jquery-3.5.1.min.dc5e7f18c8.js

55 ms

webflow.63e8d386a.js

webflow.63e8d386a.js

63 ms

api.js

api.js

86 ms

css

css

30 ms

recaptcha__en.js

recaptcha__en.js

161 ms

5eb33d3270be2a0239a687bd_Logo_OTO_white.png

5eb33d3270be2a0239a687bd_Logo_OTO_white.png

142 ms

61c33e0644b75c0ce82de4ff_U_Logo_White_RGB.png

61c33e0644b75c0ce82de4ff_U_Logo_White_RGB.png

88 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3z.ttf

91 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRSW3z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRSW3z.ttf

95 ms

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRSW3z.ttf

rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRSW3z.ttf

98 ms

835b06006f3446099e054b756526e82fa3774824b127462b959f5a3c33e9280e

835b06006f3446099e054b756526e82fa3774824b127462b959f5a3c33e9280e

116 ms

Accessibility Review

oto.ai accessibility score

88

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.

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

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

oto.ai 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

oto.ai 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

    N/A

  • Encoding

    UTF-8

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

oto.ai

Open Graph data is detected on the main page of OTO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: