1.3 sec in total
21 ms
876 ms
386 ms
Visit aids.gov now to see the best up-to-date AIDS content for United States and also check out these interesting facts you probably never knew about aids.gov
HIV.gov is the US Government’s gateway to federal HIV policies, programs, and resources to end the HIV epidemic.
Visit aids.govWe analyzed Aids.gov page load time and found that the first response time was 21 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
aids.gov performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value6.1 s
12/100
25%
Value3.6 s
87/100
10%
Value1,240 ms
19/100
30%
Value0.162
72/100
15%
Value9.1 s
33/100
10%
21 ms
85 ms
12 ms
42 ms
17 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 85% of them (62 requests) were addressed to the original Aids.gov, 7% (5 requests) were made to Google-analytics.com and 4% (3 requests) were made to Blog.aids.gov. The less responsive or slowest element that took the longest time to load (491 ms) relates to the external source Blog.aids.gov.
Page size can be reduced by 314.8 kB (19%)
1.6 MB
1.3 MB
In fact, the total size of Aids.gov main page is 1.6 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.2 MB which makes up the majority of the site volume.
Potential reduce by 58.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 9.1 kB, which is 13% 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 58.6 kB or 81% of the original size.
Potential reduce by 29.7 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. AIDS images are well optimized though.
Potential reduce by 125.8 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 125.8 kB or 60% of the original size.
Potential reduce by 100.6 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. Aids.gov needs all CSS files to be minified and compressed as it can save up to 100.6 kB or 83% of the original size.
Number of requests can be reduced by 24 (35%)
69
45
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AIDS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
aids.gov
21 ms
www.aids.gov
85 ms
icomoon.css
12 ms
style.css
42 ms
homepage.css
17 ms
ie8.css
20 ms
responsiveimgs.min.js
18 ms
jquery-1.7.1.min.js
30 ms
plugins.js
36 ms
script.js
17 ms
helper.js
16 ms
swipe.min.js
16 ms
jquery-ui-1.8.20.custom.min.js
17 ms
homepage.js
20 ms
gtm.js
242 ms
gtm.js
277 ms
feeds.php
35 ms
feeds.php
23 ms
feeds.php
25 ms
feeds.php
29 ms
latest_tweet.php
189 ms
body_tile.gif
19 ms
header_back.jpg
22 ms
top_nav_back.jpg
20 ms
bg-top-nav-icons.png
24 ms
magnify_glass.png
23 ms
mega_back.jpg
34 ms
icon_menu.gif
24 ms
logo_ribbon.png
32 ms
logo_text.png
31 ms
nhas_douglas_brooks188.jpg
34 ms
exitaidsdisc.png
32 ms
croi_2016_panel190.jpg
34 ms
voh-brush-graphic-call-out191.jpg
48 ms
women_and_girls_ad159.jpg
45 ms
aca_health_coverage187.jpg
46 ms
viral_hepatitis_action_plan118.jpg
47 ms
bld_sprite.png
47 ms
loading_64x64.gif
50 ms
red_icons.png
50 ms
logo-national-women-girls-hiv-awareness.png
50 ms
logo-national-native-hiv-awareness.png
50 ms
nhas-community-action-plan-framework.jpg
49 ms
bg-service-locator.gif
50 ms
magnifying-glass.png
76 ms
girl_point.png
77 ms
social_icons.gif
77 ms
subscribe-govdelivery.jpg
76 ms
facebook-banner.jpg
75 ms
footer_back.gif
77 ms
icomoon.svg
80 ms
icomoon.woff
68 ms
BebasNeue-webfont.woff
66 ms
bg-service-locator-tab-link.gif
66 ms
bg-service-locator-tab.gif
66 ms
nhas_douglas_brooks188.jpg
67 ms
croi_2016_panel190.jpg
65 ms
voh-brush-graphic-call-out191.jpg
66 ms
women_and_girls_ad159.jpg
65 ms
aca_health_coverage187.jpg
63 ms
croi_four_senarios.png
263 ms
viral_hepatitis_action_plan118.jpg
62 ms
ACA-post-feb-25-image.jpg
442 ms
blackmsm.png
491 ms
blog_icon.png
59 ms
arrow_right_gold.gif
57 ms
analytics.js
82 ms
3698.js
39 ms
linkid.js
10 ms
collect
13 ms
collect
19 ms
collect
25 ms
print.css
5 ms
aids.gov accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
aids.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
Page has valid source maps
aids.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aids.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 Aids.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.
aids.gov
Open Graph description is not detected on the main page of AIDS. 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: