Tools & Wizards About Us
hotelpalace.jp screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

hotelpalace.jp

埼玉県川口市のビジネスホテル｜蕨パレスホテル｜東京至近｜公式

Page Load Speed

6.7 sec in total

First Response

837 ms

Resources Loaded

5.6 sec

Page Rendered

317 ms

hotelpalace.jp screenshot

About Website

Click here to check amazing Hotelpalace content. Otherwise, check out these important facts you probably never knew about hotelpalace.jp

埼玉県 蕨・川口・浦和・大宮周辺のビジネスホテル『蕨パレスホテル』蕨駅東口から徒歩約2分。都内にも至近（赤羽10分､池袋22分､上野26分､新宿27分､東京33分）ビジネス、イベント、スポーツ観戦に最適です。

Visit hotelpalace.jp

Key Findings

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

Performance Metrics

hotelpalace.jp performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

hotelpalace.jp

837 ms

import.css

324 ms

top.css

502 ms

heightLine.js

529 ms

swf_top.js

370 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Hotelpalace.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Hotelpalace.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.8 kB (11%)

Content Size

358.6 kB

After Optimization

319.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 15.3 kB

  • Original 20.5 kB
  • After minification 18.1 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.4 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 15.3 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 4.7 kB

  • Original 297.2 kB
  • After minification 292.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. Hotelpalace images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 5.4 kB

  • Original 24.8 kB
  • After minification 23.2 kB
  • After compression 19.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 5.4 kB or 22% of the original size.

CSS Optimization

-84%

Potential reduce by 13.4 kB

  • Original 16.0 kB
  • After minification 8.2 kB
  • After compression 2.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. Hotelpalace.jp needs all CSS files to be minified and compressed as it can save up to 13.4 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotelpalace.jp

hotelpalace.jp

837 ms

import.css

import.css

324 ms

top.css

top.css

502 ms

heightLine.js

heightLine.js

529 ms

swf_top.js

swf_top.js

370 ms

swf_map_top.js

swf_map_top.js

334 ms

search.js

search.js

335 ms

analytics1.js

analytics1.js

342 ms

analytics2.js

analytics2.js

441 ms

default.css

default.css

516 ms

common.css

common.css

736 ms

print.css

print.css

676 ms

bg_header.gif

bg_header.gif

181 ms

logo.gif

logo.gif

490 ms

img_walk.gif

img_walk.gif

520 ms

img_contact_tel.gif

img_contact_tel.gif

526 ms

img_contact_mail.gif

img_contact_mail.gif

358 ms

plan_title.jpg

plan_title.jpg

550 ms

img_1296525741_4.jpeg

img_1296525741_4.jpeg

816 ms

btn_plan_list.gif

btn_plan_list.gif

720 ms

plan_title_bussiness.jpg

plan_title_bussiness.jpg

970 ms

img_1298874937_4.JPG

img_1298874937_4.JPG

1020 ms

img_1298874037_4.jpg

img_1298874037_4.jpg

1068 ms

img_1296525865_4.jpg

img_1296525865_4.jpg

1220 ms

bn_soine.jpg

bn_soine.jpg

1636 ms

bn_long_stay.jpg

bn_long_stay.jpg

1453 ms

tl_service_l.gif

tl_service_l.gif

1306 ms

img_service1.jpg

img_service1.jpg

1688 ms

img_service2.jpg

img_service2.jpg

1597 ms

img_service3.jpg

img_service3.jpg

1984 ms

img_service4.jpg

img_service4.jpg

1851 ms

bn_point01.jpg

bn_point01.jpg

2126 ms

bn_point02.jpg

bn_point02.jpg

2126 ms

bn_point03.jpg

bn_point03.jpg

2360 ms

bn_point04.jpg

bn_point04.jpg

2410 ms

tl_news.gif

tl_news.gif

2174 ms

tl_friendship_hotels.gif

tl_friendship_hotels.gif

2486 ms

bn_bestrate.jpg

bn_bestrate.jpg

3004 ms

tl_search.gif

tl_search.gif

2653 ms

btn_cancel.gif

btn_cancel.gif

2558 ms

img_reserve_tel.gif

img_reserve_tel.gif

2857 ms

img_access.gif

img_access.gif

3198 ms

img_long_stay.jpg

img_long_stay.jpg

3016 ms

btn_pagetop.gif

btn_pagetop.gif

2894 ms

bg_global_menu.gif

bg_global_menu.gif

3018 ms

btn_global_menu.gif

btn_global_menu.gif

3720 ms

bg_cont_bottom.gif

bg_cont_bottom.gif

3213 ms

img_border01.gif

img_border01.gif

3316 ms

ga.js

ga.js

4 ms

__utm.gif

__utm.gif

12 ms

img_lank1.gif

img_lank1.gif

3175 ms

img_lank2.gif

img_lank2.gif

3033 ms

img_lank3.gif

img_lank3.gif

3085 ms

bk_yuukansarvice.gif

bk_yuukansarvice.gif

3105 ms

img_greeting.jpg

img_greeting.jpg

3465 ms

img_border02.jpg

img_border02.jpg

3159 ms

bg_search.gif

bg_search.gif

3044 ms

btn_search.gif

btn_search.gif

3108 ms

bg_footer_top.gif

bg_footer_top.gif

2989 ms

Accessibility Review

hotelpalace.jp accessibility score

90

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

High

robots.txt is not valid

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

hotelpalace.jp

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