2.4 sec in total
56 ms
2.2 sec
120 ms
Visit doodly.com now to see the best up-to-date Doodly content for India and also check out these interesting facts you probably never knew about doodly.com
The Simplest Whiteboard Animation Software
Visit doodly.comWe analyzed Doodly.com page load time and found that the first response time was 56 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
doodly.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value7.3 s
5/100
25%
Value15.2 s
1/100
10%
Value10,690 ms
0/100
30%
Value2.01
0/100
15%
Value28.8 s
0/100
10%
56 ms
287 ms
99 ms
90 ms
113 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 7% of them (8 requests) were addressed to the original Doodly.com, 55% (65 requests) were made to Images.clickfunnels.com and 15% (18 requests) were made to Statics.myclickfunnels.com. The less responsive or slowest element that took the longest time to load (900 ms) relates to the external source Images.clickfunnels.com.
Page size can be reduced by 431.5 kB (17%)
2.5 MB
2.1 MB
In fact, the total size of Doodly.com main page is 2.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. 75% 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 422.0 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 422.0 kB or 86% of the original size.
Potential reduce by 7.9 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. Doodly images are well optimized though.
Potential reduce by 113 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.4 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. Doodly.com has all CSS files already compressed.
Number of requests can be reduced by 24 (21%)
112
88
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doodly. 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 9 to 1 for CSS and as a result speed up the page load time.
doodly.com
56 ms
www.doodly.com
287 ms
loading-attribute-polyfill.min.js
99 ms
container-query-polyfill.modern.js
90 ms
jquery.min.js
113 ms
jquery.cookie.min.js
126 ms
lazysizes.min.js
109 ms
jquery.fitvids.min.js
105 ms
video.min.js
133 ms
video-js.min.css
109 ms
all.css
111 ms
v4-shims.css
164 ms
css
105 ms
user_pages-M2AWEVSP.css
107 ms
navigation-v1-Q2ASDVF2.css
166 ms
video-K4KL7M5Q.css
162 ms
owl.carousel.min.css
115 ms
owl.theme.default.min.css
148 ms
js
115 ms
embed-build.js
87 ms
owl.carousel.min.js
104 ms
user_pages-UEHJI6JO.js
509 ms
navigation-v1-KZVMKXN6.js
509 ms
video-ZAXPZ32P.js
484 ms
vcd15cbe7772f49c399c6a5babf22c1241717689176015
484 ms
gtm.js
370 ms
fbevents.js
398 ms
dfd9bc60e95ae08fbc8a58b99aec9c0e.png
576 ms
c1d7918e3f90f4c7eef38098bdd86bb3.png
574 ms
cac7765271fcefa2624e28b1db1f27e8.png
369 ms
b7be93934e7577c866577ed84655cb56.jpg
429 ms
ce3e28413ca64b8f3d5c83380c3ef66d.jpg
423 ms
69eeef7ec688662df21d6b2bb5034e70.jpg
889 ms
216948a3f1886bb935466e3e80c7e88c.png
427 ms
1ae77d8339ba532554814c679af60707.png
443 ms
56b9124f6f927eaae3c35016d7e0d328.png
419 ms
30601e11d4bd919fcd15a977e30545e0.png
484 ms
25e8c96a7b865ee6d670f423fa935d6e.png
482 ms
43eead15267b4624382ab6f1d2af8962.png
456 ms
3a7a051b5e6b10e41d1fc5899dd8f765.png
518 ms
dca5b4708f7e4b6428a4872ebcf59cf1.png
504 ms
294a590ae171bd66bd024341e321f817.png
531 ms
bc24b754995435ec4251ff2bcb3d3a6d.png
570 ms
51a88801fda522a789014f77430b7fe0.png
535 ms
70cc47da2bd7b28251293160a92fa163.png
588 ms
a9745b74c19a6bca201a2756e381e873.png
635 ms
0ba2258b761f426b8d33bf7a7c98a41f.jpg
593 ms
6643944d27e93ebc8334c5674b73db27.png
594 ms
5deae973de77717c8d03e4a3366f315c.png
650 ms
47f601c5660055a425f79f071483eb2b.png
678 ms
4190de49c7a985aeaee1ba16e26f1cf7.png
682 ms
3d2ca6c43f12a2da84bff2ea891395af.png
637 ms
9d55622054543e81fa486b731eb9e680.png
768 ms
2e10ae868c202bc8883eaf8ddc10d878.png
761 ms
30a835fca976c79437d68b61c13fe000.png
731 ms
be5e3d306d11e226f07be22236c638be.png
751 ms
2a89f22afa400c29e20ac96983510262.png
778 ms
ae9118e174507c6dd9804da0d67f6920.png
817 ms
4e65e60b71f27cd1cc57ce3db971e568.png
850 ms
047759c15c616b94764b34347b7d62a9.png
793 ms
d045b08a51a67adc85185da79cb2610c.png
848 ms
44016eb7108a3a3b588a9e0f24cfb3bd.png
844 ms
384f1df74c35d6a8faabcee604993b7a.png
840 ms
6c00d6b3252872b1901f3d25c97f28c8.png
900 ms
d1a5a05ec0950c72d3c1b1e943188093.png
328 ms
0baf5a6e7315a88e5ecc5bd73deed476.png
366 ms
06d325828b8fa8b39803799010abd9ae.png
369 ms
2c89517378fa8cc3ef054b3236333004.png
367 ms
0fd8835bbef8d6e2e200babdd881c0e5.png
369 ms
cadb176afbaaefab9a380eebee0e0394.png
369 ms
3d0c364ce1ac4f08650b21273d5da01f.png
367 ms
e093dc6bd61100b4a36c93cbe055faa4.png
416 ms
9e1eadec922f00295582f34da691c491.png
417 ms
419ed33cb1d1781762735493d7e92906.png
417 ms
6147ef42699117e4547cdd52371a2274.png
420 ms
09d932e50bf2a5347b1d73b9ed255314.jpg
419 ms
d1b821f20d823f522083681b2dd987db.jpg
419 ms
197c74f06f82484e882dfc7de444b8f6.png
419 ms
1296114edab1d6e8cd5bea97c0e925d0.png
420 ms
f2f38db67f05230ba0b764d82e493cdd.png
423 ms
4003b66ba71d6a5854b68876b42fd04d.png
418 ms
font
232 ms
original-7d6415f25978370e3b59aef41dcd2831.ttf
349 ms
font
311 ms
fa-brands-400.woff
100 ms
fa-solid-900.woff
229 ms
fa-regular-400.woff
174 ms
font
350 ms
1add62b9ff4ec1288a9d713ff3ed8770.png
629 ms
e38399e8ada943b7c992d2aa3665070d.png
541 ms
51c7a437260d4a576e69182e31cc6b36.png
486 ms
34881174d606656612b188b5e9d33a8b.png
532 ms
52c0b46473c94fd9307b92ea071baae5.png
491 ms
d7112194756514ef67a0366a48e0effe.png
582 ms
5d3588badecc25657e97ec43a796eaee.png
564 ms
edb80095c017be4e7da47deec6540f1d.png
496 ms
a40503d153bb4dcb079794c025ec1d08.png
504 ms
5ee83801e3fd31b7b812159f2bd6cc2a.png
469 ms
6ac2ee03996bf7233ac83ccc0a3259f0.png
548 ms
03505a8e09486b211ed24e93101c4c81.png
565 ms
eaaaa6401493480eda78829291842c5d.png
569 ms
13bcbcd69c0f981a5c1ad32346ed6e45.png
525 ms
47623ee657554587b5b71f8907db6f23.png
477 ms
557f4702d840a410de2617954a91b8cb.png
481 ms
d1f834cb54fe7d36fb6264f7fbdc0707.png
513 ms
c70856aca1446b5c48f75866ead6b221.png
532 ms
a4a4744cee228bc17e5a3050bd565433.png
493 ms
2236125e3ac4a0c297c4c961991ebcc7.png
552 ms
b5729e3a5098a2137a29fa2b37989a11.png
478 ms
2598913fe84553b830ff7a22ff7aa1b4.png
497 ms
6cab9886175b4870cea3d64f5aec780b.png
645 ms
3a7451bb96fa8ab2fd8e90e75beba2e7.png
482 ms
4a1f5cc63909e4b23b9ef401af18c74e.png
433 ms
d949f4deaee89858a307dfc62038c01d.png
487 ms
86976fdda5b8d7a05c4c914b5729f02c.png
477 ms
9512b8ffa40362cc6ace2ed409f8394f.png
457 ms
cac7765271fcefa2624e28b1db1f27e8.png
448 ms
aem.js
34 ms
doodly.com 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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
doodly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
doodly.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Doodly.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 Doodly.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.
doodly.com
Open Graph data is detected on the main page of Doodly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: