2.9 sec in total
153 ms
2.5 sec
237 ms
Welcome to health.state.tn.us homepage info - get ready to check Health State best content for United States right away, or after learning these important things about health.state.tn.us
Visit health.state.tn.usWe analyzed Health.state.tn.us page load time and found that the first response time was 153 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
health.state.tn.us performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value15.2 s
0/100
25%
Value8.0 s
22/100
10%
Value630 ms
47/100
30%
Value0.04
99/100
15%
Value19.0 s
3/100
10%
153 ms
851 ms
242 ms
380 ms
149 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Health.state.tn.us, 21% (22 requests) were made to Static.xx.fbcdn.net and 20% (21 requests) were made to Tn.gov. The less responsive or slowest element that took the longest time to load (851 ms) relates to the external source Tn.gov.
Page size can be reduced by 516.1 kB (33%)
1.6 MB
1.1 MB
In fact, the total size of Health.state.tn.us 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. 70% of websites need less resources to load. Images take 837.4 kB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 4.3 kB, which is 11% 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 28.1 kB or 75% of the original size.
Potential reduce by 19.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. Health State images are well optimized though.
Potential reduce by 261.9 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 261.9 kB or 56% of the original size.
Potential reduce by 206.2 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. Health.state.tn.us needs all CSS files to be minified and compressed as it can save up to 206.2 kB or 88% of the original size.
Number of requests can be reduced by 52 (53%)
99
47
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Health State. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
health.state.tn.us
153 ms
health
851 ms
foundation.min.css
242 ms
tngov.site15.css
380 ms
modernizr.js
149 ms
jquery.js
331 ms
css_browser_selector.js
98 ms
tngov.site15.js
278 ms
include.js
152 ms
buttons.js
8 ms
ga.js
33 ms
analytics.js
69 ms
star-ball-bg.png
213 ms
test.jpg
484 ms
Hero_Zika.jpg
286 ms
tn-seal.png
225 ms
footer-starball.png
225 ms
widgets.js
39 ms
OpenSans-Regular-webfont.woff
203 ms
OpenSans-Bold-webfont.woff
356 ms
tngov-icons.woff
394 ms
OpenSans-Italic-webfont.woff
394 ms
OpenSans-BoldItalic-webfont.woff
459 ms
PermianSlabSerifTypeface-webfont.woff
545 ms
PermianSlabSerifTypeface-Bold-webfont.woff
611 ms
sdk.js
36 ms
__utm.gif
48 ms
stat.gif
148 ms
invite.js
162 ms
collect
102 ms
element.js
75 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
67 ms
getAllAppDefault.esi
18 ms
health.svg
372 ms
tn-logo.svg
394 ms
277 ms
xd_arbiter.php
59 ms
xd_arbiter.php
97 ms
606169881118179329
276 ms
translateelement.css
76 ms
main.js
107 ms
getSegment.php
219 ms
checkOAuth.esi
17 ms
element_main.js
52 ms
like_box.php
307 ms
translate_24dp.png
65 ms
l
52 ms
googlelogo_color_42x16dp.png
73 ms
t.dhj
13 ms
t.dhj
9 ms
cm
27 ms
18 ms
s-3271.xgi
10 ms
12 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
7 ms
xrefid.xgi
6 ms
hbpix
77 ms
pixel
42 ms
vUyARus-_normal.png
135 ms
f31votW9_normal.png
167 ms
b6mve75v7mdwl86gtcf9_normal.jpeg
255 ms
2ils97Q4_normal.jpg
379 ms
1v1Yt-bR_normal.png
425 ms
CcGG7sxXEAIUTWd.jpg:small
442 ms
CcFUMiuWEAArVUs.jpg:small
433 ms
CcFKknxUAAAEhNc.jpg:small
440 ms
CcFGh9JW0AUPe5N.jpg:small
433 ms
Cb7h3YeWEAEXwVY.jpg:small
466 ms
CbXJ7QXWwAI3dzv.png:small
468 ms
CatvXdTW8AAIJ5S.jpg:small
460 ms
pixel
32 ms
2981
34 ms
roNeOY-tz5Y.css
45 ms
UHhaxo8Cs3k.css
54 ms
dbNRhrdsQao.css
82 ms
1ssvpqNRk1L.css
98 ms
kCqR6fITdsR.css
97 ms
O8DK6hTywHD.css
102 ms
_rx8naC75Dy.js
116 ms
x5F9OMjKyLw.js
116 ms
ICDbTSzjQEg.js
96 ms
TTCre3391I0.js
113 ms
njO1TPvGzoR.js
114 ms
b_6HNn_J2BZ.js
114 ms
7cm7D75Y0Sf.js
168 ms
rFmE1g6Dkoz.js
174 ms
336JejShbZp.js
149 ms
12565386_10153737529495049_1408586084597933847_n.jpg
109 ms
11207289_10153325383645049_8533828019353928238_n.png
32 ms
12027675_10153820681460049_7136823377683316288_n.jpg
38 ms
12079112_10154085702902873_460599535916353974_n.jpg
54 ms
12801180_10153819887170049_6888621997982826780_n.jpg
58 ms
12734161_10153818492315049_1118389625214024409_n.jpg
58 ms
12745549_843195939122473_7620347492740339501_n.jpg
58 ms
wL6VQj7Ab77.png
23 ms
s7jcwEQH7Sx.png
23 ms
QDwYpIaRyfG.png
22 ms
WC6AgLuP72p.png
22 ms
a-ZN6WoEOje.png
22 ms
jot
126 ms
I6-MnjEovm5.js
8 ms
vlXaquuXMrr.js
15 ms
health.state.tn.us 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
Image elements do not have [alt] attributes
health.state.tn.us 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
health.state.tn.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Health.state.tn.us 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 Health.state.tn.us 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.
health.state.tn.us
Open Graph description is not detected on the main page of Health State. 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: