5.5 sec in total
1.4 sec
3.7 sec
410 ms
Click here to check amazing Older content for United States. Otherwise, check out these important facts you probably never knew about older.fitness
Welcome to 40+ Fitness! Through 40+ Online Personal Training and the 40+ Fitness Podcast, thousands of people are improving their health and getting more fit than they've been in decades.
Visit older.fitnessWe analyzed Older.fitness page load time and found that the first response time was 1.4 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
older.fitness performance score
1407 ms
256 ms
18 ms
28 ms
16 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 84% of them (68 requests) were addressed to the original Older.fitness, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Older.fitness.
Page size can be reduced by 986.8 kB (59%)
1.7 MB
672.5 kB
In fact, the total size of Older.fitness main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 626.2 kB which makes up the majority of the site volume.
Potential reduce by 86.3 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 86.3 kB or 83% of the original size.
Potential reduce by 41.2 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. Older images are well optimized though.
Potential reduce by 480.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 480.2 kB or 77% of the original size.
Potential reduce by 379.1 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. Older.fitness needs all CSS files to be minified and compressed as it can save up to 379.1 kB or 86% of the original size.
Number of requests can be reduced by 43 (54%)
79
36
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Older. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.older.fitness
1407 ms
wp-emoji-release.min.js
256 ms
style.css
18 ms
twb_aweber_optin.css
28 ms
styles.css
16 ms
cff-style.css
42 ms
font-awesome.min.css
7 ms
all-skins.css
488 ms
1-popupally-pro-style.css
146 ms
css
27 ms
app-player.css
197 ms
mediaelementplayer.css
235 ms
app-icon.css
60 ms
rrssb.css
101 ms
wpp.css
123 ms
admin_style.min.css
187 ms
css
36 ms
sphinxsearch.css
177 ms
jquery.js
694 ms
jquery-migrate.min.js
238 ms
flowplayer.min.js
428 ms
check-source.min.js
261 ms
1-popupally-pro-code.js
265 ms
popup.min.js
296 ms
bootstrap.css
471 ms
arf_front.css
476 ms
maincss_100.css
515 ms
arforms.js
994 ms
font-awesome.min.css
598 ms
bootstrap.min.js
598 ms
jqBootstrapValidation.js
757 ms
jquery.form.min.js
569 ms
scripts.js
635 ms
cff-scripts.js
827 ms
comment-reply.min.js
592 ms
mediaelement-and-player.min.js
889 ms
wp-mediaelement.js
713 ms
rrssb.min.js
713 ms
popupwindow.js
714 ms
fluidvids.js
715 ms
small-menu.js
714 ms
sticky.js
715 ms
wp-embed.min.js
735 ms
ga.js
40 ms
fbevents.js
81 ms
MYW-MBG2-300x600.jpg
22 ms
74534e2f8f06bfc13b8ae5a87fddee31
57 ms
close.png
21 ms
loading.gif
41 ms
prev.png
40 ms
next.png
41 ms
1500x175_Banner-2.jpg
43 ms
itunes1.png
43 ms
stitcher2.png
42 ms
fb-connect.png
42 ms
Episode_75_238x238-200x200.jpg
54 ms
Episode_74_238x238-200x200.jpg
53 ms
Episode_73_238x238-200x200.jpg
52 ms
Episode_72_238x238-200x200.jpg
56 ms
Episode_71_238x238-200x200.jpg
57 ms
Episode_70_238x238-200x200.jpg
59 ms
Episode_69_238x238-200x200.jpg
56 ms
Episode_68_238x238-200x200.jpg
61 ms
Episode_67_238x238-200x200.jpg
81 ms
Episode_66_238x238-200x200.jpg
81 ms
Episode_65_238x238-200x200.jpg
81 ms
Episode_64_238x238-200x200.jpg
88 ms
Episode_63_238x238-200x200.jpg
84 ms
Episode_62_238x238-200x200.jpg
83 ms
Episode_61_238x238-200x200.jpg
90 ms
1440698519092_formfinal.jpg
93 ms
icon-ivinco.png
79 ms
594-featured-75x75.jpg
83 ms
256-featured-75x75.jpg
83 ms
199-featured-75x75.jpg
84 ms
MG9KbUZFchDs94Tbv9U-paCWcynf_cDxXwCLxiixG1c.ttf
20 ms
__utm.gif
16 ms
30 ms
6awuuqjf85hdp10rzmptbo4xp2mpdud7.js
386 ms
0qbop5xu0ap4eif8.png
68 ms
label_mic_v.png
405 ms
older.fitness SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Older.fitness 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 Older.fitness 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.
older.fitness
Open Graph description is not detected on the main page of Older. 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: