Analyze

Page load speed analysis

  • 56/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    478 ms

  • Resources loaded

    4 sec

  • Page rendered

    244 ms

  • Total page load time

    4.7 sec

Visit catchball.co now to see the best up-to-date Catchball content for Japan and also check out these interesting facts you probably never knew about catchball.co

We analyzed Catchball.co page load time and found that the first response time was 478 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Page optimization

  • HTML 16.5 kB
    Images 513.3 kB
    Javascripts 142.4 kB
    CSS 41.6 kB

    In fact, the total size of Catchball.co main page is 713.7 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. 45% of websites need less resources to load. Images take 513.3 kB which makes up the majority of the site volume.

    • Original 16.5 kB
    • After minification 12.6 kB
    • After compression 3.9 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. This page needs HTML code to be minified as it can gain 3.9 kB, which is 24% 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 12.6 kB or 76% of the original size.

    • Original 513.3 kB
    • After optimization 504.0 kB

    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. Catchball images are well optimized though.

    • Original 142.4 kB
    • After minification 142.3 kB
    • After compression 54.4 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 88.0 kB or 62% of the original size.

    • Original 41.6 kB
    • After minification 30.5 kB
    • After compression 6.5 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. Catchball.co needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 84% of the original size.

Network requests diagram

  • catchball.co
  • products.ch3cooh.jp
  • css
  • modernizr
  • adsbygoogle.js
  • jquery
  • bootstrap
  • css
  • 328x328
  • 1458264600
  • 1457754082
  • 1457697495
  • 1457577440
  • 1457487966
  • 1457485200
  • 328x328
  • 328x328
  • 328x328
  • 328x328
  • 328x328
  • 328x328
  • icon_pixishare_thum.png
  • v0SdcGFAl2aezM9Vq_aFTQ.ttf
  • DvlFBScY1r-FMtZSYIYoYw.ttf
  • ca-pub-6275292186973463.js
  • zrt_lookup.html
  • show_ads_impl.js
  • analytics.js
  • ads
  • osd.js
  • collect
  • 00006.gif
  • embed.css
  • http%3A%2F%2Fcdn.mogile.archive.st-hatena.com%2Fv1%2Fimage%2Fch3cooh393%2F297786671183086532.png
  • entry.count.image
  • 1457577440
  • http%3A%2F%2Fcdn.image.st-hatena.com%2Fimage%2Fscale%2F1aacf11e8a50a662d2e1c3869bb233cca601882a%2Fenlarge%3D0%3Bheight%3D200%3Bversion%3D1%3Bwidth%3D200%2Fhttp%253A%252F%252Fis3.mzstatic.com%252Fimage%252Fthumb%252FPurple49%252Fv4%252Faa%252Fc3%252F42%252Faac342fa-602c-a157-59b0-82e05370fe66%252Fsource%252F100x100bb.jpg
  • embed-logo.gif
  • entry.count.image
  • 1457697495
  • 00000.gif
  • 00000.gif
  • 00002.gif
  • entry.count.image
  • http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fc%2Fch3cooh393%2F20160317%2F20160317142228.png
  • 1458264600
  • entry.count.image
  • http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fc%2Fch3cooh393%2F20160309%2F20160309103506.png
  • 1457487966
  • entry.count.image
  • http%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fc%2Fch3cooh393%2F20160312%2F20160312122305.png
  • 1457754082
  • entry.count.image
  • http%3A%2F%2Fecx.images-amazon.com%2Fimages%2FI%2F61ApsGGdAmL.jpg
  • 1457485200
  • m_js_controller.js
  • abg.js
  • googlelogo_color_112x36dp.png
  • nessie_icon_tiamat_white.png
  • s
  • x_button_blue2.png
  • Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
  • 00000.gif
  • 00001.gif
  • 00001.gif
  • 00000.gif
  • 00000.gif
  • 00001.gif

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Catchball.co, 15% (10 requests) were made to Cdn.b.st-hatena.com and 10% (7 requests) were made to Capture.heartrails.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Products.ch3cooh.jp.

Additional info on catchball.co

Requests

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

11

Javascripts

35

Images

3

CSS

9

AJAX

58

All

Possible request optimization

1

Javascripts

17

Images

3

CSS

9

AJAX

28

Optimized

30

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://products.ch3cooh.jp/ before it reached this domain.

IP address

Catchball.co 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

catchball.co

docstoc.com

sitemeter.com

yourfilehost.com

hotklix.com

34.102.136.180

DNS records

Type Host Target/ip TTL Other
A

catchball.co

34.102.136.180 600
NS

catchball.co

ns36.domaincontrol.com 3600
NS

catchball.co

ns35.domaincontrol.com 3600
SOA

catchball.co

3600 Mname: ns35.domaincontrol.com
Rname: dns.jomax.net
Serial: 2020112800
Refresh: 28800
Retry: 7200
Expire: 604800
Minimum-ttl: 600

Language and encoding

Normal result

Language

N/A  language flag

Detected

JA ja language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Catchball.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Catchball.co 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

Catchball.co 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

Country of origin for 100% of all visits is Japan. It lies approximately 6720 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up Catchball.co page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

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

catchball.co

Share this report in social media

Analyze another website

Analyze