7.4 sec in total
332 ms
6.8 sec
281 ms
Click here to check amazing Fao content for India. Otherwise, check out these important facts you probably never knew about fao.org
FAO Home page
Visit fao.orgWe analyzed Fao.org page load time and found that the first response time was 332 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fao.org performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value12.2 s
0/100
25%
Value9.3 s
13/100
10%
Value8,420 ms
0/100
30%
Value0.001
100/100
15%
Value29.1 s
0/100
10%
332 ms
223 ms
4624 ms
222 ms
221 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 61% of them (61 requests) were addressed to the original Fao.org, 23% (23 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Fao.org.
Page size can be reduced by 1.6 MB (36%)
4.4 MB
2.8 MB
In fact, the total size of Fao.org main page is 4.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. 50% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 40.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 40.5 kB or 79% of the original size.
Potential reduce by 151.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. Fao images are well optimized though.
Potential reduce by 697.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 697.9 kB or 70% of the original size.
Potential reduce by 664.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. Fao.org needs all CSS files to be minified and compressed as it can save up to 664.2 kB or 69% of the original size.
Number of requests can be reduced by 30 (32%)
95
65
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fao. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fao.org
332 ms
www.fao.org
223 ms
4624 ms
tx_jfmulticontent_pi1.css
222 ms
stylesheet_5d370599a3.css
221 ms
0ad75cee-12a6-49a0-a922-c4ecad41ec44.css
70 ms
fao_style.css
332 ms
main.css
222 ms
normalize.css
221 ms
header_menu_style.css
256 ms
font-awesome.css
437 ms
idangerous.swiper.css
329 ms
main.js
335 ms
plugins.js
334 ms
jquery-1.8.3.min.js
484 ms
modernizr-2.6.2.min.js
548 ms
rgaccordion_jquery.js
441 ms
jquery.selectbox-0.2.min.js
442 ms
comm_func.js
442 ms
jquery.iosslider.min.js
565 ms
jquery.cycle.all.min.js
567 ms
idangerous.swiper.js
662 ms
brand
14 ms
brand
35 ms
FAO-logo.png
130 ms
search_icon.png
130 ms
LARC34_En.jpg
336 ms
df40d6c912.jpg
328 ms
17254316191_fa494bf258_b.jpg
661 ms
c512b8e0d2.jpg
551 ms
1124fc583e.jpg
456 ms
35a49e179f.jpg
556 ms
storm-ocean.png
455 ms
sowa.JPG
455 ms
Emblem_125x90.jpg
556 ms
IYP-Pulses-Facts-infographic.png
560 ms
ZIKA.png
561 ms
more.png
663 ms
7e209f61b8.png
667 ms
83abb9985b.png
668 ms
more-full.png
672 ms
small_1_fei%20banana.jpg
673 ms
small_ecosystems%20main%20pic.jpg
769 ms
small_Google4.jpg
771 ms
small_3_medium_banner_iyp.jpg
776 ms
small_Popova.jpg
778 ms
flags.jpg
780 ms
d287cb8437.png
782 ms
hand-shake.jpg
879 ms
CSF-Banner-210-EN_01.png
882 ms
RTEmagicC_facebook_26.png.png
884 ms
RTEmagicC_flickr_23.png.png
886 ms
RTEmagicC_c6270bed47.png.png
891 ms
RTEmagicC_456950478f.png.png
892 ms
RTEmagicC_linkedin_07.png.png
989 ms
RTEmagicC_rss_19.png.png
991 ms
RTEmagicC_433b8859a8.png.png
994 ms
RTEmagicC_2e22811972.png.png
998 ms
RTEmagicC_twitter_01.png.png
1002 ms
RTEmagicC_youtube_40.png.png
993 ms
59d9a83f-4045-4d43-af46-655f845461ee.woff
94 ms
google_custom_search_watermark.gif
32 ms
widgets.js
31 ms
analytics.js
23 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
34 ms
collect
21 ms
collect
19 ms
collect
18 ms
download-app-icon-55x81px.png
978 ms
applestore-icon-127x38px.png
980 ms
syndication
88 ms
345123828525047808
220 ms
googleplay-icon-127x38px.png
784 ms
HP-Infographic-milk-en.jpg
783 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
NshDcm07_normal.png
137 ms
c23f22e168e328b64fecef4a48bbe625_normal.png
165 ms
06b2e4f112bace5fd5bf03dd5e165101_normal.png
196 ms
UEoCaMHw_normal.jpg
226 ms
n_jhaeB-_normal.png
241 ms
d5affe4d7038fe5c6ff9e5412d76cda7_normal.png
244 ms
2795f2309567aa7bde4f1686fed8997c_normal.jpeg
258 ms
g1ts6xYc_normal.jpg
254 ms
a6fWkaSB_normal.jpeg
253 ms
44f6b111c76dd1b008723d2dc1851bcb_normal.jpeg
257 ms
CcIe9CBUYAIOC1T.jpg:small
315 ms
CcYQ2bUWIAExj2Q.jpg:small
271 ms
CcYLAtDXIAApL76.jpg:small
281 ms
CcYKeTCWwAExmXE.jpg:small
281 ms
CcXCQp6WwAA-rdr.jpg:small
313 ms
CcYDpM8VIAAQR1D.jpg:small
310 ms
CcYAl8jXIAE1FH8.jpg:small
318 ms
CcU92p7XEAEen58.jpg:small
309 ms
CcXwJTQWIAA7PvY.jpg:small
307 ms
CcX26GJWIAAiSF2.jpg:small
336 ms
CcX1LVlW4AA_6Ih.jpg:small
334 ms
CcXxvetWEAAOq56.jpg:small
337 ms
CcXpMLZXIAAh9a8.jpg:small
340 ms
jot
28 ms
fao.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
fao.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
Browser errors were logged to the console
Page has valid source maps
fao.org 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
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 Fao.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 Fao.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.
fao.org
Open Graph description is not detected on the main page of Fao. 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: