Tools & Wizards About Us
capsule510.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

capsule510.jp

新宿のカプセルホテル・サウナなら510グループ

Page Load Speed

6.4 sec in total

First Response

1.2 sec

Resources Loaded

4.9 sec

Page Rendered

297 ms

capsule510.jp screenshot

About Website

Visit capsule510.jp now to see the best up-to-date Capsule 510 content for Japan and also check out these interesting facts you probably never knew about capsule510.jp

都内どこでもアクセスの良い新宿。 繁華街に隣接した静かな立地にあるカプセルホテル。

Visit capsule510.jp

Key Findings

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

Performance Metrics

capsule510.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.61

10/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

capsule510.jp

1189 ms

set.css

349 ms

blueberry.css

361 ms

jsapi

17 ms

bace.js

361 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 59% of them (57 requests) were addressed to the original Capsule510.jp, 14% (14 requests) were made to Maps.googleapis.com and 7% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Capsule510.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 23.7 kB

  • Original 31.4 kB
  • After minification 30.6 kB
  • After compression 7.6 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 23.7 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 63.3 kB

  • Original 936.0 kB
  • After minification 872.7 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. Capsule 510 images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 573.6 kB

  • Original 865.7 kB
  • After minification 861.4 kB
  • After compression 292.1 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 573.6 kB or 66% of the original size.

CSS Optimization

-79%

Potential reduce by 27.7 kB

  • Original 35.2 kB
  • After minification 25.0 kB
  • After compression 7.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. Capsule510.jp needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (35%)

Requests Now

92

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

capsule510.jp

capsule510.jp

1189 ms

set.css

set.css

349 ms

blueberry.css

blueberry.css

361 ms

jsapi

jsapi

17 ms

bace.js

bace.js

361 ms

jTabs.js

jTabs.js

371 ms

search.js

search.js

372 ms

colorbox.css

colorbox.css

500 ms

styles.css

styles.css

523 ms

css3_black.css

css3_black.css

539 ms

jquery.js

jquery.js

1436 ms

jquery-migrate.min.js

jquery-migrate.min.js

738 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

617 ms

jquery-colorbox-wrapper-min.js

jquery-colorbox-wrapper-min.js

506 ms

jquery.form.min.js

jquery.form.min.js

712 ms

scripts.js

scripts.js

607 ms

default.css

default.css

492 ms

layout.css

layout.css

945 ms

jquery.min.js

jquery.min.js

26 ms

sdk.js

sdk.js

27 ms

bodyBg.png

bodyBg.png

184 ms

logo.png

logo.png

409 ms

br.png

br.png

723 ms

newBtn03_off.png

newBtn03_off.png

187 ms

mypageBtn03_off.png

mypageBtn03_off.png

185 ms

footerBnr_off.png

footerBnr_off.png

553 ms

gnavi01.png

gnavi01.png

410 ms

gnavi02_off.png

gnavi02_off.png

435 ms

gnavi03_off.png

gnavi03_off.png

434 ms

gnavi04_off.png

gnavi04_off.png

551 ms

gnavi05_off.png

gnavi05_off.png

599 ms

mainImg.jpg

mainImg.jpg

2068 ms

topMainLogo.png

topMainLogo.png

626 ms

sinzyuku510Bnr_off.png

sinzyuku510Bnr_off.png

705 ms

wormanBnr_off.png

wormanBnr_off.png

892 ms

supaBnr_off.png

supaBnr_off.png

912 ms

topMainBg01.png

topMainBg01.png

786 ms

reserveText.png

reserveText.png

878 ms

searchTi.png

searchTi.png

898 ms

mainOnlineBnr_off.png

mainOnlineBnr_off.png

1140 ms

couponBnr_off.png

couponBnr_off.png

1051 ms

point01.png

point01.png

1261 ms

point02.png

point02.png

1255 ms

point03.png

point03.png

1078 ms

point04.png

point04.png

1225 ms

point05.png

point05.png

1246 ms

point06.png

point06.png

1319 ms

hotelList01.png

hotelList01.png

2441 ms

listMore_off.png

listMore_off.png

1416 ms

hotelList03.png

hotelList03.png

2510 ms

hotelList02.png

hotelList02.png

2555 ms

accessTi.png

accessTi.png

1498 ms

more_off.png

more_off.png

1582 ms

infoTi.png

infoTi.png

1678 ms

newsMore_off.png

newsMore_off.png

1751 ms

fLogo.png

fLogo.png

1852 ms

embed

embed

134 ms

306 ms

xd_arbiter.php

xd_arbiter.php

19 ms

xd_arbiter.php

xd_arbiter.php

38 ms

js

js

90 ms

init_embed.js

init_embed.js

46 ms

onlineBtn_off.png

onlineBtn_off.png

1744 ms

topMainBg02.png

topMainBg02.png

1862 ms

arrow.png

arrow.png

1911 ms

common.js

common.js

79 ms

map.js

map.js

104 ms

google4.png

google4.png

167 ms

overlay.js

overlay.js

57 ms

util.js

util.js

164 ms

onion.js

onion.js

164 ms

search_impl.js

search_impl.js

163 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

311 ms

overlay.png

overlay.png

1818 ms

stats.js

stats.js

97 ms

openhand_8_8.cur

openhand_8_8.cur

34 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

73 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

63 ms

kh

kh

117 ms

kh

kh

117 ms

transparent.png

transparent.png

53 ms

controls.js

controls.js

49 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

66 ms

vt

vt

122 ms

vt

vt

158 ms

vt

vt

135 ms

vt

vt

133 ms

vt

vt

152 ms

css

css

94 ms

entity11.png

entity11.png

49 ms

mapcnt6.png

mapcnt6.png

29 ms

tmapctrl.png

tmapctrl.png

28 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

28 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

35 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

40 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

39 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

26 ms

Accessibility Review

capsule510.jp accessibility score

51

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

capsule510.jp best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

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

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

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

capsule510.jp

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