1.7 sec in total
47 ms
780 ms
854 ms
Click here to check amazing Vid Ly content. Otherwise, check out these important facts you probably never knew about vidly.com
Video player, transcoding, device detection, and delivery...
Visit vidly.comWe analyzed Vidly.com page load time and found that the first response time was 47 ms and then it took 1.6 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.
vidly.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value8.1 s
2/100
25%
Value3.9 s
82/100
10%
Value20 ms
100/100
30%
Value0.148
76/100
15%
Value6.5 s
59/100
10%
47 ms
25 ms
59 ms
64 ms
49 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Vidly.com, 6% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Static.olark.com. The less responsive or slowest element that took the longest time to load (399 ms) relates to the external source Vid.ly.
Page size can be reduced by 341.1 kB (41%)
827.3 kB
486.2 kB
In fact, the total size of Vidly.com main page is 827.3 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. 60% of websites need less resources to load. Images take 557.1 kB which makes up the majority of the site volume.
Potential reduce by 33.9 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 8.2 kB, which is 18% 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 33.9 kB or 76% of the original size.
Potential reduce by 165.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. Obviously, Vid Ly needs image optimization as it can save up to 165.7 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 84.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 84.7 kB or 54% of the original size.
Potential reduce by 56.8 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. Vidly.com needs all CSS files to be minified and compressed as it can save up to 56.8 kB or 84% of the original size.
Number of requests can be reduced by 26 (40%)
65
39
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vid Ly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
m.vid.ly
47 ms
css
25 ms
default.css
59 ms
vidly.css
64 ms
vidly-new.css
49 ms
jquery.min.js
28 ms
plugins.js
114 ms
script.js
42 ms
ZeroClipboard.min.js
125 ms
homepage.js
115 ms
jScrollPane.js
115 ms
tabs.js
128 ms
utils.js
117 ms
step.js
117 ms
upload.js
118 ms
script.js
118 ms
embeded.html
58 ms
header-border.gif
189 ms
vidly-logo.png
195 ms
from-enc.png
190 ms
free.png
183 ms
free-face.png
192 ms
vidly-logo-small.png
187 ms
selected-tick.png
190 ms
icon-time.png
194 ms
icon-phone.png
194 ms
icon-chat.png
201 ms
icon-free.png
194 ms
intro-header-ico.png
197 ms
intro-header-sup.png
195 ms
intro-players.png
197 ms
player-logo-jw-2.png
198 ms
readmore-arrow.png
208 ms
player-logo-flow.png
199 ms
player-logo-vidly.png
200 ms
signuprow-header-ico.png
201 ms
transcoding.gif
202 ms
cdn.gif
202 ms
link-arrow.png
201 ms
detection.gif
204 ms
api.png
204 ms
vidly-ui.jpg
205 ms
my-dad.png
201 ms
embed-image.gif
205 ms
or-use-vidly-com.png
203 ms
lockdown.gif
204 ms
qrcode.gif
206 ms
hls.gif
201 ms
customize.gif
248 ms
video-email.gif
201 ms
cc_lib.js
196 ms
ga_js.php
399 ms
loader0.js
173 ms
ga.js
166 ms
webvtt.js
38 ms
device-stats.gif
78 ms
_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf
80 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
82 ms
OsJ2DjdpjqFRVUSto6IffKCWcynf_cDxXwCLxiixG1c.ttf
85 ms
0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf
84 ms
html5-logo.png
78 ms
browsers.jpg
79 ms
twitter.gif
80 ms
fb.gif
75 ms
edc-logo.gif
69 ms
film.gif
74 ms
__utm.gif
30 ms
8619-313-10-2055.js
53 ms
vjs.css
3 ms
application2.js
109 ms
vidly.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
vidly.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
vidly.com 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
Image elements do not have [alt] attributes
Document uses plugins
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vidly.com 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 Vidly.com 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.
vidly.com
Open Graph description is not detected on the main page of Vid Ly. 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: