Tools & Wizards About Us
johnwmann.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

johnwmann.com

johnwmann.com

Page Load Speed

4.5 sec in total

First Response

933 ms

Resources Loaded

3.2 sec

Page Rendered

326 ms

johnwmann.com screenshot

About Website

Visit johnwmann.com now to see the best up-to-date Johnwmann content and also check out these interesting facts you probably never knew about johnwmann.com

By John Mann Learn To Do Affiliate Marketing The Right Way!   March 2016 Niche60 is Michael Brown’s newest course on how to make money as an Affiliate Marketer and believe me, this product really work...

Visit johnwmann.com

Key Findings

We analyzed Johnwmann.com page load time and found that the first response time was 933 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

johnwmann.com performance score

0

Network Requests Diagram

www.johnwmann.com

933 ms

style.css

208 ms

style.css.php

444 ms

jquery.js

358 ms

jquery-migrate.min.js

246 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 50% of them (18 requests) were addressed to the original Johnwmann.com, 8% (3 requests) were made to S.ytimg.com and 6% (2 requests) were made to D5k6iufjynyu8.cloudfront.net. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Johnwmann.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 497.6 kB (64%)

Content Size

771.5 kB

After Optimization

273.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnwmann.com main page is 771.5 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. 50% of websites need less resources to load. Javascripts take 391.0 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 20.7 kB

  • Original 29.5 kB
  • After minification 28.5 kB
  • After compression 8.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 20.7 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 3.9 kB

  • Original 86.0 kB
  • After minification 82.1 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. Johnwmann images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 253.2 kB

  • Original 391.0 kB
  • After minification 383.0 kB
  • After compression 137.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 253.2 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 219.8 kB

  • Original 265.0 kB
  • After minification 257.8 kB
  • After compression 45.2 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. Johnwmann.com needs all CSS files to be minified and compressed as it can save up to 219.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (55%)

Requests Now

33

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Johnwmann. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.johnwmann.com

www.johnwmann.com

933 ms

style.css

style.css

208 ms

style.css.php

style.css.php

444 ms

jquery.js

jquery.js

358 ms

jquery-migrate.min.js

jquery-migrate.min.js

246 ms

jquery.cross-slide.js

jquery.cross-slide.js

238 ms

md5.js

md5.js

223 ms

contact-page-plugin.js

contact-page-plugin.js

299 ms

button.js

button.js

128 ms

comment-reply.min.js

comment-reply.min.js

278 ms

wp-embed.min.js

wp-embed.min.js

240 ms

reset.css

reset.css

139 ms

grid.css

grid.css

174 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

101 ms

Intro.png

Intro.png

399 ms

seogear_2_300x250.gif

seogear_2_300x250.gif

129 ms

MarketSamuraiBanner1.jpg

MarketSamuraiBanner1.jpg

395 ms

sdk.js

sdk.js

405 ms

grad.gif

grad.gif

108 ms

vLTT1wDscm8

vLTT1wDscm8

324 ms

sidebar-h4-bg.gif

sidebar-h4-bg.gif

284 ms

counter.js

counter.js

20 ms

t.php

t.php

256 ms

onlywire_button.png

onlywire_button.png

46 ms

header-resized-image-960x156.jpg

header-resized-image-960x156.jpg

223 ms

www-embed-player-vflRGs1ko.css

www-embed-player-vflRGs1ko.css

166 ms

www-embed-player.js

www-embed-player.js

208 ms

base.js

base.js

265 ms

82 ms

106 ms

xd_arbiter.php

xd_arbiter.php

428 ms

xd_arbiter.php

xd_arbiter.php

632 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

169 ms

ad_status.js

ad_status.js

174 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

155 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

156 ms

SEO Factors

johnwmann.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnwmann.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Johnwmann.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.

Social Sharing Optimization

johnwmann.com

Open Graph data is detected on the main page of Johnwmann. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: