Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

hyakkarou.jp

【公式】百花籠 | 名古屋市東区の結婚式場

Page Load Speed

9.3 sec in total

First Response

753 ms

Resources Loaded

7.9 sec

Page Rendered

616 ms

hyakkarou.jp screenshot

About Website

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

誰とも、どことも違うただひとつの結婚式を。百花籠は名古屋市にある結婚式場です。日本とヨーロッパそれぞれの伝統と新旧の美が綯交ぜになった世界観はクラシカルでいて斬新。和洋渾然の空間がここにはあります。

Visit hyakkarou.jp

Key Findings

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

Performance Metrics

hyakkarou.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value42.1 s

0/100

25%

SI (Speed Index)

Value25.5 s

0/100

10%

TBT (Total Blocking Time)

Value9,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value42.4 s

0/100

10%

Network Requests Diagram

hyakkarou.jp

753 ms

common.css

1021 ms

jquery.min.js

32 ms

jquery_easing_1_3.js

332 ms

rollover.js

364 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 72% of them (80 requests) were addressed to the original Hyakkarou.jp, 7% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Hyakkarou.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 302.0 kB (11%)

Content Size

2.7 MB

After Optimization

2.4 MB

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

HTML Optimization

-81%

Potential reduce by 31.4 kB

  • Original 38.7 kB
  • After minification 37.1 kB
  • After compression 7.4 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 31.4 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 82.6 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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

JavaScript Optimization

-62%

Potential reduce by 81.6 kB

  • Original 131.5 kB
  • After minification 116.7 kB
  • After compression 49.9 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 81.6 kB or 62% of the original size.

CSS Optimization

-89%

Potential reduce by 106.4 kB

  • Original 119.0 kB
  • After minification 96.2 kB
  • After compression 12.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. Hyakkarou.jp needs all CSS files to be minified and compressed as it can save up to 106.4 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (35%)

Requests Now

107

After Optimization

70

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

Accessibility Review

hyakkarou.jp accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hyakkarou.jp SEO score

91

Search Engine Optimization Advices

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

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