4 sec in total
473 ms
954 ms
2.6 sec
Click here to check amazing Booklike content. Otherwise, check out these important facts you probably never knew about booklike.jp
良本生活。今までにない本のレビューサービス。面白い本が探せる!失敗しない本探し!さまざまな本の書評(レビュー)をお届けします。
Visit booklike.jpWe analyzed Booklike.jp page load time and found that the first response time was 473 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
booklike.jp performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value0.8 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.8 s
100/100
10%
473 ms
151 ms
156 ms
155 ms
7 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 13% of them (8 requests) were addressed to the original Booklike.jp, 79% (50 requests) were made to Ecx.images-amazon.com and 3% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (473 ms) belongs to the original domain Booklike.jp.
Page size can be reduced by 374.2 kB (16%)
2.4 MB
2.0 MB
In fact, the total size of Booklike.jp main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 87.9 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 14.7 kB, which is 13% 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 87.9 kB or 79% of the original size.
Potential reduce by 143.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. Booklike images are well optimized though.
Potential reduce by 88.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 88.2 kB or 58% of the original size.
Potential reduce by 54.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. Booklike.jp needs all CSS files to be minified and compressed as it can save up to 54.5 kB or 82% of the original size.
Number of requests can be reduced by 8 (13%)
62
54
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Booklike. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
booklike.jp
473 ms
main2.css
151 ms
header2.css
156 ms
rset2.css
155 ms
jquery-ui.css
7 ms
jquery-ui.js
11 ms
jquery-1.10.1.min.js
231 ms
masonry.pkgd.min.js
164 ms
jquery.balloon.js
165 ms
416KTVyoPgL.jpg
170 ms
logo.png
224 ms
41-Wp0orjAL.jpg
170 ms
51f-5D90E%2BL.jpg
166 ms
41ioLMk1oZL.jpg
165 ms
51A2uOjjKIL.jpg
168 ms
51YYzSrQAVL.jpg
167 ms
41yJju35wUL.jpg
171 ms
414AbY7vq1L.jpg
171 ms
61P4JSTG-AL.jpg
172 ms
41%2BKjxfWfdL.jpg
169 ms
51uKBWjbL7L.jpg
173 ms
51DyjDPdPOL.jpg
172 ms
51AoeI6qzcL.jpg
175 ms
613gRZliesL.jpg
177 ms
31KAIJrlNoL.jpg
174 ms
61aXy2LzdQL.jpg
176 ms
41OO4JZJnRL.jpg
184 ms
41zyW0QnSWL.jpg
175 ms
5102pl-ZdUL.jpg
179 ms
51It3rJzSaL.jpg
178 ms
51oE%2BZVM1ZL.jpg
177 ms
41ZEAzcQ8KL.jpg
176 ms
51whkj3HPbL.jpg
179 ms
51q%2BPRNAoUL.jpg
181 ms
51ynxuIesnL.jpg
179 ms
41BoxP0jqUL.jpg
187 ms
41KR1Z3h%2BXL.jpg
180 ms
41zbXvvdo6L.jpg
179 ms
51t-Qij4DLL.jpg
181 ms
31jLwPzsvcL.jpg
181 ms
51bMjClwdOL.jpg
182 ms
41ETak1hgcL.jpg
185 ms
61z-15UdqHL.jpg
183 ms
51W0a%2B1XhqL.jpg
183 ms
41rBEDOJtQL.jpg
184 ms
410Q6Ehg5CL.jpg
184 ms
41S%2Bt30zRAL.jpg
30 ms
51yNlfknFqL.jpg
55 ms
51gMWaFt7IL.jpg
54 ms
41rG-JTJgzL.jpg
27 ms
5169KLr8I6L.jpg
51 ms
51wUpdCEm0L.jpg
27 ms
5139TGko-1L.jpg
27 ms
418ZXrcrIPL.jpg
26 ms
51mzC2sYt2L.jpg
26 ms
41h9p9NG24L.jpg
26 ms
51wxiKOezQL.jpg
27 ms
51HzEl5qdHL.jpg
25 ms
41oUv-qCNPL.jpg
32 ms
41R13MDt57L.jpg
32 ms
analytics.js
7 ms
sdk.js
71 ms
collect
10 ms
booklike.jp accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
booklike.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
booklike.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Booklike.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 Booklike.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.
booklike.jp
Open Graph description is not detected on the main page of Booklike. 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: