2.1 sec in total
167 ms
1.5 sec
422 ms
Click here to check amazing Flu content for United States. Otherwise, check out these important facts you probably never knew about flu.gov
Everything you need to know about the flu illness, including symptoms, treatment and prevention.
Visit flu.govWe analyzed Flu.gov page load time and found that the first response time was 167 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
flu.gov performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.1 s
48/100
25%
Value5.8 s
50/100
10%
Value1,090 ms
24/100
30%
Value0.452
20/100
15%
Value12.5 s
14/100
10%
167 ms
122 ms
139 ms
49 ms
69 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Flu.gov, 81% (48 requests) were made to Cdc.gov and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (573 ms) relates to the external source Cdc.gov.
Page size can be reduced by 466.8 kB (38%)
1.2 MB
777.8 kB
In fact, the total size of Flu.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 457.9 kB which makes up the majority of the site volume.
Potential reduce by 231.9 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 231.9 kB or 75% of the original size.
Potential reduce by 91 B
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. Flu images are well optimized though.
Potential reduce by 231.1 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 231.1 kB or 50% of the original size.
Potential reduce by 3.7 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. Flu.gov has all CSS files already compressed.
Number of requests can be reduced by 26 (55%)
47
21
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
flu.gov
167 ms
flu
122 ms
139 ms
bootstrap.min.css
49 ms
app.min.css
69 ms
topic_levels.js
39 ms
launch-04da70ea688d.min.js
45 ms
localrd.css
56 ms
style.css
60 ms
css
50 ms
all.css
40 ms
topic_levels.js
177 ms
analytics_cdcgov.js
178 ms
motionpoint.js
183 ms
motionpoint-inline.js
362 ms
cdc_config.js
174 ms
jquery.min.js
175 ms
bootstrap.bundle.min.js
180 ms
ab.js
196 ms
app.min.js
175 ms
2024.banner.js
168 ms
vaxbot-nohover.js
183 ms
h5n1-cow-update.png
44 ms
vaccines-protect-banner.jpg
41 ms
how-to-prevent-banner.jpg
54 ms
flu-treatment-banner.jpg
88 ms
wild-to-mild-banner.png
140 ms
prevent2.png
140 ms
symptoms2.png
192 ms
treatment2.png
141 ms
FluView-graphic.png
140 ms
1918-pandemic-photo.jpg
154 ms
maps-002.png
150 ms
globe.png
178 ms
avian.png
191 ms
swine.png
177 ms
bat.png
451 ms
canine.png
452 ms
transmissions.png
573 ms
id
24 ms
AppMeasurement.min.js
429 ms
AppMeasurement_Module_ActivityMap.min.js
428 ms
dest5.html
22 ms
ibs:dpid=411&dpuuid=ZjgKNQAAAF-s7wN_
4 ms
open-sans-v28-latin-regular.woff
359 ms
open-sans-v28-latin-500.woff
380 ms
cdciconfont.woff
417 ms
7cHqv4kjgoGqM7E3t-4s51oqtz0rdg.woff
16 ms
7cHqv4kjgoGqM7E30-8s51oqtz0rdg.woff
23 ms
7cHqv4kjgoGqM7E3_-gs51oqtz0rdg.woff
33 ms
7cHpv4kjgoGqM7E_DMs_ynghnQ.woff
34 ms
left.png
62 ms
right.png
62 ms
ajax-loader.gif
113 ms
s15630566042382
50 ms
qrcode.min.js
62 ms
bootstrap.min.css
22 ms
app.min.css
48 ms
print.min.css
21 ms
flu.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.
flu.gov 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
flu.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flu.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 Flu.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.
flu.gov
Open Graph data is detected on the main page of Flu. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: