1 sec in total
47 ms
668 ms
314 ms
Visit pepfar.gov now to see the best up-to-date Pepfar content for United States and also check out these interesting facts you probably never knew about pepfar.gov
Visit pepfar.govWe analyzed Pepfar.gov page load time and found that the first response time was 47 ms and then it took 982 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
pepfar.gov performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value5.3 s
21/100
25%
Value7.3 s
29/100
10%
Value5,150 ms
0/100
30%
Value0
100/100
15%
Value22.8 s
1/100
10%
47 ms
88 ms
36 ms
12 ms
8 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 83% of them (57 requests) were addressed to the original Pepfar.gov, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (196 ms) belongs to the original domain Pepfar.gov.
Page size can be reduced by 636.1 kB (51%)
1.2 MB
608.7 kB
In fact, the total size of Pepfar.gov main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 572.3 kB which makes up the majority of the site volume.
Potential reduce by 36.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 16.1 kB, which is 36% 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 36.6 kB or 82% of the original size.
Potential reduce by 41.5 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. Pepfar images are well optimized though.
Potential reduce by 406.0 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 406.0 kB or 71% of the original size.
Potential reduce by 152.1 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. Pepfar.gov needs all CSS files to be minified and compressed as it can save up to 152.1 kB or 74% of the original size.
Number of requests can be reduced by 36 (57%)
63
27
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pepfar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
pepfar.gov
47 ms
index.htm
88 ms
jquery-1.5.2.min.js
36 ms
custom-form-elements.js
12 ms
jquery.dropdownPlain.js
8 ms
functions2.js
12 ms
jquery-select-overlap.js
10 ms
browseby.js
8 ms
foresee-trigger.js
78 ms
highlights.js
11 ms
newstyle.css
13 ms
tier3-pepfar.css
12 ms
oldtier3.css
28 ms
newmenu.css
31 ms
noprint.css
16 ms
Universal-Federated-Analytics.1.0.js
46 ms
widget.php
53 ms
APIModules_all.js
29 ms
BrightcoveExperiences.js
46 ms
jquery.cycle.js
46 ms
topstory_pepfar.css
46 ms
reset.css
30 ms
analytics.js
85 ms
iframe_api
85 ms
widgets.js
73 ms
core201.js
55 ms
c_11.xml
118 ms
c_11.xml
116 ms
bkg-gradient-tile.jpg
98 ms
bkg-flag06-pepfar.jpg
111 ms
printbanner950_2010.jpg
9 ms
dos-flag-no-white02.jpg
132 ms
pepfar-logo-seal.png
10 ms
pepfar-logo-text01.png
97 ms
white-pipe.gif
111 ms
searchbox.gif
98 ms
hdr-search-the-site.png
111 ms
search-button.gif
168 ms
global-nav-pepfar.png
167 ms
bkg-global-nav-sub.png
166 ms
hdr-stay-connected-pepfar.png
167 ms
icn-blog.png
130 ms
icn-twitter.png
131 ms
icn-facebook.png
131 ms
icn-flickr.png
132 ms
icn-youtube.png
134 ms
icn-rss-feed.png
134 ms
icn-subscribe.png
135 ms
pepfar-dashboards.png
135 ms
bkg-highlights-short.png
165 ms
bkg-top-story-pagination.png
166 ms
bkg-top-story03.png
196 ms
Purple_20151006_DREAMS_Logo_Reverse_RGB_FOR_WEB_432_1.jpg
169 ms
DRCBoyRaisesFistUSAID_432_1.jpg
170 ms
2015_0518_AIDS_Ribbons_EditedForWeb_432_1.jpg
167 ms
bkg-in-other-news.jpg
188 ms
hdr-in-other-news.png
166 ms
footer-bar.png
194 ms
usa_gov_logo150.gif
170 ms
Abel.woff
194 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
99 ms
collect
142 ms
www-widgetapi.js
85 ms
collect
118 ms
widget020.top.svg.css
15 ms
366948448819347456
178 ms
print.css
7 ms
printtier3.css
4 ms
collect
57 ms
pepfar.gov accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
pepfar.gov 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
Missing source maps for large first-party JavaScript
pepfar.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pepfar.gov can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pepfar.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.
pepfar.gov
Open Graph description is not detected on the main page of Pepfar. 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: