2.9 sec in total
917 ms
1.8 sec
151 ms
Visit denverpublichealth.org now to see the best up-to-date Denver Public Health content for United States and also check out these interesting facts you probably never knew about denverpublichealth.org
The Public Health Institute at Denver Health offers a variety of clinical services to Colorado and Denver residents
Visit denverpublichealth.orgWe analyzed Denverpublichealth.org page load time and found that the first response time was 917 ms and then it took 2 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.
denverpublichealth.org performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value7.4 s
4/100
25%
Value10.7 s
7/100
10%
Value630 ms
48/100
30%
Value0.438
21/100
15%
Value14.0 s
10/100
10%
917 ms
89 ms
143 ms
122 ms
133 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 91% of them (100 requests) were addressed to the original Denverpublichealth.org, 2% (2 requests) were made to Apis.google.com and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (917 ms) belongs to the original domain Denverpublichealth.org.
Page size can be reduced by 3.5 MB (70%)
5.0 MB
1.5 MB
In fact, the total size of Denverpublichealth.org main page is 5.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 101.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 101.9 kB or 86% of the original size.
Potential reduce by 924.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. Obviously, Denver Public Health needs image optimization as it can save up to 924.6 kB or 54% 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.9 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.9 MB or 75% of the original size.
Potential reduce by 569.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. Denverpublichealth.org needs all CSS files to be minified and compressed as it can save up to 569.7 kB or 85% of the original size.
Number of requests can be reduced by 87 (83%)
105
18
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Denver Public Health. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
denverpublichealth.org
917 ms
minimalist.css
89 ms
base.css
143 ms
default.css
122 ms
ie.css
133 ms
module.css
135 ms
module.css
72 ms
skin.css
106 ms
DPH.css
147 ms
container.css
136 ms
Container01.css
151 ms
Container03.css
157 ms
Footer.css
161 ms
portal.css
163 ms
cache_skin_DPH.css
166 ms
cache_skin_DPH%20-%20Footer.css
175 ms
trans-banner.css
177 ms
sirius.css
185 ms
rateit.css
188 ms
all.css
192 ms
bootstrap.min.css
225 ms
colorpicker.css
201 ms
fancybox.css
203 ms
font-awesome.min.css
213 ms
TableLayoutCss.css
218 ms
styles.css
220 ms
cache_skin_DPH-Header.css
237 ms
cache_skin_DPH.css
237 ms
module.css
242 ms
bootstrap.min.css
296 ms
jquery.js
286 ms
jquery-migrate.js
251 ms
jquery-ui.js
328 ms
eds1.8.2.js
293 ms
eds2.2.3.js
307 ms
EasyDnnSolutions_1.1_2.2.js
279 ms
plusone.js
54 ms
WebResource.axd
279 ms
dnncore.js
256 ms
jquery.mousewheel.min.js
248 ms
jquery.tinyscrollbar.js
230 ms
flowplayer.min.js
227 ms
jquery.chameleonSlider.min.js
224 ms
NavXpJsClient--1633394243.js
236 ms
css
15 ms
Telerik.Web.UI.WebResource.axd
245 ms
dnn.js
231 ms
jquery.hoverIntent.min.js
218 ms
jquery.iframe-transport.js
232 ms
jquery.fileupload.js
231 ms
dnn.servicesframework.js
235 ms
jquery.rateit_2.2.js
233 ms
script.js
229 ms
dnncore.js
232 ms
dnn.jquery.js
242 ms
dnn.analytics.Injected.js
229 ms
jquery.cookie_2.2.js
235 ms
responsive.css
226 ms
dnnsf.js
307 ms
bootstrap.min.js
303 ms
typeahead.11.min.js
290 ms
sb-client.js
287 ms
jquery.hoverIntent.min.js
286 ms
jquery-ui.min.js
272 ms
StandardMenu.js
269 ms
MegaMenu.js
269 ms
trans-banner.min.js
266 ms
scrolltop.js
254 ms
scrolltop.call.js
226 ms
jquery.fancybox.min.js
223 ms
jquery.mousewheel.min.js
214 ms
animatedcollapse.js
227 ms
jquery.easing.1.3.min.js
228 ms
jquery.tipsy.js
227 ms
colorpicker.js
222 ms
eye.js
215 ms
utils.js
214 ms
jquery.cookie.js
212 ms
bootstrap.js
238 ms
jquery.accordion.js
235 ms
jquery.carouFredSel-6.2.0-packed.js
223 ms
jquery.quovolver.js
223 ms
shake.js
222 ms
custom.js
210 ms
initWidgets.js
208 ms
dc.js
58 ms
siteanalyze_67285.js
59 ms
DPH-Logo.png
80 ms
mobileUI_nav.png
81 ms
cb=gapi.loaded_0
22 ms
__utm.gif
20 ms
ga-audiences
58 ms
analytics.js
27 ms
fontawesome-webfont.woff
53 ms
glyphicons-halflings-regular.woff
53 ms
glyphicons-halflings-regular.woff
52 ms
DHH-MenuBG.png
43 ms
cache_skin_DPH.css
43 ms
collect
24 ms
DotNetNukeAjaxShared.js
72 ms
ChameleonData.ashx
44 ms
loading_white_bg.gif
34 ms
widgets.js
33 ms
image.aspx
8 ms
5ncgqgga.png
46 ms
w5y5rm0r.png
42 ms
szyflptw.png
45 ms
jdevb4t3.png
117 ms
DPH-Left_Arrow.png
43 ms
DPH-Right_Arrow.png
34 ms
denverpublichealth.org accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
denverpublichealth.org 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
denverpublichealth.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Denverpublichealth.org 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 Denverpublichealth.org 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.
denverpublichealth.org
Open Graph description is not detected on the main page of Denver Public Health. 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: