4.7 sec in total
166 ms
3.6 sec
933 ms
Visit odus.ai now to see the best up-to-date Odus content for India and also check out these interesting facts you probably never knew about odus.ai
Replace sales and support team with the intelligent assistant! Automate customer service around the clock anywhere.
Visit odus.aiWe analyzed Odus.ai page load time and found that the first response time was 166 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
odus.ai performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value15.7 s
0/100
25%
Value14.9 s
1/100
10%
Value10,930 ms
0/100
30%
Value0.04
99/100
15%
Value22.5 s
1/100
10%
166 ms
43 ms
30 ms
50 ms
78 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 40% of them (40 requests) were addressed to the original Odus.ai, 9% (9 requests) were made to Maps.googleapis.com and 8% (8 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Vk.com.
Page size can be reduced by 911.7 kB (69%)
1.3 MB
401.7 kB
In fact, the total size of Odus.ai main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 685.6 kB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 21% 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 63.7 kB or 79% of the original size.
Potential reduce by 487 B
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. Odus images are well optimized though.
Potential reduce by 393.2 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 393.2 kB or 57% of the original size.
Potential reduce by 454.3 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. Odus.ai needs all CSS files to be minified and compressed as it can save up to 454.3 kB or 87% of the original size.
Number of requests can be reduced by 67 (75%)
89
22
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
odus.ai
166 ms
odus.ai
43 ms
style.css
30 ms
main.css
50 ms
animate.css
78 ms
nprogress.css
78 ms
modernizr-2.6.2.min.js
85 ms
jquery-3.3.1.min.js
74 ms
jquery.easing.1.3.js
46 ms
jquery.waypoints.min.js
83 ms
modernizr-custom.js
83 ms
svg4everybody.min.js
453 ms
picturefill.min.js
452 ms
stickyfill.min.js
453 ms
lazysizes.min.js
282 ms
slick.min.js
453 ms
bootstrap.min.js
452 ms
video.js
449 ms
jquery.translate.js
455 ms
scripts.min.js
473 ms
nprogress.js
473 ms
main.js
472 ms
index.js
472 ms
translate.js
472 ms
6708583.js
674 ms
gtm.js
652 ms
gtm.js
739 ms
fbevents.js
526 ms
fs_GtbgsDEA
727 ms
embed
811 ms
logo.png
289 ms
bg-balloon.png
396 ms
svg.svg
293 ms
svg.svg
292 ms
svg.svg
396 ms
noto-sans-v9-latin-regular.woff
281 ms
MontserratBold.woff
284 ms
MontserratSemiBold.woff
287 ms
MontserratMedium.woff
287 ms
MontserratRegular.woff
353 ms
svg.svg
127 ms
svg.svg
124 ms
svg.svg
276 ms
6708583.js
342 ms
collectedforms.js
455 ms
6708583.js
343 ms
143371373051214
180 ms
conversion_async.js
210 ms
insight.min.js
362 ms
www-player.css
158 ms
www-embed-player.js
296 ms
base.js
424 ms
fetch-polyfill.js
222 ms
240 ms
1346242738814468
131 ms
js
234 ms
analytics.js
225 ms
tag.js
1070 ms
openapi.js
1600 ms
685 ms
299740834198450
631 ms
332 ms
json
725 ms
insight.beta.min.js
393 ms
collect
518 ms
init_embed.js
592 ms
ad_status.js
584 ms
36t2pzUCsky2p8StOfRDuZ2SQrRQGkwFUvrIpVyovYo.js
396 ms
embed.js
324 ms
collect
439 ms
id
227 ms
171 ms
67 ms
314963249104403
155 ms
common.js
132 ms
util.js
427 ms
map.js
427 ms
google4.png
366 ms
overlay.js
402 ms
KFOmCnqEu92Fr1Mu4mxM.woff
470 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
472 ms
onion.js
377 ms
search_impl.js
376 ms
282 ms
103 ms
103 ms
rtrg
155 ms
14 ms
102 ms
openhand_8_8.cur
102 ms
kh
84 ms
ViewportInfoService.GetViewportInfo
100 ms
ViewportInfoService.GetViewportInfo
53 ms
counters.gif
81 ms
28 ms
__ptq.gif
160 ms
Builder.png
70 ms
Builder_2.png
69 ms
Builder_3.png
67 ms
odus.ai accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
odus.ai best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
odus.ai SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odus.ai 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 Odus.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.
odus.ai
Open Graph data is detected on the main page of Odus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: