3.2 sec in total
619 ms
2.4 sec
209 ms
Click here to check amazing Kids For Tomorrow content. Otherwise, check out these important facts you probably never knew about kidsfortomorrow.org
Our mission is to empower students and communities through education, equipping them to think globally and act locally.
Visit kidsfortomorrow.orgWe analyzed Kidsfortomorrow.org page load time and found that the first response time was 619 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
kidsfortomorrow.org performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value13.1 s
0/100
25%
Value8.3 s
19/100
10%
Value1,090 ms
24/100
30%
Value0.086
93/100
15%
Value11.6 s
18/100
10%
619 ms
88 ms
90 ms
90 ms
95 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Kidsfortomorrow.org, 3% (2 requests) were made to Staticxx.facebook.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kidsfortomorrow.org.
Page size can be reduced by 243.5 kB (17%)
1.4 MB
1.2 MB
In fact, the total size of Kidsfortomorrow.org main page is 1.4 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 28.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 28.8 kB or 79% of the original size.
Potential reduce by 57.0 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. Kids For Tomorrow images are well optimized though.
Potential reduce by 123.1 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 123.1 kB or 71% of the original size.
Potential reduce by 34.6 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. Kidsfortomorrow.org needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 79% of the original size.
Number of requests can be reduced by 21 (36%)
59
38
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kids For Tomorrow. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
kidsfortomorrow.org
619 ms
nivo-slider.css
88 ms
style.css
90 ms
shadowbox.css
90 ms
template.css.php
95 ms
btcontentslider.css
95 ms
style.css
97 ms
mootools-core.js
223 ms
core.js
133 ms
caption.js
137 ms
jquery.min.js
12 ms
jquery.noconflict.js
138 ms
jquery.nivo.slider.js
135 ms
all.js
7 ms
index.php
558 ms
modernizr.js
174 ms
slides.js
300 ms
default.js
178 ms
jquery.easing.1.3.js
181 ms
transmenu_Packed.js
301 ms
kids4tom.css
299 ms
system.css
299 ms
typography.php
1332 ms
34 ms
system.css
46 ms
facebook.png
46 ms
twitter.png
48 ms
google.png
48 ms
linkedin.png
46 ms
KFT_logo.gif
131 ms
menu_aboutus.png
91 ms
menu_over_aboutus.png
89 ms
menu_projects.png
95 ms
menu_over_projects.png
94 ms
menu_media.png
133 ms
menu_over_media.png
138 ms
menu_store.png
138 ms
menu_over_store.png
139 ms
menu_involved.png
173 ms
menu_over_involved.png
178 ms
menu_donate.png
180 ms
menu_over_donate.png
185 ms
KFT_backgrnd.gif
469 ms
loading.gif
62 ms
slide1.png
223 ms
slide2.png
241 ms
slide3.png
242 ms
KFT_homeR.png
317 ms
education_power.png
179 ms
9ad07a92f4663226e22e52a0013be512-1.jpg
272 ms
948ab40a88327b61662b245921eb73f7-image_0.jpg
269 ms
7bc302dd77e02595240040af8a72865f-247768_537559719591600_1468158244_n.jpg
288 ms
b042b3a418617b1525cc78bb17bed390-a-kenya_850.jpg
293 ms
5eaca6848e50096203b25d478db0c1c7-520bbeb98f0dd.jpg
321 ms
xd_arbiter.php
33 ms
xd_arbiter.php
37 ms
re-left.png
262 ms
re-right.png
276 ms
pagination.png
281 ms
loading.gif
300 ms
kidsfortomorrow.org 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.
kidsfortomorrow.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
kidsfortomorrow.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
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 Kidsfortomorrow.org 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 Kidsfortomorrow.org 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.
kidsfortomorrow.org
Open Graph description is not detected on the main page of Kids For Tomorrow. 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: