Tools & Wizards About Us
hatenko.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hatenko.co.jp

京都 居酒屋『祭り屋』木屋町

Page Load Speed

5.9 sec in total

First Response

939 ms

Resources Loaded

4.8 sec

Page Rendered

235 ms

hatenko.co.jp screenshot

About Website

Welcome to hatenko.co.jp homepage info - get ready to check Hatenko best content right away, or after learning these important things about hatenko.co.jp

京都四条木屋町にある居酒屋『祭り屋』では祭り姿やハッピでお出迎えします。ぜひ至福の時をお過ごしください。板前が作る創作料理美味しいお料理がたくさんあります。大人がワイワイと飲みたい時に是非お越し下さい。

Visit hatenko.co.jp

Key Findings

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

Performance Metrics

hatenko.co.jp performance score

0

Network Requests Diagram

hatenko.co.jp

939 ms

global.css

362 ms

containerSkin.css

370 ms

skin.css

371 ms

pageView.css

404 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that all of those requests were addressed to Hatenko.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Hatenko.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 299.3 kB (32%)

Content Size

946.1 kB

After Optimization

646.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 9.3 kB

  • Original 11.9 kB
  • After minification 11.9 kB
  • After compression 2.6 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 9.3 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 185 B

  • Original 589.7 kB
  • After minification 589.5 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. Hatenko images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 222.2 kB

  • Original 272.0 kB
  • After minification 209.1 kB
  • After compression 49.8 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 222.2 kB or 82% of the original size.

CSS Optimization

-93%

Potential reduce by 67.6 kB

  • Original 72.5 kB
  • After minification 57.8 kB
  • After compression 4.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. Hatenko.co.jp needs all CSS files to be minified and compressed as it can save up to 67.6 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (46%)

Requests Now

35

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hatenko.co.jp

hatenko.co.jp

939 ms

global.css

global.css

362 ms

containerSkin.css

containerSkin.css

370 ms

skin.css

skin.css

371 ms

pageView.css

pageView.css

404 ms

blockLayout.css

blockLayout.css

413 ms

boxStyle.css

boxStyle.css

1472 ms

jquery.js

jquery.js

1500 ms

corecms_base.js

corecms_base.js

916 ms

corecms_ajax.js

corecms_ajax.js

1204 ms

corecms_modules.js

corecms_modules.js

1061 ms

corecms_spry.js

corecms_spry.js

1899 ms

log.js

log.js

1098 ms

swfobject.js

swfobject.js

1469 ms

smartRollover.js

smartRollover.js

1279 ms

thickbox.js

thickbox.js

1608 ms

thickbox.css

thickbox.css

1464 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

2014 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

1672 ms

bg.jpg

bg.jpg

644 ms

200 ms

hd.jpg

hd.jpg

540 ms

nav_01.jpg

nav_01.jpg

186 ms

nav_02.jpg

nav_02.jpg

184 ms

nav_03.jpg

nav_03.jpg

206 ms

nav_04.jpg

nav_04.jpg

368 ms

nav_06.jpg

nav_06.jpg

368 ms

main20120904.jpg

main20120904.jpg

2213 ms

title_shinchaku.jpg

title_shinchaku.jpg

619 ms

img_catch.jpg

img_catch.jpg

918 ms

title_tenpo.jpg

title_tenpo.jpg

552 ms

map.gif

map.gif

718 ms

bn_face_none.jpg

bn_face_none.jpg

720 ms

banner_gurnv.jpg

banner_gurnv.jpg

1008 ms

ban_tabe_111111.jpg

ban_tabe_111111.jpg

834 ms

ban_hot_none.jpg

ban_hot_none.jpg

882 ms

index.php

index.php

1194 ms

SEO Factors

hatenko.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hatenko.co.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 Hatenko.co.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.

Social Sharing Optimization

hatenko.co.jp

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