5.5 sec in total
424 ms
4.8 sec
236 ms
Visit m.otd.to now to see the best up-to-date M Otd content for India and also check out these interesting facts you probably never knew about m.otd.to
OTD is a place for people to discover and share content from anywhere on the web.
Visit m.otd.toWe analyzed M.otd.to page load time and found that the first response time was 424 ms and then it took 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.
m.otd.to performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value8.1 s
2/100
25%
Value11.5 s
5/100
10%
Value750 ms
39/100
30%
Value0.012
100/100
15%
Value8.0 s
43/100
10%
424 ms
630 ms
383 ms
127 ms
59 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original M.otd.to, 19% (15 requests) were made to Cdn.owebhost.eu and 13% (10 requests) were made to Analytics.otd.to. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Analytics.otd.to.
Page size can be reduced by 983.0 kB (66%)
1.5 MB
509.0 kB
In fact, the total size of M.otd.to main page is 1.5 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. 70% of websites need less resources to load. Javascripts take 855.1 kB which makes up the majority of the site volume.
Potential reduce by 146.8 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 146.8 kB or 77% of the original size.
Potential reduce by 2.4 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. M Otd images are well optimized though.
Potential reduce by 587.3 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 587.3 kB or 69% of the original size.
Potential reduce by 246.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. M.otd.to needs all CSS files to be minified and compressed as it can save up to 246.5 kB or 83% of the original size.
Number of requests can be reduced by 39 (51%)
76
37
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Otd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
m.otd.to
424 ms
www.otd.to
630 ms
style.css
383 ms
jquery.dropdown.js
127 ms
jquery.min.js
59 ms
jquery-ui.min.js
9 ms
jquery.min.js
83 ms
pay-now-button.js
56 ms
platform.js
99 ms
pr.js
507 ms
xmlhttp.php
263 ms
r.js
444 ms
addthis_widget.js
37 ms
prum.min.js
11 ms
otd-sky-bg.jpg
14 ms
search-bg.png
525 ms
sign_in.png
212 ms
light-gradient.png
212 ms
otdto-logo-s.png
210 ms
signin.png
221 ms
signup.png
311 ms
sign-in.png
212 ms
donate_64.png
31 ms
share.png
61 ms
facebook.png
30 ms
twitter.png
29 ms
google.png
14 ms
reddit.png
8 ms
linkedin.png
29 ms
stumbleupon.png
28 ms
tumblr.png
30 ms
delicious.png
38 ms
newsvine.png
33 ms
email.png
30 ms
rssfeed.png
31 ms
otdto-32x32.png
34 ms
topbar.png
33 ms
loading-large.gif
58 ms
all.js
55 ms
widgets.js
95 ms
pr.png
234 ms
piwik.js
429 ms
cb=gapi.loaded_0
92 ms
cb=gapi.loaded_1
124 ms
fastbutton
242 ms
index.php
608 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
106 ms
175 ms
like.php
206 ms
xd_arbiter.php
99 ms
xd_arbiter.php
229 ms
postmessageRelay
192 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
66 ms
cb=gapi.loaded_0
71 ms
cb=gapi.loaded_1
71 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
152 ms
info.json
144 ms
vpc6VNjRPXV.js
108 ms
LVx-xkvaJ0b.png
116 ms
xd_arbiter.php
32 ms
api.js
44 ms
core:rpc:shindig.random:shindig.sha1.js
98 ms
2536007149-postmessagerelay.js
80 ms
jot
98 ms
index.php
603 ms
index.php
1517 ms
index.php
626 ms
bootstrap.css
149 ms
icons.css
151 ms
realtimemap-loading.gif
154 ms
loading-blue.gif
154 ms
world.svg
543 ms
300lo.json
42 ms
getpr.php
705 ms
sh.7c7179124ea24ac6ba46caac.html
26 ms
beacon.gif
214 ms
custom-messages.ff94d8c06a032bf68fcb.js
9 ms
layers.3643cb2e25fb91c29386.js
26 ms
jquery.min.js
13 ms
m.otd.to 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
Form elements do not have associated labels
m.otd.to 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
m.otd.to SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 M.otd.to 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 M.otd.to 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.
m.otd.to
Open Graph description is not detected on the main page of M Otd. 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: