Access granvia-osaka.jp. 【公式】ホテルグランヴィア大阪

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value3,320 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.408

24/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

granvia-osaka.jp

668 ms

import.css

348 ms

WebKitDetect.js

370 ms

jquery-1.8.3.min.js

931 ms

jquery.easing.js

379 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 97% of them (131 requests) were addressed to the original Granvia-osaka.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to C.nakanohito.jp. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Granvia-osaka.jp.

Content Size

5.7 MB

After Optimization

5.1 MB

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

HTML Optimization

-78%

Potential reduce by 31.6 kB

Original 40.5 kB
After minification 35.8 kB
After compression 8.9 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 4.7 kB, which is 12% 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 31.6 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 185.6 kB

Original 5.1 MB
After minification 4.9 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. Granvia Osaka images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 204.3 kB

Original 302.5 kB
After minification 244.9 kB
After compression 98.2 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 204.3 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 175.2 kB

Original 204.7 kB
After minification 152.9 kB
After compression 29.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. Granvia-osaka.jp needs all CSS files to be minified and compressed as it can save up to 175.2 kB or 86% of the original size.

Requests Now

134

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

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

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

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 Granvia-osaka.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 Granvia-osaka.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

granvia-osaka.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

【公式】ホテルグランヴィア大阪 | JR大阪駅直結

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

granvia-osaka.jp

import.css

WebKitDetect.js

jquery-1.8.3.min.js

jquery.easing.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

granvia-osaka.jp

import.css

WebKitDetect.js

jquery-1.8.3.min.js

jquery.easing.js

jquery.flexslider.js

flexslider.css

jquery.colorbox-min.js

script.js

calendar.js

calendar-jp.js

calendar-setup.js

theme.css

common.css

base.css

stay.css

restaurant.css

party.css

wedding.css

index.css

colorbox.css

index.php

index.php

head_bg.gif

logo.jpg

h_lang_01.gif

h_lang_02.gif

h_lang_03.gif

h_lang_04.gif

h_navi_01.gif

h_navi_02.gif

h_navi_03.gif

h_navi_04.gif

h_01.jpg

h_02.jpg

h_03.jpg

h_04.jpg

h_05.jpg

main_05_bg.jpg

main_05.jpg

main_25_bg.jpg

main_25.jpg

main_04_bg.jpg