Analyze

Page load speed analysis

  • 59/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    243 ms

  • Resources loaded

    10.2 sec

  • Page rendered

    1.9 sec

  • Total page load time

    12.3 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

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

Page optimization

  • HTML 68.5 kB
    Images 1.1 MB
    Javascripts 1.2 MB
    CSS 202.7 kB

    In fact, the total size of Johnrmeese.com main page is 2.5 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. 60% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

    • Original 68.5 kB
    • After minification 66.4 kB
    • After compression 16.1 kB

    HTML optimization

    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.

    • Original 1.1 MB
    • After optimization 1.0 MB

    Image optimization

    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.

    • Original 1.2 MB
    • After minification 1.1 MB
    • After compression 359.6 kB

    JavaScript optimization

    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 792.5 kB or 69% of the original size.

    • Original 202.7 kB
    • After minification 176.4 kB
    • After compression 30.8 kB

    CSS optimization

    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.

Network requests diagram

  • johnrmeese.com
  • johnmeese.me
  • wp-emoji-release.min.js
  • wd-styles.css
  • styles.css
  • style.css
  • style-custom.css
  • style-responsive.css
  • jquery.js
  • jquery-migrate.min.js
  • q2w3-fixed-widget.min.js
  • snippet.js
  • a9a46e605c8d9b995fcfef550ca0ca976d822974.js
  • vertical-m.css
  • load.sumome.com
  • audio-player.js
  • effect.min.js
  • effect-slide.min.js
  • main.min.js
  • wp-embed.min.js
  • fbds.js
  • hotjar-137652.js
  • analytics.js
  • ga.js
  • Header-3.0-bw1.png
  • blog-header-jan25-logotype-tagline.png
  • sprites.png
  • sprites-18px.png
  • roadrunner.gif
  • ConvertKit-Giveaway-760x395.jpg
  • Closing-the-Doors-760x507.jpg
  • Dollarphotoclub_91091089-760x528.jpg
  • Headshot-Landscape-1024x682.jpg
  • centrifuge-sidebar.png
  • widget.js
  • collect
  • __utm.gif
  • modules-79ac3e471402dedc7fa595a0b4974f10.js
  • count.js
  • fbevents.js
  • 2b05.png
  • fql
  • share
  • share
  • share
  • share
  • share
  • jquery.min.js
  • eAtKrG
  • service.js
  • service.js
  • service.js
  • service.js
  • visit-data
  • highlighter-popup.css
  • sumome-scrollbox-popup.css
  • eAtKrG-56f8d2a6bb05f-fallback.css
  • css
  • image-56ef0ec51f287-default.jpeg
  • css
  • status
  • lazy.png
  • spin.min.js
  • jquery.min.js
  • fallback-56f10100175aa-min.js
  • image-56ef0b750a4d3-default.gif
  • load
  • load
  • status
  • style-print.css
  • ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
  • toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
  • fallback
  • share-facebook.png
  • share-twitter.png
  • share-linkedin.png
  • share-googleplus.png
  • share-buffer.png

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.

Additional info on johnrmeese.com

Requests

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.

34

Javascripts

24

Images

12

CSS

8

AJAX

78

All

Possible request optimization

1

Javascripts

13

Images

1

CSS

8

AJAX

55

Optimized

23

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.johnmeese.me/ before it reached this domain.

IP address

Johnrmeese.com uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

johnrmeese.com

teedoz.com

bikini-dare.com

komodomedia.com

xmovie.com

64.98.145.30

DNS records

Type Host Target/ip TTL Other
A

johnrmeese.com

64.98.145.30 892
NS

johnrmeese.com

ns1.hover.com 900
NS

johnrmeese.com

ns2.hover.com 900
SOA

johnrmeese.com

900 Mname: ns1.hover.com
Rname: dnsmaster.hover.com
Serial: 1465323408
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum-ttl: 900
MX

johnrmeese.com

mx.hover.com.cust.hostedemail.com 900 Pri: 10

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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.

HTTPS certificate

SSL Certificate

Johnrmeese.com has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Johnrmeese.com is located in Canada, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Normal result

Social Sharing Optimization

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:

johnrmeese.com

Share this report in social media

Analyze another website

Analyze