Tools & Wizards About Us
freerice.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

freerice.org

Play online, learn online and feed the hungry | Freerice.com

Page Load Speed

2.8 sec in total

First Response

426 ms

Resources Loaded

1.9 sec

Page Rendered

433 ms

freerice.org screenshot

About Website

Click here to check amazing Freerice content. Otherwise, check out these important facts you probably never knew about freerice.org

For every correct answer you choose, 10 grains of rice are raised to help end world hunger through the World Food Programme.

Visit freerice.org

Key Findings

We analyzed Freerice.org page load time and found that the first response time was 426 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

freerice.org performance score

0

Network Requests Diagram

freerice.com

426 ms

css_27fe70e699e1e7002f2af6e105167569.css

408 ms

ew-en.js

6 ms

logo.gif

162 ms

pic_givemorerice.gif

245 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Freerice.org, 10% (5 requests) were made to Google-analytics.com and 8% (4 requests) were made to Cdn.wfp.org. The less responsive or slowest element that took the longest time to load (426 ms) relates to the external source Freerice.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 274.8 kB (46%)

Content Size

599.0 kB

After Optimization

324.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freerice.org main page is 599.0 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 243.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.0 kB

  • Original 29.6 kB
  • After minification 26.7 kB
  • After compression 7.5 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 22.0 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 14.2 kB

  • Original 243.2 kB
  • After minification 229.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. Freerice images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 143.8 kB

  • Original 211.2 kB
  • After minification 174.3 kB
  • After compression 67.5 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 143.8 kB or 68% of the original size.

CSS Optimization

-82%

Potential reduce by 94.8 kB

  • Original 114.9 kB
  • After minification 110.8 kB
  • After compression 20.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.org needs all CSS files to be minified and compressed as it can save up to 94.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (38%)

Requests Now

48

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

freerice.com

freerice.com

426 ms

css_27fe70e699e1e7002f2af6e105167569.css

css_27fe70e699e1e7002f2af6e105167569.css

408 ms

ew-en.js

ew-en.js

6 ms

logo.gif

logo.gif

162 ms

pic_givemorerice.gif

pic_givemorerice.gif

245 ms

pic_watchfreerice.gif

pic_watchfreerice.gif

244 ms

emerg_EBOLA_549x90.jpg

emerg_EBOLA_549x90.jpg

326 ms

js_9542f9cf45b50c5e4a47537bf76e21c2.js

js_9542f9cf45b50c5e4a47537bf76e21c2.js

411 ms

qtools_ahah.js

qtools_ahah.js

162 ms

js_aaf064972372b393981c4c2b742447f6.js

js_aaf064972372b393981c4c2b742447f6.js

243 ms

fr-twitter.jpg

fr-twitter.jpg

245 ms

bg_body.jpg

bg_body.jpg

324 ms

bg_ui_ul_ul.png

bg_ui_ul_ul.png

89 ms

bg_ui_ul_li.gif

bg_ui_ul_li.gif

89 ms

arrow-down.png

arrow-down.png

88 ms

bg_body_foot.png

bg_body_foot.png

88 ms

bg_header.gif

bg_header.gif

172 ms

slogan.gif

slogan.gif

172 ms

bg_home_content.gif

bg_home_content.gif

172 ms

bg_frblog_ui.gif

bg_frblog_ui.gif

171 ms

bg-fshare.png

bg-fshare.png

86 ms

bg-tweet.png

bg-tweet.png

84 ms

ga.js

ga.js

8 ms

wfp-ew.css

wfp-ew.css

14 ms

qtools_ajax.index.php

qtools_ajax.index.php

236 ms

game.php

game.php

360 ms

tab.js

tab.js

11 ms

__utm.gif

__utm.gif

14 ms

__utm.gif

__utm.gif

5 ms

loader.gif

loader.gif

163 ms

__utm.gif

__utm.gif

4 ms

en.jpg

en.jpg

8 ms

close.png

close.png

5 ms

table-ico_2.gif

table-ico_2.gif

84 ms

MFRT0846.JPG

MFRT0846.JPG

245 ms

hunger-in-numbers.jpg

hunger-in-numbers.jpg

87 ms

infographic4.jpg

infographic4.jpg

89 ms

ico_user_login.gif

ico_user_login.gif

84 ms

widgets.js

widgets.js

136 ms

pic_rice_1.gif

pic_rice_1.gif

85 ms

pic_rice_2.gif

pic_rice_2.gif

87 ms

pic_rice_3.gif

pic_rice_3.gif

88 ms

title_how_to_play_en-US.gif

title_how_to_play_en-US.gif

88 ms

sprite.gif

sprite.gif

89 ms

ico_voice.gif

ico_voice.gif

164 ms

loader-question.gif

loader-question.gif

164 ms

bg_see_the_totals.jpg

bg_see_the_totals.jpg

325 ms

__utm.gif

__utm.gif

4 ms

css_f4f156d46c3477126dbab05ffffb4cf8.css

css_f4f156d46c3477126dbab05ffffb4cf8.css

84 ms

SEO Factors

freerice.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freerice.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 Freerice.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.

Social Sharing Optimization

freerice.org

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: