Tools & Wizards About Us
vdo.ai screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

vdo.ai

Redefining Video Advertising Across All Platforms | VDO.AI

Page Load Speed

1.4 sec in total

First Response

107 ms

Resources Loaded

795 ms

Page Rendered

531 ms

vdo.ai screenshot

About Website

Click here to check amazing VDO content for India. Otherwise, check out these important facts you probably never knew about vdo.ai

VDO.AI helps achieve enhanced brand awareness via video advertising solutions that capture consumer attention across all screens and all streams.

Visit vdo.ai

Key Findings

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

Performance Metrics

vdo.ai performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

vdo.ai

107 ms

vdo.ai

55 ms

www.vdo.ai

75 ms

a54cf9bf3948ffcf.css

16 ms

7c735c05af084bb2.css

26 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that all of those requests were addressed to Vdo.ai and no external sources were called. The less responsive or slowest element that took the longest time to load (403 ms) belongs to the original domain Vdo.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.1 kB (2%)

Content Size

1.1 MB

After Optimization

1.1 MB

  • HTML
  • Images

In fact, the total size of Vdo.ai main page is 1.1 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 26.1 kB

  • Original 33.6 kB
  • After minification 33.6 kB
  • After compression 7.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 26.1 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.1 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. VDO images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 13 (36%)

Requests Now

36

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vdo.ai

vdo.ai

107 ms

vdo.ai

vdo.ai

55 ms

www.vdo.ai

www.vdo.ai

75 ms

a54cf9bf3948ffcf.css

a54cf9bf3948ffcf.css

16 ms

7c735c05af084bb2.css

7c735c05af084bb2.css

26 ms

8c821440ae150976.css

8c821440ae150976.css

25 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

71 ms

webpack-2b948159e288f005.js

webpack-2b948159e288f005.js

43 ms

framework-2c79e2a64abdb08b.js

framework-2c79e2a64abdb08b.js

51 ms

main-74c4d6b2b5c362f3.js

main-74c4d6b2b5c362f3.js

42 ms

_app-a7a2cafbe6f8f7a2.js

_app-a7a2cafbe6f8f7a2.js

47 ms

d6e1aeb5-09f10c7c30224c12.js

d6e1aeb5-09f10c7c30224c12.js

49 ms

31-9a27375ff630380c.js

31-9a27375ff630380c.js

50 ms

965-71421c8b5fcab730.js

965-71421c8b5fcab730.js

50 ms

945-d65994d7a96e3bee.js

945-d65994d7a96e3bee.js

53 ms

451-124c372831268797.js

451-124c372831268797.js

57 ms

247-7e5552b2b088081f.js

247-7e5552b2b088081f.js

54 ms

index-c6e262b77c4e866d.js

index-c6e262b77c4e866d.js

53 ms

_buildManifest.js

_buildManifest.js

53 ms

_ssgManifest.js

_ssgManifest.js

57 ms

close-white.svg

close-white.svg

119 ms

logoBlack.svg

logoBlack.svg

131 ms

dexter.svg

dexter.svg

115 ms

advertiser-ctv.svg

advertiser-ctv.svg

120 ms

online-video.svg

online-video.svg

119 ms

native.svg

native.svg

121 ms

web.svg

web.svg

139 ms

mobile.svg

mobile.svg

138 ms

publisher-ctv.svg

publisher-ctv.svg

146 ms

image

image

180 ms

image

image

215 ms

image

image

225 ms

image

image

222 ms

image

image

216 ms

image

image

229 ms

image

image

207 ms

GCPP.svg

GCPP.svg

403 ms

hero.png

hero.png

380 ms

hero-flipped.png

hero-flipped.png

381 ms

Metropolis-SemiBold.woff

Metropolis-SemiBold.woff

78 ms

Metropolis-Bold.woff

Metropolis-Bold.woff

77 ms

Metropolis-ExtraBold.woff

Metropolis-ExtraBold.woff

76 ms

Metropolis-Black.woff

Metropolis-Black.woff

77 ms

Metropolis-Medium.woff

Metropolis-Medium.woff

78 ms

Metropolis-Regular.woff

Metropolis-Regular.woff

46 ms

Metropolis-Light.woff

Metropolis-Light.woff

112 ms

Metropolis-ExtraLight.woff

Metropolis-ExtraLight.woff

113 ms

Metropolis-Thin.woff

Metropolis-Thin.woff

112 ms

Accessibility Review

vdo.ai accessibility score

94

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

vdo.ai SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

vdo.ai

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