Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

keioplaza.co.jp

東京のホテルなら京王プラザホテル【公式】

Page Load Speed

10.1 sec in total

First Response

1.4 sec

Resources Loaded

8 sec

Page Rendered

653 ms

keioplaza.co.jp screenshot

About Website

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

都庁前駅からB1出口よりすぐ。新宿の喧騒から離れ、落ち着いた街並みが広がる「西新宿」の超高層ホテル。ご宿泊、レストラン、ウエディング、ご宴会・会議、出張など、様々なご利用シーンに最高のおもてなしでお応えます。

Visit keioplaza.co.jp

Key Findings

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

keioplaza.co.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,360 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.153

75/100

15%

TTI (Time to Interactive)

Value41.6 s

0/100

10%

Network Requests Diagram

keioplaza.co.jp

1359 ms

import.css

389 ms

font_medium.css

393 ms

prototype.js

1772 ms

default.js

585 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 97% of them (116 requests) were addressed to the original Keioplaza.co.jp, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Keioplaza.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.7 kB (22%)

Content Size

1.1 MB

After Optimization

847.3 kB

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

HTML Optimization

-78%

Potential reduce by 30.4 kB

  • Original 39.1 kB
  • After minification 30.8 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 8.3 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.4 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 734 B

  • Original 772.1 kB
  • After minification 771.3 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. Keioplaza images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 136.9 kB

  • Original 194.5 kB
  • After minification 158.3 kB
  • After compression 57.6 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 136.9 kB or 70% of the original size.

CSS Optimization

-89%

Potential reduce by 74.7 kB

  • Original 84.3 kB
  • After minification 69.9 kB
  • After compression 9.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. Keioplaza.co.jp needs all CSS files to be minified and compressed as it can save up to 74.7 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (53%)

Requests Now

118

After Optimization

55

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

Accessibility Review

keioplaza.co.jp accessibility score

70

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

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

<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

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

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

keioplaza.co.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

High

Page has valid source maps

SEO Factors

keioplaza.co.jp SEO score

85

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Keioplaza.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 Keioplaza.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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