Tools & Wizards About Us
yth.jp screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

yth.jp

≪公式ＨＰ≫【ベストレート宣言】八重洲ターミナルホテル Yaesu Terminal Hotel website

Page Load Speed

5.6 sec in total

First Response

518 ms

Resources Loaded

3.7 sec

Page Rendered

1.4 sec

yth.jp screenshot

About Website

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

八重洲ターミナルホテルは、JR東京駅八重洲北口より徒歩3分。スタイリッシュな都市型ホテル。(公式ＨＰ)

Visit yth.jp

Key Findings

We analyzed Yth.jp page load time and found that the first response time was 518 ms and then it took 5.1 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

yth.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.892

3/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

yth.jp

518 ms

yth.jp

1093 ms

gtm.js

78 ms

abichat.js

1230 ms

common.css

310 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 78% of them (45 requests) were addressed to the original Yth.jp, 7% (4 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Yth.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 54.1 kB (37%)

Content Size

145.8 kB

After Optimization

91.7 kB

  • HTML
  • JavaScript

In fact, the total size of Yth.jp main page is 145.8 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. 45% of websites need less resources to load. Javascripts take 108.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 28.3 kB

  • Original 37.8 kB
  • After minification 35.0 kB
  • After compression 9.5 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 28.3 kB or 75% of the original size.

JavaScript Optimization

-24%

Potential reduce by 25.8 kB

  • Original 108.0 kB
  • After minification 108.0 kB
  • After compression 82.3 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 25.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (25%)

Requests Now

53

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yth. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yth.jp

yth.jp

518 ms

yth.jp

yth.jp

1093 ms

gtm.js

gtm.js

78 ms

abichat.js

abichat.js

1230 ms

common.css

common.css

310 ms

css2

css2

93 ms

homepage.css

homepage.css

468 ms

slick.css

slick.css

47 ms

logo.png

logo.png

787 ms

fv_ic.png

fv_ic.png

640 ms

fv_slider1.webp

fv_slider1.webp

812 ms

fv_slider2.webp

fv_slider2.webp

640 ms

fv_slider3.webp

fv_slider3.webp

1294 ms

fv_slider4.webp

fv_slider4.webp

958 ms

ic_rate.png

ic_rate.png

806 ms

access_map.png

access_map.png

986 ms

acc_route1.jpg

acc_route1.jpg

1170 ms

ic-pin1.png

ic-pin1.png

987 ms

acc_route2.jpg

acc_route2.jpg

1117 ms

ic-pin2.png

ic-pin2.png

1172 ms

embed

embed

216 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

33 ms

common.min.js

common.min.js

1168 ms

yprox_searchForm.min.js

yprox_searchForm.min.js

1273 ms

homepage.min.js

homepage.min.js

1294 ms

slick.min.js

slick.min.js

19 ms

room_mv.webp

room_mv.webp

1500 ms

room_img1.jpg

room_img1.jpg

1330 ms

room_img2.jpg

room_img2.jpg

1593 ms

room_img3.jpg

room_img3.jpg

1430 ms

room_img4.jpg

room_img4.jpg

1452 ms

room_img5.jpg

room_img5.jpg

1456 ms

room_img6.jpg

room_img6.jpg

1503 ms

rb_img1.jpg

rb_img1.jpg

1584 ms

rb_img2.jpg

rb_img2.jpg

1613 ms

fac_img.webp

fac_img.webp

1615 ms

gall1_img.webp

gall1_img.webp

1667 ms

gall2_img.webp

gall2_img.webp

1673 ms

gall3_img.webp

gall3_img.webp

1744 ms

gall4_img.webp

gall4_img.webp

1755 ms

gall5_img.webp

gall5_img.webp

1778 ms

ic-acc.png

ic-acc.png

1778 ms

acc_hotel.webp

acc_hotel.webp

2011 ms

logo.png

logo.png

1847 ms

js

js

38 ms

search.js

search.js

6 ms

geometry.js

geometry.js

11 ms

main.js

main.js

14 ms

fv_bg.webp

fv_bg.webp

1561 ms

about_bg.webp

about_bg.webp

1582 ms

rooms_bg.webp

rooms_bg.webp

1321 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubAILO5wSiX.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubAILO5wSiX.ttf

484 ms

Qw3GZR9MED_6PSuS_50nEaVrfzgEXH0OiJM6.ttf

Qw3GZR9MED_6PSuS_50nEaVrfzgEXH0OiJM6.ttf

535 ms

icomoon.ttf

icomoon.ttf

1320 ms

rb_bg.webp

rb_bg.webp

1398 ms

fac_bg.webp

fac_bg.webp

1437 ms

acc_bg.webp

acc_bg.webp

1302 ms

rsv_bg.webp

rsv_bg.webp

1310 ms

Accessibility Review

yth.jp accessibility score

93

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-hidden="true"] elements contain focusable descendents

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

yth.jp SEO score

91

Search Engine Optimization Advices

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 doesn't use 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 Yth.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 Yth.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

yth.jp

Open Graph data is detected on the main page of Yth. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: