5.2 sec in total
1.7 sec
3.1 sec
531 ms
Welcome to whocares.me homepage info - get ready to check Whocares best content for Netherlands right away, or after learning these important things about whocares.me
Whocares verzamelt wereldwijd de meest inspirerende initiatieven en projecten gericht op het helpen van mensen in moeilijke omstandigheden.
Visit whocares.meWe analyzed Whocares.me page load time and found that the first response time was 1.7 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
whocares.me performance score
1654 ms
269 ms
354 ms
9 ms
26 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 79% of them (46 requests) were addressed to the original Whocares.me, 5% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Whocares.me.
Page size can be reduced by 676.4 kB (37%)
1.8 MB
1.2 MB
In fact, the total size of Whocares.me main page is 1.8 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. 55% of websites need less resources to load. Images take 857.2 kB which makes up the majority of the site volume.
Potential reduce by 65.7 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 65.7 kB or 74% of the original size.
Potential reduce by 3.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. Whocares images are well optimized though.
Potential reduce by 467.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 467.9 kB or 65% of the original size.
Potential reduce by 139.2 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. Whocares.me needs all CSS files to be minified and compressed as it can save up to 139.2 kB or 86% of the original size.
Number of requests can be reduced by 5 (10%)
51
46
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whocares. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
whocares.me
1654 ms
styles.css
269 ms
footer.min.js
354 ms
addthis_widget.js
9 ms
ga.js
26 ms
empty.gif
99 ms
whocares_homepage_headliner.jpg
737 ms
marianne_88_88_int_s_c1_c_c.jpg
308 ms
marianne_478_235_int_s_c1_c_c.jpg
387 ms
1450110_704171409594359_199582465_n_88_88_int_s_c1_c_c.jpg
308 ms
1450110_704171409594359_199582465_n_478_235_int_s_c1_c_c.jpg
403 ms
141034819052744200_resized_88_88_int_s_c1_c_c.jpg
306 ms
141034819052744200_resized_478_235_int_s_c1_c_c.jpg
486 ms
img_0009_2_88_88_int_s_c1_c_c.jpg
401 ms
img_0009_2_478_235_int_s_c1_c_c.jpg
646 ms
wzhjustice2-1_88_88_int_s_c1_c_c.jpg
473 ms
wzhjustice2-1_478_235_int_s_c1_c_c.jpg
565 ms
Bananas_88_88_int_s_c1_c_c.jpg
490 ms
Bananas_478_235_int_s_c1_c_c.jpg
730 ms
Lieve_Joep_88_88_int_s_c1_c_c.jpg
575 ms
Lieve_Joep_478_235_int_s_c1_c_c.jpg
760 ms
blog-tanja-klein_copy_130_130_int_c1_c_c.jpg
646 ms
aranka_130_130_int_c1_c_c.jpg
664 ms
carolien_130_130_int_c1_c_c.jpg
730 ms
vera_130_130_int_c1_c_c.jpg
733 ms
karlien_2_130_130_int_c1_c_c.jpg
754 ms
blog-matthijs-klein_copy_130_130_int_c1_c_c.jpg
814 ms
jessica_130_130_int_c1_c_c.jpg
816 ms
index_102_101_int.jpg
817 ms
logo_bright_135_30_int.jpg
819 ms
nudge_logo_135_50_int.jpg
844 ms
nieuw_logo_nobla_120_101_int.jpg
847 ms
par-ff_101_101_int.jpg
900 ms
par-des_101_101_int.jpg
901 ms
par-hi5_101_101_int.jpg
903 ms
par-360_101_101_int.jpg
903 ms
par-uc_101_101_int.jpg
933 ms
de_beste_social_media_101_101_int.jpg
937 ms
gezondnu_100_100_int.jpg
984 ms
all.js
308 ms
nav_home_icon.jpg
974 ms
__utm.gif
20 ms
collect
215 ms
ubuntumono-bold-webfont.woff
901 ms
pt_sans-web-regular-webfont.woff
700 ms
kelson_sans_regular-webfont.woff
725 ms
ubuntumono-regular-webfont.woff
729 ms
lekton-bold-webfont.woff
773 ms
134 ms
xd_arbiter.php
213 ms
xd_arbiter.php
418 ms
sprite.png
686 ms
logo-high.png
682 ms
logo-care.png
689 ms
300lo.json
29 ms
nl.js
25 ms
ping
58 ms
sh.953eb77977227bfd253ee158.html
30 ms
whocares.me SEO score
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whocares.me can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Whocares.me 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.
whocares.me
Open Graph data is detected on the main page of Whocares. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: