Tools & Wizards About Us
vizcaya.jp screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

vizcaya.jp

【神戸迎賓館】神戸・須磨離宮の結婚式・ウエディング・披露宴

Page Load Speed

5.9 sec in total

First Response

552 ms

Resources Loaded

4.9 sec

Page Rendered

380 ms

vizcaya.jp screenshot

About Website

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

神戸迎賓館は、1919年、由緒ある須磨離宮の地に誕生した迎賓館。全てが文化財という緑豊かな1万平米もの敷地で、世界中から訪れるVIPを招きもてなすために贅を尽くした空間を、今もなおウエディング、各種宴会・パーティ、レストランとしてご利用いただけます。

Visit vizcaya.jp

Key Findings

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

Performance Metrics

vizcaya.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,800 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

vizcaya.jp

552 ms

www.vizcaya.jp

701 ms

base.css

339 ms

smartphone.js

335 ms

smartRollover.js

340 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 41% of them (16 requests) were addressed to the original Vizcaya.jp, 5% (2 requests) were made to Facebook.com and 5% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Vizcaya.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.4 kB (8%)

Content Size

529.5 kB

After Optimization

486.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vizcaya.jp main page is 529.5 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 377.4 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 5.2 kB

  • Original 8.3 kB
  • After minification 7.5 kB
  • After compression 3.1 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 5.2 kB or 63% of the original size.

Image Optimization

-1%

Potential reduce by 1.9 kB

  • Original 377.4 kB
  • After minification 375.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. Vizcaya images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 35.1 kB

  • Original 142.0 kB
  • After minification 139.5 kB
  • After compression 106.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 35.1 kB or 25% of the original size.

CSS Optimization

-66%

Potential reduce by 1.1 kB

  • Original 1.7 kB
  • After minification 1.4 kB
  • After compression 579 B

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. Vizcaya.jp needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (56%)

Requests Now

34

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vizcaya.jp

vizcaya.jp

552 ms

www.vizcaya.jp

www.vizcaya.jp

701 ms

base.css

base.css

339 ms

smartphone.js

smartphone.js

335 ms

smartRollover.js

smartRollover.js

340 ms

jquery.min.js

jquery.min.js

76 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

356 ms

01.jpg

01.jpg

1787 ms

02.jpg

02.jpg

2115 ms

03.jpg

03.jpg

1901 ms

04.jpg

04.jpg

1740 ms

05.jpg

05.jpg

1659 ms

bg.png

bg.png

364 ms

navi_01_off.png

navi_01_off.png

547 ms

navi_02_off.png

navi_02_off.png

729 ms

navi_03_off.png

navi_03_off.png

909 ms

navi_access.png

navi_access.png

1091 ms

tag.js

tag.js

191 ms

bi.js

bi.js

582 ms

like.php

like.php

96 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

34 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

33 ms

tag

tag

20 ms

362 ms

ga.js

ga.js

61 ms

fbevents.js

fbevents.js

23 ms

ya.js

ya.js

388 ms

conversion_async.js

conversion_async.js

123 ms

blade_track_jp.js

blade_track_jp.js

398 ms

18 ms

__utm.gif

__utm.gif

37 ms

41 ms

40 ms

79 ms

94 ms

pb.js

pb.js

968 ms

349 ms

cookie_enabled_get.html

cookie_enabled_get.html

320 ms

bl_track.cgi

bl_track.cgi

388 ms

Accessibility Review

vizcaya.jp accessibility score

72

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

vizcaya.jp SEO score

92

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vizcaya.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vizcaya.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

vizcaya.jp

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