4 sec in total
1.4 sec
2.2 sec
398 ms
Click here to check amazing 60 Plus content for United States. Otherwise, check out these important facts you probably never knew about 60plus.org
A non-partisan seniors advocacy group with a free enterprise, less government, less taxes approach to seniors issues.
Visit 60plus.orgWe analyzed 60plus.org page load time and found that the first response time was 1.4 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
60plus.org performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value11.6 s
0/100
25%
Value10.5 s
7/100
10%
Value690 ms
43/100
30%
Value0.004
100/100
15%
Value14.4 s
9/100
10%
1366 ms
8 ms
10 ms
12 ms
14 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 59% of them (58 requests) were addressed to the original 60plus.org, 10% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Farm8.staticflickr.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain 60plus.org.
Page size can be reduced by 774.6 kB (56%)
1.4 MB
619.8 kB
In fact, the total size of 60plus.org main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 734.8 kB which makes up the majority of the site volume.
Potential reduce by 40.8 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 40.8 kB or 80% of the original size.
Potential reduce by 4.3 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. 60 Plus images are well optimized though.
Potential reduce by 499.4 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 499.4 kB or 68% of the original size.
Potential reduce by 230.0 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. 60plus.org needs all CSS files to be minified and compressed as it can save up to 230.0 kB or 82% of the original size.
Number of requests can be reduced by 51 (53%)
96
45
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 60 Plus. 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.
60plus.org
1366 ms
style.css
8 ms
scripts.js
10 ms
thickbox.css
12 ms
styles.css
14 ms
youtube-channel.min.css
14 ms
magnific-popup.min.css
12 ms
colorbox.css
25 ms
jquery.js
17 ms
jquery.ui.core.min.js
13 ms
jquery.ui.effect.min.js
22 ms
jquery.ui.effect-fade.min.js
22 ms
jquery.caret.min.js
22 ms
highcharts.js
20 ms
exporting.js
52 ms
audio-player.js
50 ms
campaign_voter.css
49 ms
moment.js
48 ms
langs.min.js
48 ms
topbg.png
24 ms
leftborder.jpg
8 ms
rightborder.jpg
7 ms
topleftborder.jpg
10 ms
toprightborder.jpg
18 ms
searchtab.png
8 ms
searchglass.jpg
11 ms
joinbutton.gif
10 ms
donatebutton.gif
12 ms
icon-rss.png
13 ms
banner.png
13 ms
printbanner.png
16 ms
pr-no-default.jpg
14 ms
epamandate.jpg
14 ms
boone.jpg
15 ms
facebooklogo.jpg
13 ms
likebox.php
249 ms
kyEKgjk51ZE.css
45 ms
xgj7bXhJNEH.css
47 ms
q68gy-v_YMF.js
54 ms
FJmpeSpHpjS.js
75 ms
0wM5s1Khldu.js
53 ms
1bNoFZUdlYZ.js
51 ms
1779186_10151971559131025_1752583040_n.jpg
48 ms
1915287_10153592044701025_2344857433955012153_n.png
13 ms
62598_101992420003629_629006589_n.jpg
11 ms
998091_419936444791835_969449059_n.jpg
11 ms
10003883_757604494257908_1165222936_n.jpg
13 ms
12299358_897107733671784_3143441106203944651_n.jpg
9 ms
wL6VQj7Ab77.png
7 ms
s7jcwEQH7Sx.png
8 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
4 ms
YouTube.png
4 ms
rss.png
43 ms
twitter.gif
9 ms
widgets.js
11 ms
16750968299_0bd1ba5cf8_c.jpg
95 ms
16936193221_e1b2d517bf_c.jpg
96 ms
flickr.gif
10 ms
16750968629_ae30f304c1_c.jpg
91 ms
16935856982_ec74429be2_c.jpg
93 ms
16750968729_f5ed69a7a1_c.jpg
94 ms
16911237696_d277de7bd1_c.jpg
92 ms
16749500028_d272b8d027_c.jpg
91 ms
16911237856_216a168d93_c.jpg
94 ms
16749500278_be619c2b86_c.jpg
95 ms
thickbox.js
32 ms
jquery.colorbox-min.js
53 ms
jquery.form.min.js
30 ms
scripts.js
35 ms
jquery.magnific-popup.min.js
37 ms
youtube-channel.min.js
31 ms
Fredd-logo.gif
29 ms
bottomredbg.jpg
31 ms
bottomleftborder.jpg
35 ms
bottomrightborder.jpg
31 ms
60P_Logo_sm.png
33 ms
facebook_footer.jpg
868 ms
transpix.gif
35 ms
twitter_footer.jpg
36 ms
flickr_footer.jpg
35 ms
YouTube_footer.jpg
36 ms
yVjQEoKm_aA
111 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
22 ms
border1.png
16 ms
border2.png
28 ms
loading.gif
15 ms
loadingAnimation.gif
15 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
19 ms
info.json
138 ms
www-embed-player-vflfNyN_r.css
73 ms
www-embed-player.js
94 ms
base.js
163 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
45 ms
ad_status.js
48 ms
jot
119 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
87 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
92 ms
printstyle.css
4 ms
60plus.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
Links do not have a discernible name
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.
60plus.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
Page has valid source maps
60plus.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 60plus.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 60plus.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.
60plus.org
Open Graph description is not detected on the main page of 60 Plus. 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: