4 sec in total
181 ms
3.6 sec
249 ms
Visit healthier.com now to see the best up-to-date Health Ier content and also check out these interesting facts you probably never knew about healthier.com
Everyday Health inspires and empowers people to live their healthiest lives, every day, through trusted, medically reviewed information and expert health advice from the nation's leading healthcare pr...
Visit healthier.comWe analyzed Healthier.com page load time and found that the first response time was 181 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
healthier.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value15.4 s
0/100
25%
Value8.5 s
18/100
10%
Value2,810 ms
3/100
30%
Value0.027
100/100
15%
Value21.3 s
1/100
10%
181 ms
931 ms
56 ms
1652 ms
1650 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 9% of them (8 requests) were addressed to the original Healthier.com, 42% (38 requests) were made to Images.healthier.com and 16% (14 requests) were made to Eversave.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Images.healthier.com.
Page size can be reduced by 403.2 kB (62%)
645.1 kB
241.9 kB
In fact, the total size of Healthier.com main page is 645.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 472.5 kB 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. This page needs HTML code to be minified as it can gain 16.3 kB, which is 30% 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 48.1 kB or 88% of the original size.
Potential reduce by 441 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. Health Ier images are well optimized though.
Potential reduce by 322.2 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 322.2 kB or 68% of the original size.
Potential reduce by 32.5 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. Healthier.com needs all CSS files to be minified and compressed as it can save up to 32.5 kB or 86% of the original size.
Number of requests can be reduced by 60 (71%)
85
25
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Health Ier. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
healthier.com
181 ms
www.healthier.com
931 ms
healthier.css
56 ms
core.js
1652 ms
events.js
1650 ms
partner_polls.css
934 ms
PartnerPollsSm.js
962 ms
CarouselSurveysSm.js
965 ms
ebay_activeContent-min.js
277 ms
cb
496 ms
WRb.js
1001 ms
loading.gif
1720 ms
wshealthierheader_110105_01.gif
1608 ms
wshealthierheader_110105_03.jpg
1622 ms
wshealthierheader_110105_04.jpg
1676 ms
wshealthierheader_110105_05.gif
1623 ms
wshealthierheader_110105_06.jpg
1623 ms
wshealthierheader_110105_08.jpg
1803 ms
wshealthierheader_110105_09.jpg
1676 ms
wshehometopsubmit.gif
1682 ms
wshealthierheader_110105_11.jpg
1677 ms
wshealthierheader_110105_13.jpg
1676 ms
wshealthierbody_110105_14.gif
1717 ms
wshealthiernav_110805_01.gif
1716 ms
wshealthiernav_110805_02.gif
1715 ms
wshealthiernav_110805_03.gif
1716 ms
wshealthiernav_110805_04.gif
1715 ms
wshealthiernav_110805_06.gif
1825 ms
wshealthiernav_110805_07.gif
1825 ms
wshealthiernav_110805_08.gif
1799 ms
wshealthiernav_110805_09.gif
1824 ms
he_homebox_flow072606.gif
1799 ms
he_universal_spacer.gif
1873 ms
he_blt_grn_01.gif
1874 ms
he_home_fruit072706.jpg
1856 ms
he_homebox_grflow072606.gif
1869 ms
wshealthierbody_110105_20_2.gif
1832 ms
wshealthierfooter_110105_26.jpg
1855 ms
wshealthierfooter_110105_27.gif
1874 ms
wshealthierfooter_110105_29.gif
1875 ms
wshealthierfooter_110105_30.gif
1873 ms
wshealthierfooter_110105_31.gif
1894 ms
wshealthierfooter_110105_32.gif
1946 ms
log_page.gif
1947 ms
he_homebox_flow072606.gif
1784 ms
he_universal_spacer.gif
1721 ms
he_blt_grn_01.gif
1795 ms
he_home_tomatoes072706.jpg
1868 ms
Banner120x600IF.jsp
33 ms
wshesidenavbullet110905.gif
196 ms
wshenavYELLOWflower.gif
195 ms
wsheheaderimage_5.jpg
347 ms
wshealthierheader_110105_10.jpg
295 ms
wshealthierheader_110105_12.jpg
293 ms
jquery.js
177 ms
jcarousel.js
91 ms
MochiKit.js
211 ms
DynamicFormEmbeddedSm.js
91 ms
librarySm.js
164 ms
show_ads.js
6 ms
bannerspot.gif
190 ms
ca-pub-4434167144055551.js
176 ms
zrt_lookup.html
167 ms
show_ads_impl.js
64 ms
ads
332 ms
osd.js
84 ms
HealthierPollInc.jsp
74 ms
ga.js
8 ms
__utm.gif
17 ms
wshealthierfooter_110105_28.gif
146 ms
detectBrowser.js
30 ms
adjustFrameSize.js
37 ms
he_home_pollbut072706.gif
40 ms
xhpEmbedded
462 ms
xhpEmbedded
180 ms
1x1_for_Impressions.gif
11 ms
m_js_controller.js
79 ms
abg.js
102 ms
jquery.jcarousel.css
140 ms
onepageconveyor.css
141 ms
onepageflowshort.css
48 ms
ShortFormHealthier.css
46 ms
favicon
102 ms
googlelogo_color_112x36dp.png
101 ms
nessie_icon_tiamat_white.png
76 ms
s
42 ms
x_button_blue2.png
26 ms
prev-horizontal.png
48 ms
next-horizontal.png
51 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
healthier.com 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
healthier.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
healthier.com 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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Healthier.com 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 Healthier.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
healthier.com
Open Graph description is not detected on the main page of Health Ier. 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: