Tools & Wizards About Us
100hyakunen.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

100hyakunen.com

吉祥寺「百年」古本の買取と販売

Page Load Speed

5.5 sec in total

First Response

1.1 sec

Resources Loaded

4.2 sec

Page Rendered

167 ms

100hyakunen.com screenshot

About Website

Visit 100hyakunen.com now to see the best up-to-date 100 Hyakunen content and also check out these interesting facts you probably never knew about 100hyakunen.com

吉祥寺にある古本屋「百年」のウェブサイト／トークや作品展示などイベントも行っています／出張買取も行っていますのでお気軽にお問い合わせください

Visit 100hyakunen.com

Key Findings

We analyzed 100hyakunen.com page load time and found that the first response time was 1.1 sec and then it took 4.4 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

100hyakunen.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value20,530 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value34.9 s

0/100

10%

Network Requests Diagram

www.100hyakunen.com

1128 ms

wp-emoji-release.min.js

180 ms

style.min.css

338 ms

styles.css

348 ms

colorbox.css

347 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 57% of them (39 requests) were addressed to the original 100hyakunen.com, 16% (11 requests) were made to Platform.twitter.com and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain 100hyakunen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.9 kB (12%)

Content Size

375.1 kB

After Optimization

330.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 32.4 kB

  • Original 42.7 kB
  • After minification 41.7 kB
  • After compression 10.3 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 32.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 5.5 kB

  • Original 233.3 kB
  • After minification 227.8 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. 100 Hyakunen images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 4.8 kB

  • Original 78.0 kB
  • After minification 78.0 kB
  • After compression 73.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 2.2 kB

  • Original 21.2 kB
  • After minification 21.2 kB
  • After compression 18.9 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. 100hyakunen.com needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (63%)

Requests Now

68

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.100hyakunen.com

www.100hyakunen.com

1128 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

180 ms

style.min.css

style.min.css

338 ms

styles.css

styles.css

348 ms

colorbox.css

colorbox.css

347 ms

fotorama.css

fotorama.css

344 ms

style.css

style.css

358 ms

editor352.js

editor352.js

351 ms

jquery.min.js

jquery.min.js

8 ms

jquery.cookie.js

jquery.cookie.js

505 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

512 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

521 ms

fotorama.js

fotorama.js

521 ms

widgets.js

widgets.js

38 ms

scripts.js

scripts.js

523 ms

imagesloaded.min.js

imagesloaded.min.js

537 ms

masonry.min.js

masonry.min.js

682 ms

wp-embed.min.js

wp-embed.min.js

681 ms

setup.js

setup.js

759 ms

setup.css

setup.css

338 ms

paint2.jpg

paint2.jpg

174 ms

btnTWTR_min.png

btnTWTR_min.png

175 ms

btnFB_min.png

btnFB_min.png

175 ms

btnINSTGRM_min.png

btnINSTGRM_min.png

181 ms

btnSearch_min.png

btnSearch_min.png

167 ms

siteLogo_min.png

siteLogo_min.png

168 ms

copy-copy-img_1001.jpg

copy-copy-img_1001.jpg

523 ms

bnrStore-min.png

bnrStore-min.png

338 ms

bnrPR-min.png

bnrPR-min.png

349 ms

bnrRainy-min.png

bnrRainy-min.png

347 ms

bnrPurchase-min.png

bnrPurchase-min.png

348 ms

bnrAccess-min.png

bnrAccess-min.png

359 ms

bnrIchinichi-min.png

bnrIchinichi-min.png

510 ms

d10cfb09c6b976574ae24d41c6413ace-200x200.jpg

d10cfb09c6b976574ae24d41c6413ace-200x200.jpg

528 ms

ae2a0d1a1b9746d134be7ab08ffa590f-200x200.jpg

ae2a0d1a1b9746d134be7ab08ffa590f-200x200.jpg

523 ms

DM-135x200.jpg

DM-135x200.jpg

539 ms

20240419-200x200.jpg

20240419-200x200.jpg

543 ms

20240426-200x160.jpg

20240426-200x160.jpg

680 ms

2024411a-150x200.jpg

2024411a-150x200.jpg

700 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

132 ms

overlay.png

overlay.png

624 ms

fotorama.png

fotorama.png

628 ms

sdk.js

sdk.js

15 ms

sdk.js

sdk.js

7 ms

37 ms

settings

settings

108 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

20 ms

100hyakunen

100hyakunen

955 ms

page.php

page.php

135 ms

lFC1eVji7gN.css

lFC1eVji7gN.css

20 ms

AkV4cevgxL7.js

AkV4cevgxL7.js

25 ms

O1Rb7CQsNyZ.js

O1Rb7CQsNyZ.js

22 ms

HbT8HXdZYIC.js

HbT8HXdZYIC.js

49 ms

9RGXrkPnS_6.js

9RGXrkPnS_6.js

48 ms

IfxMrflzyZZ.js

IfxMrflzyZZ.js

48 ms

p55HfXW__mM.js

p55HfXW__mM.js

48 ms

W-g8DGupFWF.js

W-g8DGupFWF.js

53 ms

305230962_493165446147688_6085459253587897544_n.jpg

305230962_493165446147688_6085459253587897544_n.jpg

189 ms

303567271_493165449481021_112423792274543858_n.jpg

303567271_493165449481021_112423792274543858_n.jpg

85 ms

GN5dD2mIuLr.js

GN5dD2mIuLr.js

7 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

4 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

23 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

41 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

62 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

73 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

93 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

96 ms

_buildManifest.js

_buildManifest.js

107 ms

_ssgManifest.js

_ssgManifest.js

106 ms

Accessibility Review

100hyakunen.com accessibility score

87

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

<input type="image"> elements do not have [alt] text

High

Links do not have a discernible name

Best Practices

100hyakunen.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

100hyakunen.com SEO score

69

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

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 100hyakunen.com 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 100hyakunen.com 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

100hyakunen.com

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