13.2 sec in total
172 ms
9.7 sec
3.4 sec
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 172 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
doodly.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value53.4 s
0/100
25%
Value41.1 s
0/100
10%
Value64,890 ms
0/100
30%
Value0.52
15/100
15%
Value87.3 s
0/100
10%
172 ms
299 ms
107 ms
374 ms
370 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 70% of them (111 requests) were addressed to the original Doodly.com, 3% (5 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to App.provely.io. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Doodly.com.
Page size can be reduced by 574.4 kB (9%)
6.3 MB
5.7 MB
In fact, the total size of Doodly.com main page is 6.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. 85% 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 5.9 MB which makes up the majority of the site volume.
Potential reduce by 79.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. This page needs HTML code to be minified as it can gain 17.2 kB, which is 17% 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 79.8 kB or 79% of the original size.
Potential reduce by 457.2 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 36.9 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 36.9 kB or 19% of the original size.
Potential reduce by 545 B
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 46 (34%)
135
89
The browser has sent 135 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 34 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
doodly.com
172 ms
www.doodly.com
299 ms
gtm.js
107 ms
osano.js
374 ms
built-home-ada.min.css
370 ms
font-awesome.min.css
98 ms
header-fixes.css
228 ms
ada-fixes.css
70 ms
embed-build.js
158 ms
email-decode.min.js
20 ms
conversion.js
95 ms
jquery-3.1.0.min.js
25 ms
popper.min.js
86 ms
bootstrap.min.js
283 ms
str-navigation.js
282 ms
jquery.cookie.js
86 ms
owl.carousel.min.js
143 ms
owl.linked.js
143 ms
slick.min.js
281 ms
modernizer.js
281 ms
scripts-home-new.js
555 ms
c2482ef4d4.js
555 ms
analytics.js
351 ms
bat.js
471 ms
js
71 ms
tracking-script.min.js
547 ms
pptm.js
582 ms
fs.js
597 ms
obtp.js
653 ms
logowhite.svg
328 ms
nav-arrow.png
333 ms
header-icon-1.png
332 ms
header-icon-2.png
335 ms
header-icon-3.png
335 ms
header-icon-6.png
336 ms
rainbow-nav-icon.png
368 ms
header-icon-4.png
337 ms
header-icon-5.png
368 ms
hero-home-new.png
574 ms
camera-graph.png
574 ms
below-top-1.jpg
574 ms
below-top-2.jpg
630 ms
below-top-3.jpg
584 ms
drawing-guy-sittin.png
629 ms
feature-1-img.png
683 ms
feature-2-img.png
1113 ms
feature-4-img.png
1113 ms
feature-5-img.png
1119 ms
feature-6-img.png
1148 ms
feature-7-img.jpg
648 ms
feature-8-img.png
1162 ms
feature-9-img-1.png
914 ms
feature-9-img-2.png
1110 ms
feature-10-img-1.png
1119 ms
feature-10-img-2.png
1517 ms
feature-10-img-3.png
1115 ms
drawing-girl.png
1241 ms
feature-10-img-4.png
2511 ms
feature-10-img-5.png
2564 ms
drawing-grandpa.png
3659 ms
feature-10-img-6.png
3579 ms
drawing-guy-2.png
3530 ms
img-1.png
3531 ms
img-2.png
4428 ms
fbevents.js
349 ms
wr-051bb36b7693c10a1a1d5ce2dc1a4f6e.js
405 ms
fontawesome-webfont.woff
281 ms
Poppins-Regular.woff
4286 ms
collect
249 ms
17184135.js
257 ms
Poppins-Medium.woff
4350 ms
Poppins-Light.woff
4348 ms
Poppins-SemiBold.woff
4325 ms
Poppins-Bold.woff
4343 ms
Gotham-Bold.woff
4345 ms
Gotham-Book.woff
4429 ms
430 ms
img-3.png
4491 ms
img-4.png
5021 ms
4709968f-87b4-4835-aabb-a91b2f382a80.js
308 ms
c2482ef4d4.css
163 ms
img-5.png
4455 ms
collect
114 ms
img-6.png
4317 ms
img-7.png
4405 ms
17184135
335 ms
img-8.png
4739 ms
173532534880180
58 ms
img-9.png
4408 ms
img-10.png
4833 ms
ga-audiences
476 ms
img-11.png
5026 ms
font-awesome-css.min.css
155 ms
unifiedPixel
471 ms
cachedClickId
474 ms
widget.js
12 ms
img-12.png
4915 ms
img-13.png
4982 ms
327 ms
img-14.png
4771 ms
clarity.js
201 ms
provely-2.0.js
196 ms
img-15.png
4509 ms
img-16.png
4511 ms
img-17.png
4662 ms
testimonials-all-3r.png
5049 ms
testimonials-all-2r.png
5410 ms
nick.png
4686 ms
jquery.min.js
30 ms
drawing-girl-2.png
4750 ms
t-img-1.png
4758 ms
campaign
163 ms
t-img-2.png
4679 ms
animate.css
5 ms
contacts
232 ms
t-img-3.png
4469 ms
css2
68 ms
font-awesome.min.css
67 ms
6105799b5128815627100fbb0157b377.jpg
94 ms
zYXgKVElMYYaJe8bpLHnCwDKtdY.ttf
34 ms
zYX9KVElMYYaJe8bpLHnCwDKjSL9MIY.ttf
38 ms
zYX9KVElMYYaJe8bpLHnCwDKjXr8MIY.ttf
47 ms
zYX9KVElMYYaJe8bpLHnCwDKjQ76MIY.ttf
48 ms
zYX9KVElMYYaJe8bpLHnCwDKjWr7MIY.ttf
43 ms
fontawesome-webfont.woff
26 ms
t-img-4.png
3559 ms
t-img-5.png
3563 ms
t-img-6.png
2565 ms
t-img-7.png
2580 ms
t-img-8.png
2645 ms
t-img-9.png
2577 ms
t-img-10.png
1776 ms
t-img-11.png
1849 ms
t-img-12.png
1807 ms
t-img-13.png
1744 ms
int-test-c2.png
2010 ms
int-test-c3.png
2028 ms
ecover.png
1794 ms
guarantee-badge.png
1805 ms
pricing-arrow.png
1792 ms
hero-home-img-l.png
1889 ms
hero-home-img-r.png
1713 ms
feature-1-bg.webp
1758 ms
feature-1-bg-l.png
1777 ms
feature-3-bg.webp
2234 ms
feature-3-img.webp
1457 ms
feature-5-bg-3.webp
1326 ms
iconsoverlay.webp
2011 ms
feature-1-bg.png
2952 ms
feature-3-bg.png
2938 ms
feature-3-img.jpg
1316 ms
feature-5-bg-3.jpg
1504 ms
iconsoverlay.png
1307 ms
arrow.svg
1229 ms
ajax-loader.gif
2770 ms
arrow-w.png
2685 ms
collect
48 ms
c.gif
38 ms
doodly.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
doodly.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
doodly.com 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 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 description is not detected on the main page of Doodly. 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: