12.3 sec in total
243 ms
10.2 sec
1.9 sec
Visit johnrmeese.com now to see the best up-to-date John R Meese content and also check out these interesting facts you probably never knew about johnrmeese.com
Turn your wisdom into wealth by building a thriving online education business—starting with a FREE Sell Your Smarts Crash Course!
Visit johnrmeese.comWe analyzed Johnrmeese.com page load time and found that the first response time was 243 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
johnrmeese.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value10.3 s
0/100
25%
Value4.4 s
73/100
10%
Value1,830 ms
9/100
30%
Value0.01
100/100
15%
Value6.3 s
61/100
10%
243 ms
287 ms
110 ms
108 ms
109 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Johnrmeese.com, 33% (27 requests) were made to Johnmeese.me and 7% (6 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source D4z6dx8qrln4r.cloudfront.net.
Page size can be reduced by 913.6 kB (39%)
2.3 MB
1.4 MB
In fact, the total size of Johnrmeese.com main page is 2.3 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 52.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. 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 52.4 kB or 77% of the original size.
Potential reduce by 13.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 R Meese images are well optimized though.
Potential reduce by 676.3 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 676.3 kB or 68% of the original size.
Potential reduce by 171.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. Johnrmeese.com needs all CSS files to be minified and compressed as it can save up to 171.9 kB or 85% of the original size.
Number of requests can be reduced by 55 (71%)
78
23
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John R Meese. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
johnrmeese.com
243 ms
johnmeese.me
287 ms
wp-emoji-release.min.js
110 ms
wd-styles.css
108 ms
styles.css
109 ms
style.css
162 ms
style-custom.css
109 ms
style-responsive.css
115 ms
jquery.js
383 ms
jquery-migrate.min.js
139 ms
q2w3-fixed-widget.min.js
139 ms
snippet.js
98 ms
a9a46e605c8d9b995fcfef550ca0ca976d822974.js
99 ms
vertical-m.css
127 ms
load.sumome.com
543 ms
audio-player.js
170 ms
effect.min.js
224 ms
effect-slide.min.js
223 ms
main.min.js
222 ms
wp-embed.min.js
222 ms
fbds.js
334 ms
hotjar-137652.js
335 ms
analytics.js
99 ms
ga.js
91 ms
Header-3.0-bw1.png
78 ms
blog-header-jan25-logotype-tagline.png
1084 ms
sprites.png
79 ms
sprites-18px.png
77 ms
roadrunner.gif
2334 ms
ConvertKit-Giveaway-760x395.jpg
284 ms
Closing-the-Doors-760x507.jpg
885 ms
Dollarphotoclub_91091089-760x528.jpg
888 ms
Headshot-Landscape-1024x682.jpg
1080 ms
centrifuge-sidebar.png
902 ms
widget.js
1008 ms
collect
162 ms
__utm.gif
86 ms
664 ms
modules-79ac3e471402dedc7fa595a0b4974f10.js
674 ms
count.js
535 ms
fbevents.js
508 ms
2b05.png
391 ms
fql
236 ms
404 ms
202 ms
share
236 ms
share
197 ms
share
194 ms
share
196 ms
share
132 ms
jquery.min.js
137 ms
eAtKrG
518 ms
service.js
201 ms
service.js
221 ms
service.js
220 ms
service.js
418 ms
visit-data
324 ms
highlighter-popup.css
66 ms
sumome-scrollbox-popup.css
72 ms
eAtKrG-56f8d2a6bb05f-fallback.css
832 ms
css
351 ms
image-56ef0ec51f287-default.jpeg
999 ms
css
185 ms
status
323 ms
lazy.png
247 ms
spin.min.js
70 ms
jquery.min.js
138 ms
fallback-56f10100175aa-min.js
1543 ms
image-56ef0b750a4d3-default.gif
6423 ms
load
479 ms
load
452 ms
status
383 ms
style-print.css
463 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
284 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
334 ms
fallback
280 ms
share-facebook.png
71 ms
59 ms
share-twitter.png
45 ms
share-linkedin.png
71 ms
share-googleplus.png
94 ms
share-buffer.png
91 ms
johnrmeese.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
johnrmeese.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
johnrmeese.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 Johnrmeese.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 Johnrmeese.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.
johnrmeese.com
Open Graph description is not detected on the main page of John R Meese. 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: