Tools & Wizards About Us
aoyama-hachi.net screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

aoyama-hachi.net

青山蜂 Aoyama HACHI

Page Load Speed

6.2 sec in total

First Response

1.4 sec

Resources Loaded

4.5 sec

Page Rendered

276 ms

aoyama-hachi.net screenshot

About Website

Welcome to aoyama-hachi.net homepage info - get ready to check Aoyama HACHI best content for Japan right away, or after learning these important things about aoyama-hachi.net

東京は青山の外れにあるCLUB。個性的な4階建てのビルをフルに利用しているので、各フロアごとに違った雰囲気を楽しむことが出来ます。

Visit aoyama-hachi.net

Key Findings

We analyzed Aoyama-hachi.net page load time and found that the first response time was 1.4 sec and then it took 4.8 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

aoyama-hachi.net performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value30.5 s

0/100

10%

Network Requests Diagram

aoyama-hachi.net

1416 ms

default.css

435 ms

960.css

440 ms

css2

35 ms

style_wp.css

658 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 65% of them (76 requests) were addressed to the original Aoyama-hachi.net, 15% (18 requests) were made to Platform.twitter.com and 6% (7 requests) were made to Widget.sndcdn.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Aoyama-hachi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.3 kB (12%)

Content Size

976.8 kB

After Optimization

862.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aoyama-hachi.net main page is 976.8 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. 70% of websites need less resources to load. Images take 813.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 30.1 kB

  • Original 37.1 kB
  • After minification 35.6 kB
  • After compression 7.0 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 30.1 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 38.4 kB

  • Original 813.8 kB
  • After minification 775.4 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. Aoyama HACHI images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 18.2 kB

  • Original 92.6 kB
  • After minification 84.8 kB
  • After compression 74.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 18.2 kB or 20% of the original size.

CSS Optimization

-83%

Potential reduce by 27.6 kB

  • Original 33.4 kB
  • After minification 25.5 kB
  • After compression 5.7 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. Aoyama-hachi.net needs all CSS files to be minified and compressed as it can save up to 27.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (39%)

Requests Now

111

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aoyama HACHI. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

aoyama-hachi.net

aoyama-hachi.net

1416 ms

default.css

default.css

435 ms

960.css

960.css

440 ms

css2

css2

35 ms

style_wp.css

style_wp.css

658 ms

smoothScroll.js

smoothScroll.js

441 ms

jsapi

jsapi

14 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

449 ms

jquery.jfeed.js

jquery.jfeed.js

478 ms

common_wp.js

common_wp.js

650 ms

ga.js

ga.js

674 ms

index_wp.js

index_wp.js

676 ms

jquery.autolink.js

jquery.autolink.js

675 ms

loader.js

loader.js

15 ms

widgets.js

widgets.js

81 ms

jquery.min.js

jquery.min.js

61 ms

ga.js

ga.js

48 ms

banner_tw.gif

banner_tw.gif

895 ms

bg_paper_s.gif

bg_paper_s.gif

440 ms

bg_header_2.gif

bg_header_2.gif

909 ms

header_menu_logo.png

header_menu_logo.png

222 ms

header_menu_bordersss.gif

header_menu_bordersss.gif

221 ms

header_menu_home.png

header_menu_home.png

221 ms

header_menu_schedule.png

header_menu_schedule.png

217 ms

header_menu_shop.png

header_menu_shop.png

434 ms

header_menu_info.png

header_menu_info.png

440 ms

header_menu_access.png

header_menu_access.png

440 ms

header_menu_other.gif

header_menu_other.gif

440 ms

header_menu_other_clubberia.gif

header_menu_other_clubberia.gif

651 ms

header_menu_other_twitter.gif

header_menu_other_twitter.gif

670 ms

header_menu_other_facebook.gif

header_menu_other_facebook.gif

671 ms

bg_illust__.gif

bg_illust__.gif

1752 ms

billboard_party_frame.png

billboard_party_frame.png

671 ms

bg_imgcover.gif

bg_imgcover.gif

1082 ms

S__38609006-300x300.jpg

S__38609006-300x300.jpg

889 ms

asahachi0615-300x300.jpg

asahachi0615-300x300.jpg

890 ms

S__38609008-300x300.jpg

S__38609008-300x300.jpg

889 ms

S__38658075-300x300.jpg

S__38658075-300x300.jpg

1098 ms

rtb618-300x300.jpg

rtb618-300x300.jpg

1316 ms

S__38494298-300x300.jpg

S__38494298-300x300.jpg

1100 ms

S__38609023-300x424.jpg

S__38609023-300x424.jpg

1124 ms

asahachi0622_3-300x300.jpg

asahachi0622_3-300x300.jpg

1298 ms

S__38658077-300x300.jpg

S__38658077-300x300.jpg

1317 ms

S__38633509-300x335.jpg

S__38633509-300x335.jpg

1321 ms

asahachi0629-300x300.jpg

asahachi0629-300x300.jpg

1350 ms

asahachi630-300x300.jpg

asahachi630-300x300.jpg

1514 ms

salon0703-300x375.jpg

salon0703-300x375.jpg

1534 ms

rtb07-300x300.jpg

rtb07-300x300.jpg

1536 ms

yo.gif

yo.gif

1540 ms

load.gif

load.gif

1573 ms

banner_fb.gif

banner_fb.gif

901 ms

banner_ig.gif

banner_ig.gif

901 ms

map_s.gif

map_s.gif

902 ms

hr_1.gif

hr_1.gif

901 ms

adbaloon_s.gif

adbaloon_s.gif

1699 ms

adbaloon_s0.gif

adbaloon_s0.gif

1722 ms

banner_free65.gif

banner_free65.gif

1723 ms

banner_marumaru_empty2.gif

banner_marumaru_empty2.gif

1728 ms

_gP_1RrxsjcxVyin9l9n_j2RSdRxqDs.woff

_gP_1RrxsjcxVyin9l9n_j2RSdRxqDs.woff

114 ms

164 ms

__utm.gif

__utm.gif

36 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

73 ms

settings

settings

93 ms

grid_3_frame_1.gif

grid_3_frame_1.gif

1586 ms

grid_3_frame_2.gif

grid_3_frame_2.gif

1732 ms

h4_3.gif

h4_3.gif

1753 ms

S__38609006-230x230.jpg

S__38609006-230x230.jpg

1757 ms

player-widget.mixcloud.com

player-widget.mixcloud.com

313 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

19 ms

391 ms

aoyama_hachi

aoyama_hachi

147 ms

asahachi0615-230x230.jpg

asahachi0615-230x230.jpg

1547 ms

S__38609008-230x230.jpg

S__38609008-230x230.jpg

1548 ms

S__38658075-230x230.jpg

S__38658075-230x230.jpg

1590 ms

S__38609023-162x230.jpg

S__38609023-162x230.jpg

1729 ms

asahachi0622_3-230x230.jpg

asahachi0622_3-230x230.jpg

1754 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

20 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

42 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

61 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

73 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

89 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

93 ms

_buildManifest.js

_buildManifest.js

103 ms

_ssgManifest.js

_ssgManifest.js

101 ms

123 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

20 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

22 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

20 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

43 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

51 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

55 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

24 ms

S__38658077-230x230.jpg

S__38658077-230x230.jpg

1532 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

189 ms

mixcloud-logo.png

mixcloud-logo.png

217 ms

asahachi0629-230x230.jpg

asahachi0629-230x230.jpg

1529 ms

asahachi630-230x230.jpg

asahachi630-230x230.jpg

1535 ms

rtb618-230x230.jpg

rtb618-230x230.jpg

1578 ms

widget-4-a7e4acae5081.js

widget-4-a7e4acae5081.js

24 ms

widget-8-9d1aada5faa4.js

widget-8-9d1aada5faa4.js

25 ms

widget-9-a120fe034041.js

widget-9-a120fe034041.js

38 ms

logo-200x120-3190df52.png

logo-200x120-3190df52.png

30 ms

widget-0-f1735e35d6cc.js

widget-0-f1735e35d6cc.js

14 ms

widget-2-f2ce33575c4f.js

widget-2-f2ce33575c4f.js

14 ms

widget-1-500155b72734.js

widget-1-500155b72734.js

14 ms

103 ms

S__38494298-230x230.jpg

S__38494298-230x230.jpg

1496 ms

S__38633509-205x230.jpg

S__38633509-205x230.jpg

1522 ms

salon0703-184x230.jpg

salon0703-184x230.jpg

1526 ms

rtb07-230x230.jpg

rtb07-230x230.jpg

1511 ms

hr_3.gif

hr_3.gif

1345 ms

h4_2.gif

h4_2.gif

1379 ms

hr_2.gif

hr_2.gif

1499 ms

h4_3s.gif

h4_3s.gif

1507 ms

bg_footer.gif

bg_footer.gif

1337 ms

footer_icon.png

footer_icon.png

1321 ms

footer_icon.gif

footer_icon.gif

1329 ms

Accessibility Review

aoyama-hachi.net accessibility score

74

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

aoyama-hachi.net best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

aoyama-hachi.net SEO score

80

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aoyama-hachi.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Aoyama-hachi.net 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

aoyama-hachi.net

Open Graph data is detected on the main page of Aoyama HACHI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: