Tools & Wizards About Us
richlifebreakthrough.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

richlifebreakthrough.com

Home - Noah St. John Official Website

Page Load Speed

5.9 sec in total

First Response

280 ms

Resources Loaded

5.3 sec

Page Rendered

366 ms

richlifebreakthrough.com screenshot

About Website

Welcome to richlifebreakthrough.com homepage info - get ready to check Richlifebreakthrough best content right away, or after learning these important things about richlifebreakthrough.com

Noah St. John is famous for inventing AFFORMATIONS® and helping people get rid of their head trash. Success coaching, time management and business services.

Visit richlifebreakthrough.com

Key Findings

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

Performance Metrics

richlifebreakthrough.com performance score

0

Network Requests Diagram

noahstjohn.com

280 ms

css

24 ms

css

35 ms

bootstrap.css

799 ms

starter-template.css

727 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Richlifebreakthrough.com, 8% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Noahstjohn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (47%)

Content Size

2.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Richlifebreakthrough.com main page is 2.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. 70% of websites need less resources to load. Images take 921.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 86.9 kB

  • Original 109.7 kB
  • After minification 102.6 kB
  • After compression 22.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 86.9 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 12.9 kB

  • Original 921.2 kB
  • After minification 908.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. Richlifebreakthrough images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 532.9 kB

  • Original 868.6 kB
  • After minification 842.2 kB
  • After compression 335.7 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 532.9 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 621.8 kB

  • Original 768.3 kB
  • After minification 720.0 kB
  • After compression 146.5 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. Richlifebreakthrough.com needs all CSS files to be minified and compressed as it can save up to 621.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (65%)

Requests Now

82

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

noahstjohn.com

noahstjohn.com

280 ms

css

css

24 ms

css

css

35 ms

bootstrap.css

bootstrap.css

799 ms

starter-template.css

starter-template.css

727 ms

jasny-bootstrap.min.css

jasny-bootstrap.min.css

725 ms

0c46009c.js

0c46009c.js

74 ms

q-a-plus.css

q-a-plus.css

717 ms

style.css

style.css

788 ms

foobox.min.css

foobox.min.css

728 ms

style-1.css

style-1.css

865 ms

settings.css

settings.css

814 ms

style.min.css

style.min.css

870 ms

v11.css

v11.css

814 ms

style.css

style.css

861 ms

colorbox.min.css

colorbox.min.css

862 ms

jquery-2.2.1.min.js

jquery-2.2.1.min.js

957 ms

jquery-migrate-1.3.0.min.js

jquery-migrate-1.3.0.min.js

889 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1014 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

942 ms

api.min.js

api.min.js

7 ms

foobox.min.js

foobox.min.js

998 ms

getTrackingCode

getTrackingCode

402 ms

2054-9677.js

2054-9677.js

67 ms

q-a-plus.js

q-a-plus.js

882 ms

jquery.adrotate.clicktracker.js

jquery.adrotate.clicktracker.js

900 ms

qppr_frontend_script.min.js

qppr_frontend_script.min.js

955 ms

effect.min.js

effect.min.js

957 ms

effect-slide.min.js

effect-slide.min.js

996 ms

main.min.js

main.min.js

994 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

1070 ms

jquery.colorbox.1.5.9-min.js

jquery.colorbox.1.5.9-min.js

1069 ms

wp-embed.min.js

wp-embed.min.js

1070 ms

jquery.js

jquery.js

1108 ms

bootstrap.js

bootstrap.js

1078 ms

ie10-viewport-bug-workaround.js

ie10-viewport-bug-workaround.js

1079 ms

jasny-bootstrap.min.js

jasny-bootstrap.min.js

1095 ms

js

js

57 ms

main.js

main.js

1135 ms

0c46009c.css

0c46009c.css

18 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

351 ms

analytics.js

analytics.js

26 ms

j.php

j.php

10 ms

NSJ2.jpg

NSJ2.jpg

392 ms

about.jpg

about.jpg

392 ms

sprites.png

sprites.png

391 ms

nsj-logo-shield.png

nsj-logo-shield.png

392 ms

new-banner-11-12-15-new1.jpg

new-banner-11-12-15-new1.jpg

772 ms

imgA.png

imgA.png

390 ms

imgB.png

imgB.png

478 ms

imgC.png

imgC.png

455 ms

imgA.png

imgA.png

453 ms

imgB.png

imgB.png

455 ms

imgC.png

imgC.png

453 ms

bigger-as-seen.jpg

bigger-as-seen.jpg

679 ms

screenshot.png

screenshot.png

624 ms

Get-Your-Foot-book1.png

Get-Your-Foot-book1.png

805 ms

cropped-logo.png

cropped-logo.png

520 ms

gtm.js

gtm.js

74 ms

la-rS4zYkT0

la-rS4zYkT0

374 ms

v.gif

v.gif

58 ms

collect

collect

31 ms

collect

collect

30 ms

1.png

1.png

551 ms

2.png

2.png

710 ms

3IDj6a12RTc

3IDj6a12RTc

312 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

104 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

260 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

262 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

306 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

306 ms

Y_TKV6o8WovbUd3m_X9aAA.ttf

Y_TKV6o8WovbUd3m_X9aAA.ttf

306 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

686 ms

js

js

12 ms

foot-bg.png

foot-bg.png

1903 ms

collect

collect

290 ms

spacer.gif

spacer.gif

312 ms

7b7670b3-4685-4705-8beb-644c016b68f9.js

7b7670b3-4685-4705-8beb-644c016b68f9.js

574 ms

9YNLL0bmRhcNrOmsDG4uAAABk8kbAAAAA==

9YNLL0bmRhcNrOmsDG4uAAABk8kbAAAAA==

19 ms

foobox.svg

foobox.svg

1381 ms

foobox.woff

foobox.woff

1315 ms

in.php

in.php

136 ms

www-embed-player-vflRGs1ko.css

www-embed-player-vflRGs1ko.css

62 ms

www-embed-player.js

www-embed-player.js

85 ms

base.js

base.js

157 ms

spacer.gif

spacer.gif

84 ms

ga-audiences

ga-audiences

32 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

20 ms

ad_status.js

ad_status.js

73 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

73 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

83 ms

blank.gif

blank.gif

14 ms

help_green_bottom_en.png

help_green_bottom_en.png

46 ms

style-print.css

style-print.css

70 ms

213 ms

SEO Factors

richlifebreakthrough.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richlifebreakthrough.com 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 Richlifebreakthrough.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

richlifebreakthrough.com

Open Graph description is not detected on the main page of Richlifebreakthrough. 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: