18.1 sec in total
2.6 sec
14.7 sec
837 ms
Click here to check amazing Independenceman content. Otherwise, check out these important facts you probably never knew about independenceman.com
Join me in my journey as I share the practical tools, proper mindsets and knowledge I have been finding to live a life full of freedom and truth guided by love.
Visit independenceman.comWe analyzed Independenceman.com page load time and found that the first response time was 2.6 sec and then it took 15.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
independenceman.com performance score
2557 ms
256 ms
298 ms
287 ms
341 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 79% of them (44 requests) were addressed to the original Independenceman.com, 7% (4 requests) were made to Maps.googleapis.com and 5% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Independenceman.com.
Page size can be reduced by 1.1 MB (22%)
5.1 MB
4.0 MB
In fact, the total size of Independenceman.com main page is 5.1 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. 60% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 46.9 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 13.4 kB, which is 24% 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 46.9 kB or 84% of the original size.
Potential reduce by 296.4 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. Independenceman images are well optimized though.
Potential reduce by 442.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 442.9 kB or 71% of the original size.
Potential reduce by 328.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. Independenceman.com needs all CSS files to be minified and compressed as it can save up to 328.0 kB or 86% of the original size.
Number of requests can be reduced by 36 (68%)
53
17
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Independenceman. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.independenceman.com
2557 ms
wp-emoji-release.min.js
256 ms
parallax.css
298 ms
font-awesome.css
287 ms
style.css
341 ms
bootstrap.css
347 ms
bootstrap-theme.css
293 ms
admin-ajax.php
2287 ms
css
25 ms
jetpack.css
443 ms
jquery.js
622 ms
jquery-migrate.min.js
470 ms
parallax.js
440 ms
modernizr.js
463 ms
carousel.js
542 ms
tipsy.js
520 ms
fields.js
602 ms
jquery.scroll.pack.js
590 ms
supersubs.js
602 ms
superfish.js
681 ms
hoverIntent.js
671 ms
buttons.js
678 ms
ddslick.js
681 ms
js
24 ms
bootstrap.js
723 ms
tabs.js
738 ms
main.js
755 ms
gmap.js
756 ms
devicepx-jetpack.js
6 ms
gprofiles.js
54 ms
wpgroho.js
760 ms
wp-embed.min.js
796 ms
e-201613.js
6 ms
reset.css
496 ms
pattern_8.png
1720 ms
list-style.png
418 ms
header_tagline2.jpg
558 ms
trans.png
416 ms
WPPodcast.jpg
423 ms
IMPC002.jpg
418 ms
IM0031.jpg
488 ms
I-am-who-I-am.jpg
1553 ms
I-am-who-I-am-680x330.jpg
542 ms
20150722_233958-680x330.jpg
654 ms
20150709_202752.jpg
1272 ms
WPPodcast-372x360.jpg
726 ms
no-thumbnail.jpg
661 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
22 ms
icomoon.ttf
754 ms
fontawesome-webfont.woff
830 ms
common.js
4 ms
util.js
19 ms
geocoder.js
4 ms
g.gif
266 ms
hovercard.css
27 ms
services.css
52 ms
independenceman.com SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Independenceman.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Independenceman.com 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.
independenceman.com
Open Graph data is detected on the main page of Independenceman. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: