Tools & Wizards About Us
e-otomari.jp screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

e-otomari.jp

東京の安い宿【東簡宿】The Economy Hotels in Tokyo

Page Load Speed

5.4 sec in total

First Response

806 ms

Resources Loaded

4.3 sec

Page Rendered

238 ms

e-otomari.jp screenshot

About Website

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

宿泊代を節約して、買物がしたい!おいしいものを食べたい!コンサートに行きたい!そんな東京を満喫したい人のための宿「東簡宿」。

Visit e-otomari.jp

Key Findings

We analyzed E-otomari.jp page load time and found that the first response time was 806 ms and then it took 4.6 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

e-otomari.jp performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

e-otomari.jp

806 ms

supersized.css

348 ms

jquery.min.js

19 ms

jquery.easing.min.js

521 ms

supersized.3.2.7.min.js

694 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 95% of them (21 requests) were addressed to the original E-otomari.jp, 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain E-otomari.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.5 kB (5%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-66%

Potential reduce by 4.1 kB

  • Original 6.1 kB
  • After minification 5.9 kB
  • After compression 2.1 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 4.1 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 67.6 kB

  • Original 2.1 MB
  • After minification 2.0 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. E Otomari images are well optimized though.

JavaScript Optimization

-83%

Potential reduce by 20.8 kB

  • Original 24.9 kB
  • After minification 21.5 kB
  • After compression 4.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 20.8 kB or 83% of the original size.

CSS Optimization

-74%

Potential reduce by 3.0 kB

  • Original 4.1 kB
  • After minification 3.1 kB
  • After compression 1.1 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. E-otomari.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 74% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Otomari. According to our analytics all requests are already optimized.

Network Requests Diagram

e-otomari.jp

e-otomari.jp

806 ms

supersized.css

supersized.css

348 ms

jquery.min.js

jquery.min.js

19 ms

jquery.easing.min.js

jquery.easing.min.js

521 ms

supersized.3.2.7.min.js

supersized.3.2.7.min.js

694 ms

supersized.shutter.min.js

supersized.shutter.min.js

373 ms

bace_top.css

bace_top.css

372 ms

rogo.png

rogo.png

714 ms

linkmark.png

linkmark.png

185 ms

e_title.png

e_title.png

347 ms

j_title.png

j_title.png

522 ms

block-left.png

block-left.png

367 ms

08.jpg

08.jpg

2969 ms

01.jpg

01.jpg

1387 ms

02.jpg

02.jpg

2204 ms

progress.gif

progress.gif

521 ms

about_buttn.png

about_buttn.png

1095 ms

toha_button.png

toha_button.png

1095 ms

annaimap300.png

annaimap300.png

1685 ms

jyohoku_bana.png

jyohoku_bana.png

744 ms

osaka_bana.png

osaka_bana.png

744 ms

toukan_rg.gif

toukan_rg.gif

869 ms

Accessibility Review

e-otomari.jp accessibility score

69

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

Links do not have a discernible name

Best Practices

e-otomari.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

e-otomari.jp SEO score

83

Search Engine Optimization Advices

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-otomari.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that E-otomari.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

e-otomari.jp

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