Tools & Wizards About Us
royalhall.co.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

royalhall.co.jp

【公式】ロイヤルホールヨコハマ（神奈川県/横浜の結婚式場）

Page Load Speed

8.7 sec in total

First Response

1.2 sec

Resources Loaded

7.4 sec

Page Rendered

228 ms

royalhall.co.jp screenshot

About Website

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

神奈川県横浜市 日本大通り駅より徒歩3分の結婚式場ロイヤルホールヨコハマ。赤レンガ倉庫や横浜中華街のほど近く、35年以上にわたり多くの新郎新婦が永遠の愛を誓った場所…それが、私たちロイヤルホールヨコハマです。

Visit royalhall.co.jp

Key Findings

We analyzed Royalhall.co.jp page load time and found that the first response time was 1.2 sec and then it took 7.6 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

royalhall.co.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

royalhall.co.jp

1164 ms

import.css

169 ms

allindex.css

332 ms

ga.js

337 ms

jquery1_8_3.js

3808 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 87% of them (13 requests) were addressed to the original Royalhall.co.jp, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Royalhall.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.9 kB (35%)

Content Size

723.6 kB

After Optimization

470.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-56%

Potential reduce by 1.7 kB

  • Original 3.1 kB
  • After minification 3.0 kB
  • After compression 1.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 1.7 kB or 56% of the original size.

Image Optimization

-2%

Potential reduce by 9.5 kB

  • Original 416.3 kB
  • After minification 406.8 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. Royalhall images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 236.7 kB

  • Original 297.8 kB
  • After minification 170.8 kB
  • After compression 61.1 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 236.7 kB or 79% of the original size.

CSS Optimization

-76%

Potential reduce by 5.0 kB

  • Original 6.5 kB
  • After minification 3.7 kB
  • After compression 1.5 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. Royalhall.co.jp needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

royalhall.co.jp

royalhall.co.jp

1164 ms

import.css

import.css

169 ms

allindex.css

allindex.css

332 ms

ga.js

ga.js

337 ms

jquery1_8_3.js

jquery1_8_3.js

3808 ms

jquery.maximage.js

jquery.maximage.js

532 ms

reset.css

reset.css

201 ms

base.css

base.css

321 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

15 ms

index_bg.jpg

index_bg.jpg

2183 ms

index_t.png

index_t.png

179 ms

wedding_door.png

wedding_door.png

331 ms

party_door.png

party_door.png

177 ms

print.css

print.css

170 ms

Accessibility Review

royalhall.co.jp accessibility score

81

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

royalhall.co.jp best practices score

75

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

SEO Factors

royalhall.co.jp SEO score

100

Search Engine Optimization Advices

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

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

royalhall.co.jp

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