2.8 sec in total
498 ms
1.9 sec
363 ms
Click here to check amazing Iaf content for Peru. Otherwise, check out these important facts you probably never knew about iaf.gov
Find out about U.S. Government foreign assistance for community development in Latin America and the Caribbean.
Visit iaf.govWe analyzed Iaf.gov page load time and found that the first response time was 498 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
iaf.gov performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value11.6 s
0/100
25%
Value17.5 s
0/100
10%
Value1,850 ms
9/100
30%
Value0.407
24/100
15%
Value13.4 s
11/100
10%
498 ms
191 ms
267 ms
216 ms
539 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 67% of them (45 requests) were addressed to the original Iaf.gov, 6% (4 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (616 ms) belongs to the original domain Iaf.gov.
Page size can be reduced by 676.8 kB (35%)
2.0 MB
1.3 MB
In fact, the total size of Iaf.gov main page is 2.0 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 41.6 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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 41.6 kB or 78% of the original size.
Potential reduce by 25.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. Iaf images are well optimized though.
Potential reduce by 505.6 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 505.6 kB or 66% of the original size.
Potential reduce by 104.0 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. Iaf.gov needs all CSS files to be minified and compressed as it can save up to 104.0 kB or 89% of the original size.
Number of requests can be reduced by 25 (40%)
62
37
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
iaf.gov
498 ms
StyleBundleDesignTheme.cssbnd
191 ms
StyleBundleDesignTheme.cssbnd
267 ms
StyleBundleFrontendExtra.cssbnd
216 ms
ScriptBundleFAllInOne.jsbnd
539 ms
x-small.css
142 ms
angular.min.js
350 ms
StyleBundleMegaMenuDropDown.cssbnd
164 ms
StyleBundleMegaMenuDropDown.cssbnd
212 ms
656.js
203 ms
homelayout_scripts.js
233 ms
mobile_nav_scripts.js
224 ms
ScriptBundleVisionFrontend.jsbnd
350 ms
css
58 ms
css
71 ms
analytics.js
23 ms
messagebox_strip.gif
124 ms
spacer.gif
123 ms
logo.png
196 ms
menu.png
165 ms
search_input.png
165 ms
ShowImage
122 ms
ShowImage
194 ms
ShowImage
194 ms
ShowImage
194 ms
ShowImage
238 ms
ShowImage
559 ms
ShowImage
269 ms
ShowImage
270 ms
ShowImage
270 ms
ShowImage
271 ms
ShowImage
356 ms
ShowImage
408 ms
ShowImage
616 ms
ShowImage
486 ms
collect
10 ms
collect
162 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
85 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
116 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
124 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
125 ms
119790034
164 ms
divider_1.png
338 ms
divider_2.png
340 ms
mixpanel-2-latest.min.js
92 ms
home_button_bg_strip.gif
392 ms
mobile_arrow.png
360 ms
events_bg_strip.gif
408 ms
datebox_bg.gif
463 ms
divider_3.png
463 ms
divider_4.png
469 ms
footer_strip.gif
468 ms
phone_img.png
539 ms
fullsite_bg.gif
518 ms
fullsite_arrow_left.png
505 ms
24 ms
19 ms
17 ms
player.js
98 ms
player.css
73 ms
ga.js
36 ms
vuid.min.js
70 ms
__utm.gif
26 ms
proxy.html
45 ms
507351906.jpg
152 ms
Print.cssbnd
68 ms
Print.cssbnd
72 ms
iaf.gov accessibility score
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
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
iaf.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
iaf.gov 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
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 Iaf.gov 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 Iaf.gov 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.
iaf.gov
Open Graph description is not detected on the main page of Iaf. 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: