970 ms in total
36 ms
662 ms
272 ms
Click here to check amazing Phe content for United States. Otherwise, check out these important facts you probably never knew about phe.gov
Visit phe.govWe analyzed Phe.gov page load time and found that the first response time was 36 ms and then it took 934 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
phe.gov performance score
name
value
score
weighting
Value11.7 s
0/100
10%
Value30.7 s
0/100
25%
Value12.2 s
3/100
10%
Value1,030 ms
26/100
30%
Value0
100/100
15%
Value27.2 s
0/100
10%
36 ms
229 ms
11 ms
16 ms
22 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Phe.gov, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (229 ms) belongs to the original domain Phe.gov.
Page size can be reduced by 1.5 MB (74%)
2.0 MB
532.8 kB
In fact, the total size of Phe.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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 48.1 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 48.1 kB or 72% of the original size.
Potential reduce by 31.8 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. Obviously, Phe needs image optimization as it can save up to 31.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 79% of the original size.
Potential reduce by 318.8 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. Phe.gov needs all CSS files to be minified and compressed as it can save up to 318.8 kB or 88% of the original size.
Number of requests can be reduced by 27 (45%)
60
33
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phe. 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 5 to 1 for CSS and as a result speed up the page load time.
phe.gov
36 ms
default.aspx
229 ms
controls.css
11 ms
controls.css
16 ms
search.css
22 ms
corev4.css
107 ms
common.css
19 ms
WebResource.axd
14 ms
blank.js
20 ms
home.js
22 ms
init.js
16 ms
ScriptResource.axd
6 ms
ScriptResource.axd
7 ms
default.aspx
116 ms
ga.js
28 ms
pageBkgnd.jpg
9 ms
hhsBannerBkgnd.gif
10 ms
hhsBanner.gif
10 ms
globalnavBkgnd.jpg
11 ms
tabPreparedness.jpg
12 ms
tabEmergencyBack.jpg
11 ms
tabAboutBack.jpg
12 ms
bannerPreparednessBkgnd.jpg
17 ms
bgximg.png
13 ms
buttonSearch.png
14 ms
localnavBkgnd.jpg
14 ms
Flint-HRSAfunding-Water.jpg
19 ms
flyoutBkgnd.jpg
17 ms
leftboxBkgnd.gif
18 ms
leftboxHeaderBkgnd.gif
19 ms
bulletArrowBlue.gif
20 ms
leftboxEmbeddedHeaderBkgnd.gif
23 ms
centerboxBkgnd.gif
22 ms
centerboxHeaderBkgnd.gif
57 ms
buttonGo.gif
58 ms
ruleDotted.gif
57 ms
PuttingPatientsFirst-feature.jpg
60 ms
centerboxshadedBkgnd.gif
58 ms
bulletArrowBlueHollow.gif
57 ms
CRPERSPC.GIF
59 ms
iconFolder.gif
59 ms
rightboxBkgnd.gif
58 ms
rightboxHeaderBkgnd.gif
62 ms
ASPR-TRACIE-logo-widget-160.jpg
61 ms
badge-nvpo-tracker-tool.png
62 ms
FB-logo.jpg
62 ms
exit-icon.png
60 ms
Twitter.jpg
61 ms
YouTube-32.square.jpg
64 ms
mail4.jpg
63 ms
LinkedIn-Logo2.jpg
59 ms
RSS.jpg
59 ms
footerBkgnd.jpg
60 ms
PHEgovLogo.png
61 ms
__utm.gif
24 ms
flyoutBkgndHover.gif
27 ms
bulletArrowRed.gif
26 ms
undefined
15 ms
core.js
117 ms
sp.core.js
22 ms
ScriptResx.ashx
25 ms
cui.js
89 ms
sp.ui.dialog.js
14 ms
sp.runtime.js
10 ms
sp.js
56 ms
phe.gov accessibility score
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
phe.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
phe.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phe.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 Phe.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.
phe.gov
Open Graph description is not detected on the main page of Phe. 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: