Tools & Wizards About Us
thekai.jp screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

thekai.jp

A hub of connection. Welcome to Kaisu. | KAISU HOSTEL

Page Load Speed

8 sec in total

First Response

512 ms

Resources Loaded

7.3 sec

Page Rendered

167 ms

thekai.jp screenshot

About Website

Visit thekai.jp now to see the best up-to-date Thekai content and also check out these interesting facts you probably never knew about thekai.jp

Right in the heart of Tokyo. Private & shared accommodations with cafe and bar.A ryotel. Diversity & relaxed vibe. A sound place.

Visit thekai.jp

Key Findings

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

thekai.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

thekai.jp

512 ms

kaisu.jp

1040 ms

reset.css

420 ms

font.css

625 ms

style.css

496 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Thekai.jp, 93% (40 requests) were made to Kaisu.jp and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Kaisu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.0 kB (8%)

Content Size

3.5 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 11.9 kB

  • Original 16.6 kB
  • After minification 14.2 kB
  • After compression 4.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 2.4 kB, which is 14% 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 11.9 kB or 71% of the original size.

Image Optimization

-4%

Potential reduce by 126.8 kB

  • Original 3.3 MB
  • After minification 3.2 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. Thekai images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 118.4 kB

  • Original 186.2 kB
  • After minification 162.1 kB
  • After compression 67.8 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 118.4 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 34.9 kB

  • Original 41.5 kB
  • After minification 29.8 kB
  • After compression 6.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. Thekai.jp needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (27%)

Requests Now

37

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thekai. 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

thekai.jp

thekai.jp

512 ms

kaisu.jp

kaisu.jp

1040 ms

reset.css

reset.css

420 ms

font.css

font.css

625 ms

style.css

style.css

496 ms

style.custom.css

style.custom.css

2788 ms

flexslider.css

flexslider.css

1033 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

1441 ms

common.js

common.js

623 ms

wp-embed.min.js

wp-embed.min.js

540 ms

jquery.flexslider.js

jquery.flexslider.js

958 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

885 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

262 ms

analytics.js

analytics.js

92 ms

mini_logo.png

mini_logo.png

701 ms

bar_room.png

bar_room.png

232 ms

bar_story.png

bar_story.png

488 ms

bar_news.png

bar_news.png

698 ms

bar_access.png

bar_access.png

454 ms

bar_bar.png

bar_bar.png

938 ms

bar_magazine.png

bar_magazine.png

944 ms

head_img2.png

head_img2.png

1266 ms

kaisu_logo.png

kaisu_logo.png

910 ms

rooms.png

rooms.png

1090 ms

story.png

story.png

965 ms

news.png

news.png

1084 ms

access.png

access.png

1283 ms

bar.png

bar.png

1263 ms

gust_book.png

gust_book.png

1142 ms

booknow.png

booknow.png

1259 ms

KAI_f-142_sd_web.jpg

KAI_f-142_sd_web.jpg

2402 ms

KAI_f-272_sd_web.jpg

KAI_f-272_sd_web.jpg

2624 ms

dusitn9.jpg

dusitn9.jpg

1915 ms

KAI_f-027_s_web.jpg

KAI_f-027_s_web.jpg

2715 ms

KAI_f-085_sd_web.jpg

KAI_f-085_sd_web.jpg

2243 ms

KAI_f-302_s_web.jpg

KAI_f-302_s_web.jpg

2913 ms

FB-f-Logo__blue_29.png

FB-f-Logo__blue_29.png

2128 ms

glyph-logo_May2016.png

glyph-logo_May2016.png

2293 ms

TiemposHeadline-Regular.woff

TiemposHeadline-Regular.woff

2307 ms

TiemposText-Semibold.woff

TiemposText-Semibold.woff

2358 ms

TiemposHeadline-Light.woff

TiemposHeadline-Light.woff

2465 ms

Tiempos%20Headline-LightItalic.woff

Tiempos%20Headline-LightItalic.woff

2480 ms

collect

collect

50 ms

Accessibility Review

thekai.jp accessibility score

65

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

SEO Factors

thekai.jp SEO score

64

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thekai.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Thekai.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

thekai.jp

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