Tools & Wizards About Us
johnrothe.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

johnrothe.com

John Rothe | Stock Market and Investment Research

Page Load Speed

1.5 sec in total

First Response

185 ms

Resources Loaded

832 ms

Page Rendered

451 ms

johnrothe.com screenshot

About Website

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

Investment research blog from John Rothe, CMT. Topics focus on technical analysis, including momentum investment strategies, relative strength, and risk management tools.

Visit johnrothe.com

Key Findings

We analyzed Johnrothe.com page load time and found that the first response time was 185 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

johnrothe.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value5.4 s

55/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

johnrothe.com

185 ms

johnrothe.com

338 ms

style-index.css

21 ms

style.min.css

19 ms

et-divi-dynamic-tb-105-381.css

52 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 73% of them (16 requests) were addressed to the original Johnrothe.com, 23% (5 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (338 ms) belongs to the original domain Johnrothe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.2 kB (12%)

Content Size

664.1 kB

After Optimization

584.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 67.9 kB

  • Original 86.5 kB
  • After minification 84.0 kB
  • After compression 18.6 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 67.9 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 11.2 kB

  • Original 549.8 kB
  • After minification 538.6 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. John Rothe images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 18 B

  • Original 3.8 kB
  • After minification 3.8 kB
  • After compression 3.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 69 B

  • Original 24.0 kB
  • After minification 24.0 kB
  • After compression 24.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. Johnrothe.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johnrothe.com

johnrothe.com

185 ms

johnrothe.com

johnrothe.com

338 ms

style-index.css

style-index.css

21 ms

style.min.css

style.min.css

19 ms

et-divi-dynamic-tb-105-381.css

et-divi-dynamic-tb-105-381.css

52 ms

et-core-unified-tb-105-381.min.css

et-core-unified-tb-105-381.min.css

39 ms

et-core-unified-381.min.css

et-core-unified-381.min.css

58 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

30 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

34 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

37 ms

John-Rothe-1.png

John-Rothe-1.png

46 ms

IBM-1970s-stagflation-1080x675.png

IBM-1970s-stagflation-1080x675.png

273 ms

css

css

34 ms

volatility-754x675.png

volatility-754x675.png

148 ms

ulcer-index-example-1080x675.png

ulcer-index-example-1080x675.png

186 ms

John-Rothe-CMT.jpg

John-Rothe-CMT.jpg

56 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQUwaEQXjM.woff

19 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQUwaEQXjM.woff

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQUwaEQXjM.woff

28 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQUwaEQXjM.woff

33 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQUwaEQXjM.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQUwaEQXjM.woff

67 ms

modules.woff

modules.woff

67 ms

Accessibility Review

johnrothe.com accessibility score

83

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

johnrothe.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

johnrothe.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

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 Johnrothe.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 Johnrothe.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

johnrothe.com

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