4.2 sec in total
97 ms
3.3 sec
855 ms
Click here to check amazing John Mauldin content. Otherwise, check out these important facts you probably never knew about johnmauldin.com
Follow John Mauldin as he uncovers the truth behind, and beyond, the financial headlines. This in-depth weekly dispatch helps you understand what's happening in the economy and navigate the markets wi...
Visit johnmauldin.comWe analyzed Johnmauldin.com page load time and found that the first response time was 97 ms 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.
johnmauldin.com performance score
name
value
score
weighting
Value8.7 s
0/100
10%
Value11.6 s
0/100
25%
Value8.7 s
16/100
10%
Value3,950 ms
1/100
30%
Value0.858
4/100
15%
Value22.8 s
1/100
10%
97 ms
40 ms
1005 ms
853 ms
825 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Johnmauldin.com, 51% (25 requests) were made to Images.mauldineconomics.com and 16% (8 requests) were made to Mauldineconomics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Mauldineconomics.com.
Page size can be reduced by 412.3 kB (60%)
688.0 kB
275.7 kB
In fact, the total size of Johnmauldin.com main page is 688.0 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. 70% of websites need less resources to load. Javascripts take 354.8 kB which makes up the majority of the site volume.
Potential reduce by 97.4 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 31.9 kB, which is 27% 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 97.4 kB or 84% of the original size.
Potential reduce by 5.0 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 Mauldin images are well optimized though.
Potential reduce by 273.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 273.9 kB or 77% of the original size.
Potential reduce by 35.9 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. Johnmauldin.com needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 84% of the original size.
Number of requests can be reduced by 38 (84%)
45
7
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Mauldin. 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 13 to 1 for CSS and as a result speed up the page load time.
johnmauldin.com
97 ms
www.mauldineconomics.com
40 ms
www.mauldineconomics.com
1005 ms
jquery-3.5.1.min.js
853 ms
jquery-migrate-3.3.0.min.js
825 ms
css2
898 ms
bootstrap.min.css
925 ms
font-awesome.min.css
985 ms
hs.megamenu.css
888 ms
hamburgers.min.css
885 ms
www.mauldineconomics.com
617 ms
www.mauldineconomics.com
999 ms
www.mauldineconomics.com
1175 ms
www.mauldineconomics.com
937 ms
dzsparallaxer.css
908 ms
slick.css
898 ms
www.mauldineconomics.com
957 ms
jquery.validate.min.js
957 ms
additional-methods.js
968 ms
recaptcha.js
1140 ms
api.js
942 ms
popper.min.js
1105 ms
bootstrap.min.js
1021 ms
lazysizes.min.js
766 ms
hs.megamenu.js
820 ms
appear.js
806 ms
hs.core.js
806 ms
hs.header.js
919 ms
hs.hamburgers.js
768 ms
hs.dropdown.js
781 ms
hs.tabs.js
782 ms
hs.popup.js
943 ms
hs.go-to.js
1091 ms
hs.onscroll-animation.js
941 ms
dzsparallaxer.js
941 ms
slick.js
954 ms
hs.carousel.js
920 ms
exit-popup-js
1065 ms
gtm.js
329 ms
mautic-form.js
94 ms
logo-2.png
268 ms
HAA-homepage-banner.png
269 ms
HAA-homepage-banner-tab.png
264 ms
recaptcha__en.js
440 ms
topbar-background.png
176 ms
stock-ticker-background.jpg
174 ms
fontawesome-webfont.woff
149 ms
uwt.js
403 ms
modal.min.css
242 ms
johnmauldin.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
johnmauldin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
johnmauldin.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnmauldin.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 Johnmauldin.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.
johnmauldin.com
Open Graph description is not detected on the main page of John Mauldin. 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: