4.2 sec in total
380 ms
3.3 sec
522 ms
Welcome to what2do.com homepage info - get ready to check What 2 Do best content right away, or after learning these important things about what2do.com
NO Description
Visit what2do.comWe analyzed What2do.com page load time and found that the first response time was 380 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
what2do.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value5.2 s
24/100
25%
Value4.7 s
68/100
10%
Value490 ms
59/100
30%
Value0.095
91/100
15%
Value7.2 s
51/100
10%
380 ms
190 ms
97 ms
250 ms
183 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original What2do.com, 19% (21 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (857 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 713.7 kB (64%)
1.1 MB
403.0 kB
In fact, the total size of What2do.com 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. Javascripts take 641.7 kB which makes up the majority of the site volume.
Potential reduce by 109.6 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 109.6 kB or 80% of the original size.
Potential reduce by 25.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, What 2 Do needs image optimization as it can save up to 25.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 455.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 455.7 kB or 71% of the original size.
Potential reduce by 122.7 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. What2do.com needs all CSS files to be minified and compressed as it can save up to 122.7 kB or 83% of the original size.
Number of requests can be reduced by 59 (55%)
108
49
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What 2 Do. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.thekidscoop.com
380 ms
styles_prod.css.php
190 ms
new_blog.css
97 ms
js_prod_2.js.php
250 ms
fullcalendar.js
183 ms
jquery.tablesorter.min.js
114 ms
jquery.tinyscrollbar.min.js
94 ms
scroll.js
122 ms
bjqs-1.3.js
121 ms
jquery.eventCalendar.js
143 ms
pinit.js
51 ms
plusone.js
69 ms
conversion.js
20 ms
jquery.min.js
16 ms
bpopup.js
29 ms
cb=gapi.loaded_0
57 ms
ga.js
57 ms
PinExt.png
56 ms
logo_en.png
223 ms
feedback.jpg
56 ms
gmail.jpg
54 ms
facebook1.jpg
57 ms
twitter1.jpg
53 ms
pin.jpg
56 ms
contest.jpg
54 ms
logo_en.png
160 ms
login_with_fb.jpg
159 ms
search_arrow.jpg
157 ms
brithday_img.jpg
165 ms
anytime_activities.jpg
159 ms
right.png
159 ms
bullet.jpg
160 ms
watch_our_video_img.jpg
161 ms
share_footer.jpg
161 ms
blank.gif
160 ms
montreal_2.png
162 ms
toronto_2.png
164 ms
calgary_2.png
165 ms
edmonton_2.png
164 ms
vancouver_2.png
164 ms
pinit_main.js
155 ms
all.js
379 ms
widgets.js
157 ms
woopra.js
151 ms
great_bg.jpg
458 ms
getCategoriesAndSubCategories_TOOL.php
81 ms
getLocationsAll_TOOL.php
116 ms
__utm.gif
58 ms
loading-small.gif
59 ms
helveticaregular.woff
46 ms
208 ms
bg-scrollbar-track-y.png
33 ms
bg-scrollbar-trackend-y.png
30 ms
bg-scrollbar-thumb-y.png
31 ms
free_jon.jpg
38 ms
footer_bg.jpg
543 ms
count.js
111 ms
100 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
217 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
254 ms
cb=gapi.loaded_1
33 ms
fastbutton
116 ms
154 ms
likebox.php
308 ms
postmessageRelay
94 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
26 ms
155 ms
xd_arbiter.php
220 ms
xd_arbiter.php
435 ms
cb=gapi.loaded_0
50 ms
cb=gapi.loaded_1
50 ms
grlryt2bdKIyfMSOhzd1eA.woff
73 ms
3193398744-postmessagerelay.js
44 ms
rpc:shindig_random.js
42 ms
syndication
139 ms
273535651620732930
249 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
58 ms
cb=gapi.loaded_0
15 ms
ebiMDO3r-8l.css
322 ms
jGc-59L_9lo.css
390 ms
6qHpHChjY_J.css
459 ms
ztINr5qMqM_.css
591 ms
uVjHKJ0glvg.css
599 ms
q68gy-v_YMF.js
658 ms
FJmpeSpHpjS.js
685 ms
0wM5s1Khldu.js
526 ms
1bNoFZUdlYZ.js
529 ms
njO1TPvGzoR.js
614 ms
1QuX41zDRrx.js
614 ms
Oagsvfb4VWi.js
722 ms
LTv6ZK-5zxz.js
857 ms
1FCa-btixu2.js
729 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
84 ms
tw_no_city_normal.jpg
55 ms
jot.html
50 ms
11831812_10153483905319383_1371730325346057810_n.jpg
308 ms
safe_image.php
341 ms
11226916_10153483905739383_5547687414391783156_n.jpg
402 ms
11831812_10153483905319383_1371730325346057810_n.jpg
510 ms
11226916_10153483905739383_5547687414391783156_n.jpg
611 ms
11855734_10153483905049383_1496645918528341708_n.jpg
528 ms
11742822_10153444396604383_6176192364596010338_n.jpg
612 ms
wL6VQj7Ab77.png
115 ms
s7jcwEQH7Sx.png
116 ms
QDwYpIaRyfG.png
117 ms
K00K-UgnsKu.png
115 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
138 ms
xd_arbiter.php
158 ms
like.php
88 ms
LVx-xkvaJ0b.png
71 ms
what2do.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
what2do.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
Browser errors were logged to the console
what2do.com SEO score
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 What2do.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 What2do.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.
what2do.com
Open Graph description is not detected on the main page of What 2 Do. 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: