1.3 sec in total
77 ms
984 ms
193 ms
Visit hpforlife.org now to see the best up-to-date Hpforlife content and also check out these interesting facts you probably never knew about hpforlife.org
Learn how Harvard Pilgrim Health Care's Medicare options are right for you. Find answers, compare plans, get information and enroll.
Visit hpforlife.orgWe analyzed Hpforlife.org page load time and found that the first response time was 77 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
hpforlife.org performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value14.2 s
0/100
25%
Value3.1 s
93/100
10%
Value2,630 ms
4/100
30%
Value0.179
67/100
15%
Value8.1 s
41/100
10%
77 ms
198 ms
23 ms
47 ms
17 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 56% of them (20 requests) were addressed to the original Hpforlife.org, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Tags.srv.stackadapt.com. The less responsive or slowest element that took the longest time to load (213 ms) relates to the external source 9603909.fls.doubleclick.net.
Page size can be reduced by 282.4 kB (10%)
2.9 MB
2.7 MB
In fact, the total size of Hpforlife.org main page is 2.9 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. 85% 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. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 40.5 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 8.6 kB, which is 16% 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 40.5 kB or 77% of the original size.
Potential reduce by 241.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. Hpforlife images are well optimized though.
Potential reduce by 114 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 12 (35%)
34
22
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hpforlife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
hpforlife.org
77 ms
gtm.js
198 ms
jquery
23 ms
core
47 ms
modernizr
17 ms
modal
17 ms
carousel
32 ms
ClientThemesBundle
21 ms
conversion.js
32 ms
168 ms
Harvard_Email_Signature_Logos_RGB_small.jpg
77 ms
EnrollBanner.png
76 ms
carousel1.jpg
79 ms
carousel2.jpg
139 ms
meeting_icon_white.png
75 ms
carousel3.jpg
78 ms
carousel4.jpg
140 ms
carousel5.jpg
134 ms
LearnIcon_AEP_2019.png
76 ms
ExploreIcon_AEP_2019.png
78 ms
ConnectIcon_AEP_2019.png
79 ms
mass_lightbox.png
135 ms
icomoon.ttf
78 ms
js
52 ms
bat.js
155 ms
insight.min.js
168 ms
fbevents.js
170 ms
events.js
198 ms
206 ms
activityi;src=9603909;type=all;cat=merkl0;ord=1;num=5308288665582;auiddc=1540525639.1705834103;gtm=45He41h0v846575294;gcd=11l1l1l1l1;dma=0;epver=2;~oref=http%3A%2F%2Fhpforlife.org%2F
213 ms
activityi;src=9603909;type=force1;cat=merkl0;ord=1;num=5551228973456;auiddc=1540525639.1705834103;gtm=45He41h0v846575294;gcd=11l1l1l1l1;dma=0;epver=2;~oref=http%3A%2F%2Fhpforlife.org%2F
205 ms
bounce
20 ms
saq_pxl
8 ms
src=9603909;type=force1;cat=merkl0;ord=1;num=5551228973456;auiddc=*;gtm=45He41h0v846575294;gcd=11l1l1l1l1;dma=0;epver=2;~oref=http%3A%2F%2Fhpforlife.org%2F
51 ms
src=9603909;type=all;cat=merkl0;ord=1;num=5308288665582;auiddc=*;gtm=45He41h0v846575294;gcd=11l1l1l1l1;dma=0;epver=2;~oref=http%3A%2F%2Fhpforlife.org%2F
46 ms
bounce
12 ms
hpforlife.org accessibility score
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-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
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
hpforlife.org 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
hpforlife.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hpforlife.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 Hpforlife.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.
hpforlife.org
Open Graph description is not detected on the main page of Hpforlife. 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: