Access palace-omiya.co.jp. 【公式】埼玉大宮のホテルなら大宮駅徒歩3分パレスホテル大宮

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value1.989

0/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

www.palace-omiya.co.jp

1539 ms

style.css

1183 ms

require.js

339 ms

jquery.carouFredSel-6.0.4-packed.js

900 ms

simpletabs_1.3.js

574 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 96% of them (128 requests) were addressed to the original Palace-omiya.co.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Palace-omiya.co.jp.

Content Size

2.8 MB

After Optimization

2.4 MB

In fact, the total size of Palace-omiya.co.jp main page is 2.8 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. 30% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 40.6 kB

Original 50.8 kB
After minification 45.7 kB
After compression 10.2 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 40.6 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 56.3 kB

Original 2.3 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. Palace Omiya images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 203.7 kB

Original 293.2 kB
After minification 233.6 kB
After compression 89.5 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 203.7 kB or 69% of the original size.

CSS Optimization

-87%

Potential reduce by 99.7 kB

Original 114.4 kB
After minification 92.0 kB
After compression 14.7 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. Palace-omiya.co.jp needs all CSS files to be minified and compressed as it can save up to 99.7 kB or 87% of the original size.

Requests Now

132

After Optimization

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

Accessibility Issues

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 usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Displays images with incorrect aspect ratio

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

N/A
Encoding

UTF-8

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

palace-omiya.co.jp

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this:

Report Summary

Performance

Accessibility

Best Practices

SEO

【公式】埼玉大宮のホテルなら大宮駅徒歩3分パレスホテル大宮

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

www.palace-omiya.co.jp

style.css

require.js

jquery.carouFredSel-6.0.4-packed.js

simpletabs_1.3.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

www.palace-omiya.co.jp

style.css

require.js

jquery.carouFredSel-6.0.4-packed.js

simpletabs_1.3.js

jkl-calendar.js

directin-search.js

jkl-calendar2.js

directin-search2.js

jquery-1.8.3.min.js

rollover.js

jquery.leanModal.min.js

smoothscroll.js

heightLine.js

jquery.orbit-1.2.3.js

jquery.bxslider.js

jquery.colorbox.js

common.js

analytics.js

bg_body.jpg

bg_header.gif

hdr_btn_faq.png

hdr_btn_en.png

hdr_btn_fb.png

head_reserve_off.gif

hdr_logo.png

nav_01_off.png

nav_02_off.png

nav_03_off.png

nav_04_off.png

nav_05_off.png

nav_06_off.png

nav_07_off.png

nav_08_off.png

bg_main.jpg

tochigi_fair.jpg

main_01.jpg

main_02.jpg

main_03.jpg

main_04.jpg

main_05.jpg

img_topcontents_01.png

btn_detail_01_off.png