4.8 sec in total
1.1 sec
3.5 sec
225 ms
Visit tohan.jp now to see the best up-to-date Tohan content for Japan and also check out these interesting facts you probably never knew about tohan.jp
株式会社トーハンの公式WEBサイトです。トーハンは出版社と書店、読者を結ぶ出版流通ネットワークを構築しています。
Visit tohan.jpWe analyzed Tohan.jp page load time and found that the first response time was 1.1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tohan.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value8.7 s
1/100
25%
Value10.1 s
9/100
10%
Value690 ms
43/100
30%
Value0.596
11/100
15%
Value7.1 s
52/100
10%
1055 ms
682 ms
866 ms
522 ms
1301 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 90% of them (54 requests) were addressed to the original Tohan.jp, 5% (3 requests) were made to Shutto.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Tohan.jp.
Page size can be reduced by 233.4 kB (25%)
924.7 kB
691.3 kB
In fact, the total size of Tohan.jp main page is 924.7 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. 30% of websites need less resources to load. Images take 657.8 kB which makes up the majority of the site volume.
Potential reduce by 25.7 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 6.3 kB, which is 20% 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 25.7 kB or 81% of the original size.
Potential reduce by 49.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. Tohan images are well optimized though.
Potential reduce by 87.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 87.1 kB or 58% of the original size.
Potential reduce by 71.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. Tohan.jp needs all CSS files to be minified and compressed as it can save up to 71.5 kB or 84% of the original size.
Number of requests can be reduced by 8 (14%)
58
50
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tohan. 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.
tohan.jp
1055 ms
layout.css
682 ms
contents.css
866 ms
top.css
522 ms
jquery.js
1301 ms
common.js
810 ms
smp.js
694 ms
jquery.spreadSlider.js
773 ms
convert.js
371 ms
analytics.js
108 ms
150319_raziralogo.jpg
939 ms
blogp.html
199 ms
header_logo01.gif
176 ms
com_sprite01.png
205 ms
header_nav01.gif
188 ms
main_bg04.jpg
512 ms
main_tx01_l.png
176 ms
main_tx04.png
324 ms
main_bg05.jpg
520 ms
main_tx02_l.png
349 ms
main_tx05.png
373 ms
main_bg06.jpg
406 ms
main_tx03_l.png
517 ms
main_tx06.png
520 ms
index_h01.png
558 ms
index_bg01.gif
608 ms
index_tx01.png
679 ms
com_ic02.png
710 ms
index_tx02.png
691 ms
index_tx03.png
693 ms
com_bn04.png
742 ms
com_bn05.png
808 ms
com_bn06.png
848 ms
index_h03.png
863 ms
com_bn07.png
863 ms
com_bn08.png
902 ms
index_h04.png
926 ms
com_bn09.png
1009 ms
com_bn15.png
1018 ms
com_bn16.png
1035 ms
com_logo08.png
1036 ms
com_bt02.png
1097 ms
footer_bg01.gif
1112 ms
footer_bg02.gif
1246 ms
com_ic01.png
1189 ms
com_bt01.png
1208 ms
gogotama_logo.jpg
893 ms
2016022seminarhouse.jpg
1077 ms
20160218hkphotobook.jpg
764 ms
20160218hokkokushorincafe.jpg
970 ms
20160217akatsuki.jpg
998 ms
20160216nurie.jpg
1119 ms
20160215_ehon.jpg
1012 ms
150319_raziralogo.jpg
1060 ms
collect
12 ms
collect
56 ms
blogp.css
1089 ms
pv_beacon.gif
375 ms
index_h02.png
197 ms
pv_beacon.gif
381 ms
tohan.jp accessibility score
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
<frame> or <iframe> elements do not have a title
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
tohan.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
tohan.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tohan.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 Tohan.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.
tohan.jp
Open Graph description is not detected on the main page of Tohan. 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: