2.4 sec in total
444 ms
1.6 sec
317 ms
Welcome to freerice.com homepage info - get ready to check Freerice best content for United States right away, or after learning these important things about freerice.com
For every correct answer you choose, 10 grains of rice are raised to help end world hunger through the World Food Programme.
Visit freerice.comWe analyzed Freerice.com page load time and found that the first response time was 444 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
freerice.com performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value11.1 s
0/100
25%
Value9.6 s
11/100
10%
Value210 ms
88/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
444 ms
401 ms
160 ms
241 ms
241 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 83% of them (38 requests) were addressed to the original Freerice.com, 11% (5 requests) were made to Google-analytics.com and 2% (1 request) were made to Cdn.uservoice.com. The less responsive or slowest element that took the longest time to load (444 ms) belongs to the original domain Freerice.com.
Page size can be reduced by 309.1 kB (51%)
608.4 kB
299.3 kB
In fact, the total size of Freerice.com main page is 608.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 244.4 kB which makes up the majority of the site volume.
Potential reduce by 20.9 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 20.9 kB or 75% of the original size.
Potential reduce by 41.6 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, Freerice needs image optimization as it can save up to 41.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 142.4 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 142.4 kB or 68% of the original size.
Potential reduce by 104.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. Freerice.com needs all CSS files to be minified and compressed as it can save up to 104.2 kB or 82% of the original size.
Number of requests can be reduced by 18 (40%)
45
27
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freerice. 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.
freerice.com
444 ms
css_27fe70e699e1e7002f2af6e105167569.css
401 ms
logo.gif
160 ms
pic_givemorerice.gif
241 ms
pic_watchfreerice.gif
241 ms
emerg_EBOLA_549x90.jpg
321 ms
fr-twitter.jpg
163 ms
js_9542f9cf45b50c5e4a47537bf76e21c2.js
320 ms
qtools_ahah.js
241 ms
js_aaf064972372b393981c4c2b742447f6.js
242 ms
bg_body.jpg
407 ms
bg_ui_ul_ul.png
82 ms
bg_ui_ul_li.gif
82 ms
arrow-down.png
83 ms
bg_body_foot.png
82 ms
bg_header.gif
137 ms
slogan.gif
163 ms
bg_home_content.gif
164 ms
bg_frblog_ui.gif
166 ms
bg-fshare.png
91 ms
bg-tweet.png
143 ms
ga.js
6 ms
qtools_ajax.index.php
281 ms
game.php
436 ms
tab.js
10 ms
__utm.gif
11 ms
__utm.gif
3 ms
loader.gif
133 ms
__utm.gif
2 ms
table-ico_2.gif
83 ms
MFRT0846.JPG
85 ms
hunger-in-numbers.jpg
87 ms
infographic4.jpg
85 ms
ico_user_login.gif
84 ms
css_f4f156d46c3477126dbab05ffffb4cf8.css
83 ms
widgets.js
83 ms
pic_rice_1.gif
102 ms
pic_rice_2.gif
102 ms
pic_rice_3.gif
102 ms
title_how_to_play_en-US.gif
103 ms
sprite.gif
164 ms
ico_voice.gif
139 ms
loader-question.gif
163 ms
bg_see_the_totals.jpg
321 ms
__utm.gif
3 ms
jot
107 ms
freerice.com accessibility score
freerice.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
Page has valid source maps
freerice.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Freerice.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 Freerice.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.
freerice.com
Open Graph data is detected on the main page of Freerice. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: