Analyze

mlbcafe.jp: MLB café TOKYO – 恵比寿・TOKYO DOMEのMLB公認カフェレストラン・スポーツバー「MLB café TOKYO」

恵比寿・新宿のMLB公認カフェレストラン・スポーツバー「MLB café TOKYO」

Page load speed analysis

  • 57/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    529 ms

  • Resources loaded

    11.6 sec

  • Page rendered

    1 sec

  • Total page load time

    13.2 sec

Welcome to mlbcafe.jp homepage info - get ready to check MLB Cafe best content for Japan right away, or after learning these important things about mlbcafe.jp

We analyzed Mlbcafe.jp page load time and found that the first response time was 529 ms and then it took 12.6 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 31.6 kB
    Images 8.0 MB
    Javascripts 435.1 kB
    CSS 47.8 kB

    In fact, the total size of Mlbcafe.jp main page is 8.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. 55% of websites need less resources to load. Images take 8.0 MB which makes up the majority of the site volume.

    • Original 31.6 kB
    • After minification 27.8 kB
    • After compression 8.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. This page needs HTML code to be minified as it can gain 3.8 kB, which is 12% 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 23.5 kB or 74% of the original size.

    • Original 8.0 MB
    • After optimization 7.8 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. MLB Cafe images are well optimized though.

    • Original 435.1 kB
    • After minification 432.5 kB
    • After compression 149.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 285.7 kB or 66% of the original size.

    • Original 47.8 kB
    • After minification 33.9 kB
    • After compression 7.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. Mlbcafe.jp needs all CSS files to be minified and compressed as it can save up to 40.0 kB or 84% of the original size.

Network requests diagram

  • mlbcafe.jp
  • styles.css
  • colorbox.css
  • colorbox-custom.css
  • rollover.min.js
  • jquery.js
  • jsapi
  • gmap.js
  • wideslider.js
  • pulldown.js
  • jquery.colorbox-min.js
  • base.css
  • fonts.css
  • js
  • body_bg.jpg
  • main_img-01.jpg
  • main_img-02.jpg
  • main_img-03.jpg
  • main_img-04.jpg
  • main_img-05.jpg
  • main_img_catch.png
  • header_logo.png
  • global01b_off.png
  • global02b_off.png
  • global03b_off.png
  • global04b_off.png
  • index_title01.png
  • top_bnr04_off.png
  • top_bnr05_off.png
  • index_bnr01_off.png
  • top_mlb_off.png
  • top_banner_off.png
  • top01_off.png
  • top03_off.png
  • top04_off.png
  • top_lady_off.png
  • top_read_title.png
  • top_read_img-01.jpg
  • top02a_off.png
  • top02c_off.png
  • navi_lady_off.png
  • navi_feature_off.png
  • navi_menu01-01_off.jpg
  • navi_menu01-07_off.jpg
  • navi_menu02-01_off.jpg
  • navi_menu02-02_off.jpg
  • navi_menu02-03_off.jpg
  • navi_sns_01.png
  • navi_sns_02.png
  • navi_sns_t.png
  • all.js
  • ga.js
  • mlbcafe_jp
  • __utm.gif
  • xd_arbiter.php
  • xd_arbiter.php
  • navi_sns_i.png
  • sessionError.html
  • navi_sns_03.png
  • navi_sns_f.png
  • navi_sns_l.png
  • navi_sns_04.png
  • navi_blog_off.png
  • navi_angepatio_off.png
  • navi_duodomo_off.png
  • navi_act_off.png
  • navi_playball_off.jpg
  • footer_ball.png
  • pt.png
  • header_bg.jpg
  • top_contents_bg.jpg
  • on_bg.png
  • shadow02.png
  • top05.png
  • navi_sns_bk.jpg
  • footer_bg.png
  • main_img_bg.png
  • overlay.png
  • common.js
  • util.js
  • stats.js
  • AuthenticationService.Authenticate
  • global01b_on.png
  • global02b_on.png
  • global03b_on.png
  • global04b_on.png
  • top_bnr04_on.png
  • top_bnr05_on.png
  • index_bnr01_on.png
  • top_mlb_on.png
  • top_banner_on.png
  • top01_on.png
  • top03_on.png
  • top04_on.png
  • top_lady_on.png
  • top02a_on.png
  • top02c_on.png
  • navi_lady_on.png
  • navi_feature_on.png
  • navi_menu01-01_on.jpg
  • navi_menu01-07_on.jpg
  • navi_menu02-01_on.jpg
  • navi_menu02-02_on.jpg
  • navi_menu02-03_on.jpg
  • navi_blog_on.png
  • navi_angepatio_on.png
  • navi_duodomo_on.png
  • navi_act_on.png
  • navi_playball_on.jpg

Our browser made a total of 110 requests to load all elements on the main page. We found that 87% of them (96 requests) were addressed to the original Mlbcafe.jp, 5% (5 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Mlbcafe.jp.

Additional info on mlbcafe.jp

Requests

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

14

Javascripts

86

Images

5

CSS

3

AJAX

108

All

Possible request optimization

1

Javascripts

77

Images

1

CSS

3

AJAX

26

Optimized

82

All

Normal result

IP address

Mlbcafe.jp 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

mlbcafe.jp

9m9.biz

gamesiyo.com

yukata-kitsuke.com

mushinavi.com

157.7.44.174

DNS records

Type Host Target/ip TTL Other
A

mlbcafe.jp

157.7.44.174 1800
NS

mlbcafe.jp

dns1.heteml.jp 86395
NS

mlbcafe.jp

dns0.heteml.jp 86395
SOA

mlbcafe.jp

2560 Mname: dns0.heteml.jp
Rname: hostmaster.mlbcafe.jp
Serial: 1539762013
Refresh: 16384
Retry: 2048
Expire: 1048576
Minimum-ttl: 2560
MX

mlbcafe.jp

mail23.heteml.jp 3600 Pri: 10

Language and encoding

Good result

Language

JA ja 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 Mlbcafe.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Mlbcafe.jp 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

Mlbcafe.jp 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’s good for Mlbcafe.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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

mlbcafe.jp

Share this report in social media

Analyze another website

Analyze