Tools & Wizards About Us
hakataza.co.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

hakataza.co.jp

福岡の演劇専用劇場 博多座

Page Load Speed

39.1 sec in total

First Response

10.1 sec

Resources Loaded

28.6 sec

Page Rendered

432 ms

hakataza.co.jp screenshot

About Website

Click here to check amazing Hakataza content for Japan. Otherwise, check out these important facts you probably never knew about hakataza.co.jp

福岡の演劇専用劇場 博多座の公式ウェブサイトです。歌舞伎・演劇の公演情報、観劇チケットのお買い求め情報を紹介しています。

Visit hakataza.co.jp

Key Findings

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

Performance Metrics

hakataza.co.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value53.6 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.181

67/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

hakataza.co.jp

10103 ms

www.hakataza.co.jp

2679 ms

import.css

342 ms

jquery-1.10.1.min.js

2299 ms

add_event.js

526 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 67% of them (56 requests) were addressed to the original Hakataza.co.jp, 5% (4 requests) were made to Tag.ladsp.com and 2% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (12.5 sec) belongs to the original domain Hakataza.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 215.5 kB (23%)

Content Size

926.4 kB

After Optimization

710.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 20.7 kB

  • Original 27.4 kB
  • After minification 25.2 kB
  • After compression 6.7 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 20.7 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 3.6 kB

  • Original 601.8 kB
  • After minification 598.2 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. Hakataza images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 159.7 kB

  • Original 259.1 kB
  • After minification 237.4 kB
  • After compression 99.4 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 159.7 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 31.4 kB

  • Original 38.0 kB
  • After minification 29.0 kB
  • After compression 6.6 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. Hakataza.co.jp needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (55%)

Requests Now

76

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hakataza.co.jp

hakataza.co.jp

10103 ms

www.hakataza.co.jp

www.hakataza.co.jp

2679 ms

import.css

import.css

342 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

2299 ms

add_event.js

add_event.js

526 ms

jquery.hcaptions.js

jquery.hcaptions.js

356 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

561 ms

jquery.galleryview-1.2.js

jquery.galleryview-1.2.js

975 ms

jquery.timers-1.1.2.js

jquery.timers-1.1.2.js

671 ms

jquery.bxslider.js

jquery.bxslider.js

1434 ms

jQueryAutoHeight.js

jQueryAutoHeight.js

850 ms

pixel.js

pixel.js

451 ms

conversion.js

conversion.js

18 ms

reset.css

reset.css

574 ms

font.css

font.css

694 ms

base.css

base.css

1218 ms

skin.css

skin.css

1294 ms

h1_01.gif

h1_01.gif

190 ms

btn_sns_01.gif

btn_sns_01.gif

325 ms

btn_sns_02.gif

btn_sns_02.gif

343 ms

btn_sns_03.gif

btn_sns_03.gif

342 ms

icon_arrow01.jpg

icon_arrow01.jpg

344 ms

txt_tel01.gif

txt_tel01.gif

343 ms

nav_img01_off.png

nav_img01_off.png

536 ms

nav_img02_off.png

nav_img02_off.png

646 ms

nav_img03_off.png

nav_img03_off.png

663 ms

nav_img04_off.png

nav_img04_off.png

664 ms

nav_img05_off.png

nav_img05_off.png

674 ms

145942740956fd18519e2d9_chirashi.jpg

145942740956fd18519e2d9_chirashi.jpg

7997 ms

145942326956fd082542a10_chirashi.jpg

145942326956fd082542a10_chirashi.jpg

7425 ms

145942599156fd12c75c4a5_chirashi.jpg

145942599156fd12c75c4a5_chirashi.jpg

5597 ms

145942612956fd13513ec20_chirashi.jpg

145942612956fd13513ec20_chirashi.jpg

7381 ms

145942691856fd1666469ae_chirashi.gif

145942691856fd1666469ae_chirashi.gif

12495 ms

145942702156fd16cde5f7a_chirashi.jpg

145942702156fd16cde5f7a_chirashi.jpg

8430 ms

145942711056fd17263b94a_chirashi.jpg

145942711056fd17263b94a_chirashi.jpg

12252 ms

145942715556fd175318036_chirashi.jpg

145942715556fd175318036_chirashi.jpg

11835 ms

145942737056fd182ab4150_chirashi.jpg

145942737056fd182ab4150_chirashi.jpg

12097 ms

h2_top01.gif

h2_top01.gif

8371 ms

btn_news01_off.gif

btn_news01_off.gif

8712 ms

bnr_top02_00_off.gif

bnr_top02_00_off.gif

8987 ms

bnr_top01_00_off.gif

bnr_top01_00_off.gif

9203 ms

bnr_top03_00_off.gif

bnr_top03_00_off.gif

9317 ms

bnr_top09_00_off.gif

bnr_top09_00_off.gif

9546 ms

bnr_top08_00.gif

bnr_top08_00.gif

9657 ms

bnr_top04_00_off.gif

bnr_top04_00_off.gif

9870 ms

bnr_top05_00_off.gif

bnr_top05_00_off.gif

10020 ms

bnr_top07_00_off.gif

bnr_top07_00_off.gif

10224 ms

btn_totop01_off.gif

btn_totop01_off.gif

10355 ms

img_logo01.gif

img_logo01.gif

10574 ms

f_tel_01.gif

f_tel_01.gif

10734 ms

f_tel_02.gif

f_tel_02.gif

10903 ms

f_tel_03.gif

f_tel_03.gif

11099 ms

f_tel_04.gif

f_tel_04.gif

11208 ms

bg_top01.gif

bg_top01.gif

11263 ms

icon_t_blank.gif

icon_t_blank.gif

11258 ms

pixel

pixel

210 ms

pixel

pixel

53 ms

Pug

Pug

52 ms

sync.ad-stir.com

sync.ad-stir.com

406 ms

sync

sync

611 ms

is

is

781 ms

75 ms

analytics.js

analytics.js

43 ms

sync

sync

38 ms

tag.js

tag.js

40 ms

blade_track_jp.js

blade_track_jp.js

383 ms

pixel

pixel

35 ms

bx_loader.gif

bx_loader.gif

11026 ms

bg_mv02.png

bg_mv02.png

11157 ms

bg_mv01.png

bg_mv01.png

11352 ms

collect

collect

19 ms

tag

tag

18 ms

sd

sd

26 ms

36 ms

google

google

397 ms

mapuser

mapuser

150 ms

adfunnel

adfunnel

200 ms

cookie_enabled_get.html

cookie_enabled_get.html

357 ms

xrost

xrost

197 ms

bl_track.cgi

bl_track.cgi

343 ms

ya.js

ya.js

366 ms

pb.js

pb.js

898 ms

368 ms

Accessibility Review

hakataza.co.jp accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

hakataza.co.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hakataza.co.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

hakataza.co.jp

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