Tools & Wizards About Us
0100.co.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

0100.co.jp

愛川の宿　観泉荘こまや ホーム-TOP | ホーム

Page Load Speed

7.2 sec in total

First Response

519 ms

Resources Loaded

6.6 sec

Page Rendered

128 ms

0100.co.jp screenshot

About Website

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

japanese traditional hotel,「kansenso komaya」. 大切な方と個室で地野菜と鮎や猪、鹿のジビエ料理等で楽しく思い出深いものとなりますようお手伝いします。 箱根より都心に近く、県央道開通で便利になりました。

Visit 0100.co.jp

Key Findings

We analyzed 0100.co.jp page load time and found that the first response time was 519 ms and then it took 6.7 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

0100.co.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

0100.co.jp

519 ms

www.0100.co.jp

918 ms

prototype.js

1475 ms

scriptaculous.js

390 ms

lightbox.js

768 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 97% of them (99 requests) were addressed to the original 0100.co.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain 0100.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.0 kB (79%)

Content Size

391.6 kB

After Optimization

83.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 8.3 kB

  • Original 11.1 kB
  • After minification 8.4 kB
  • After compression 2.8 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.7 kB, which is 24% 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 8.3 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 387 B

  • Original 4.6 kB
  • After minification 4.2 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. 0100 images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 171.0 kB

  • Original 227.0 kB
  • After minification 168.1 kB
  • After compression 56.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 171.0 kB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 128.3 kB

  • Original 148.9 kB
  • After minification 84.9 kB
  • After compression 20.6 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. 0100.co.jp needs all CSS files to be minified and compressed as it can save up to 128.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 88 (88%)

Requests Now

100

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

0100.co.jp

0100.co.jp

519 ms

www.0100.co.jp

www.0100.co.jp

918 ms

prototype.js

prototype.js

1475 ms

scriptaculous.js

scriptaculous.js

390 ms

lightbox.js

lightbox.js

768 ms

lightbox.css

lightbox.css

395 ms

imported.js

imported.js

399 ms

livepipe.js

livepipe.js

600 ms

tabs.js

tabs.js

584 ms

imported.css

imported.css

591 ms

common.css

common.css

836 ms

common.css

common.css

779 ms

AllUnits.css

AllUnits.css

1373 ms

extFlash.css

extFlash.css

614 ms

effects.js

effects.js

783 ms

builder.js

builder.js

400 ms

widgets.js

widgets.js

78 ms

common.css

common.css

202 ms

color.css

color.css

399 ms

layout.css

layout.css

402 ms

imported.css

imported.css

186 ms

imported.css

imported.css

202 ms

imported2.css

imported2.css

192 ms

cunit_1.css

cunit_1.css

186 ms

cunit_4.css

cunit_4.css

199 ms

cunit1_2.css

cunit1_2.css

205 ms

cunit1_3.css

cunit1_3.css

210 ms

cunit2_2.css

cunit2_2.css

369 ms

cunit2_3.css

cunit2_3.css

390 ms

cunit3_2.css

cunit3_2.css

399 ms

cunit3_3.css

cunit3_3.css

405 ms

cunit4_2.css

cunit4_2.css

410 ms

cunit4_3.css

cunit4_3.css

412 ms

cunit5_2.css

cunit5_2.css

551 ms

cunit5_3.css

cunit5_3.css

579 ms

cunit6_2.css

cunit6_2.css

593 ms

cunit7_2.css

cunit7_2.css

599 ms

cunit8_2.css

cunit8_2.css

607 ms

cunit9_2.css

cunit9_2.css

610 ms

bAnchor.css

bAnchor.css

732 ms

bAnchorSide.css

bAnchorSide.css

768 ms

bContact.css

bContact.css

786 ms

bFlaDl.css

bFlaDl.css

793 ms

bFlash.css

bFlash.css

805 ms

bJava.css

bJava.css

808 ms

bMap.css

bMap.css

915 ms

bPageTop.css

bPageTop.css

957 ms

bRssReader.css

bRssReader.css

979 ms

bSiteMap.css

bSiteMap.css

987 ms

bCatList.css

bCatList.css

1001 ms

bCatList2.css

bCatList2.css

1006 ms

bCatList3.css

bCatList3.css

1098 ms

bCatList4.css

bCatList4.css

1337 ms

bVCatList2.css

bVCatList2.css

1173 ms

bVCatList3.css

bVCatList3.css

1377 ms

common.css

common.css

1197 ms

bImg.css

bImg.css

1202 ms

bImg2Txt2.css

bImg2Txt2.css

1108 ms

bImg3Txt3.css

bImg3Txt3.css

1182 ms

bImgBtn.css

bImgBtn.css

1208 ms

bImgOrg.css

bImgOrg.css

1210 ms

bImgttl.css

bImgttl.css

1266 ms

bImgTtlTxt.css

bImgTtlTxt.css

1328 ms

bImgTtlTxt2.css

bImgTtlTxt2.css

1207 ms

bImgTxt.css

bImgTxt.css

1196 ms

bItems.css

bItems.css

1211 ms

bLine.css

bLine.css

1213 ms

bList2.css

bList2.css

1251 ms

bPdf.css

bPdf.css

1319 ms

bSubTtl.css

bSubTtl.css

1219 ms

bTtl.css

bTtl.css

1200 ms

bTtlBg.css

bTtlBg.css

1215 ms

bTxt.css

bTxt.css

1216 ms

bTxtImg.css

bTxtImg.css

1236 ms

bVImgTtlTxt.css

bVImgTtlTxt.css

1311 ms

bVImgTtlTxt2.css

bVImgTtlTxt2.css

1229 ms

bVImgTxt.css

bVImgTxt.css

1205 ms

ga.js

ga.js

27 ms

bg.gif

bg.gif

428 ms

__utm.gif

__utm.gif

32 ms

4-logo.gif

4-logo.gif

201 ms

4-banner.gif

4-banner.gif

201 ms

shadow_top.png

shadow_top.png

186 ms

g_navi_home.gif

g_navi_home.gif

198 ms

g_navi_topics.gif

g_navi_topics.gif

193 ms

g_navi_bath.gif

g_navi_bath.gif

370 ms

g_navi_room.gif

g_navi_room.gif

385 ms

g_navi_meal.gif

g_navi_meal.gif

393 ms

g_navi_barbecue.gif

g_navi_barbecue.gif

398 ms

g_navi_hoji.gif

g_navi_hoji.gif

400 ms

g_navi_banquet.gif

g_navi_banquet.gif

556 ms

g_navi_petblog.gif

g_navi_petblog.gif

574 ms

g_navi_nakatogawa.gif

g_navi_nakatogawa.gif

588 ms

g_navi_area.gif

g_navi_area.gif

597 ms

shadow_home.png

shadow_home.png

599 ms

main_bg.gif

main_bg.gif

609 ms

shadow_home_bottom.png

shadow_home_bottom.png

737 ms

line_dot.gif

line_dot.gif

766 ms

footer_navi_ico.gif

footer_navi_ico.gif

784 ms

logo_gurunabi.gif

logo_gurunabi.gif

795 ms

loading.gif

loading.gif

799 ms

closelabel.gif

closelabel.gif

803 ms

Accessibility Review

0100.co.jp accessibility score

63

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

0100.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

0100.co.jp SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 0100.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 0100.co.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

0100.co.jp

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