15 sec in total
546 ms
14.3 sec
203 ms
Click here to check amazing Tusinbo content for Japan. Otherwise, check out these important facts you probably never knew about tusinbo.com
「病院の通信簿」は、患者さんの口コミ、評価、評判で病院や歯科を検索出来る日本最大級の病院口コミサイトです。実際の診察や治療を受け一人一人の声を集めて公開中。「病院の通信簿」では、あなたの投票を随時受け付けています。
Visit tusinbo.comWe analyzed Tusinbo.com page load time and found that the first response time was 546 ms and then it took 14.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tusinbo.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.2 s
45/100
25%
Value9.7 s
10/100
10%
Value10,960 ms
0/100
30%
Value0.923
3/100
15%
Value20.1 s
2/100
10%
546 ms
1512 ms
365 ms
900 ms
1450 ms
Our browser made a total of 274 requests to load all elements on the main page. We found that 57% of them (157 requests) were addressed to the original Tusinbo.com, 5% (14 requests) were made to Pagead2.googlesyndication.com and 3% (9 requests) were made to Cs.adingo.jp. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Tusinbo.com.
Page size can be reduced by 799.0 kB (49%)
1.6 MB
827.3 kB
In fact, the total size of Tusinbo.com main page is 1.6 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 29.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 6.9 kB, which is 18% 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 29.8 kB or 79% of the original size.
Potential reduce by 34.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. Tusinbo images are well optimized though.
Potential reduce by 670.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 670.1 kB or 65% of the original size.
Potential reduce by 64.4 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. Tusinbo.com needs all CSS files to be minified and compressed as it can save up to 64.4 kB or 81% of the original size.
Number of requests can be reduced by 151 (57%)
266
115
The browser has sent 266 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tusinbo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and as a result speed up the page load time.
tusinbo.com
546 ms
www.tusinbo.com
1512 ms
showlistings.css
365 ms
www_application.css
900 ms
www_application.js
1450 ms
jquery.fancybox.css
388 ms
ach.js
360 ms
showlistings.js
386 ms
AdLantisLoader.js
1230 ms
keyword.php
376 ms
keyword.php
340 ms
aca.js
490 ms
bg.gif
360 ms
dr120-4.jpg
897 ms
hara.jpg
553 ms
1.jpg
911 ms
h1_title.gif
354 ms
header_btn_login.gif
357 ms
header_btn_regist.gif
360 ms
globalnav_top.gif
377 ms
globalnav_new.gif
377 ms
globalnav_regist.gif
683 ms
h3_areamap.gif
732 ms
areamap_hokkaido.gif
733 ms
areamap_aomori.gif
755 ms
areamap_iwate.gif
747 ms
areamap_miyagi.gif
758 ms
areamap_akita.gif
1042 ms
areamap_yamagata.gif
1086 ms
areamap_fukushima.gif
1104 ms
areamap_ibaragi.gif
1098 ms
areamap_tochigi.gif
1087 ms
areamap_gunma.gif
1134 ms
areamap_saitama.gif
1376 ms
areamap_chiba.gif
1425 ms
areamap_tokyo.gif
1437 ms
areamap_kanagawa.gif
1439 ms
areamap_niigata.gif
1448 ms
areamap_toyama.gif
1508 ms
areamap_ishikawa.gif
1762 ms
areamap_fukui.gif
1765 ms
areamap_yamanashi.gif
1782 ms
areamap_nagano.gif
1815 ms
areamap_gifu.gif
1824 ms
areamap_shizuoka.gif
1851 ms
areamap_aichi.gif
2070 ms
areamap_mie.gif
2145 ms
areamap_osaka.gif
2204 ms
areamap_hyogo.gif
2214 ms
areamap_kyoto.gif
2214 ms
areamap_shiga.gif
2212 ms
analytics.js
27 ms
adlantis.www.js
188 ms
swfobject.js
373 ms
collect
10 ms
collect
71 ms
areamap_nara.gif
2118 ms
areamap_wakayama.gif
2178 ms
areamap_tottori.gif
2220 ms
areamap_shimane.gif
2222 ms
areamap_okayama.gif
2222 ms
areamap_hiroshima.gif
2231 ms
load_script
374 ms
load_script
381 ms
load_script
385 ms
areamap_yamaguchi.gif
2125 ms
areamap_tokushima.gif
2152 ms
areamap_kagawa.gif
2166 ms
areamap_ehime.gif
2167 ms
areamap_kochi.gif
2177 ms
areamap_fukuoka.gif
2220 ms
load_iframe
359 ms
load_iframe
383 ms
load_iframe
384 ms
areamap_saga.gif
2123 ms
areamap_nagasaki.gif
2130 ms
areamap_kumamoto.gif
2139 ms
areamap_oita.gif
2144 ms
areamap_miyazaki.gif
2162 ms
areamap_kagoshima.gif
2202 ms
sh.adingo.jp
388 ms
sh.adingo.jp
458 ms
sh.adingo.jp
442 ms
areamap_okinawa.gif
2139 ms
btn_hotspot_r.png
2151 ms
btn_hotspot_m.png
2163 ms
home_h3_search.gif
2153 ms
hospital_search_h4_tel.gif
2183 ms
hospital_search_h4_hospital.gif
2201 ms
sync
722 ms
pixel
88 ms
cm
384 ms
sync
94 ms
show_ads.js
38 ms
i.adingo.jp
347 ms
ca-pub-6443994818666752.js
133 ms
zrt_lookup.html
50 ms
show_ads_impl.js
49 ms
sync
24 ms
pixel
74 ms
724 ms
i.adingo.jp
331 ms
718 ms
sync
513 ms
i.adingo.jp
365 ms
ads
304 ms
ads
239 ms
ads
220 ms
osd.js
11 ms
720 ms
home_h3_feature.gif
2134 ms
h3_what.gif
2146 ms
home_what_more.png
2149 ms
upcome_mark.gif
2141 ms
searchbar.gif
2165 ms
searchbar_btn.gif
2216 ms
gen_204
35 ms
bsredirect5.js
96 ms
surly.js
295 ms
ad
53 ms
aclk
142 ms
pixel
36 ms
adj
149 ms
beacon
146 ms
pixel
27 ms
pixel
46 ms
m_js_controller.js
151 ms
abg.js
181 ms
breadcrumb.gif
2155 ms
bst2tv3.html
254 ms
verifyc.js
197 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
146 ms
dfa7banner_flash_html_inpage_rendering_lib_200_98.js
173 ms
lidar.js
42 ms
sbhK2lTE.js
83 ms
box_bg.gif
2145 ms
favicon
132 ms
favicon
129 ms
googlelogo_color_112x36dp.png
117 ms
box_h3_bg.gif
2085 ms
313 ms
311 ms
306 ms
sd
68 ms
areamap.gif
2286 ms
areamap_hokkaido_bg.gif
2129 ms
areamap_tohoku_bg.gif
2233 ms
cTrvNaRi.html
71 ms
s
58 ms
x_button_blue2.png
49 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
30 ms
6-BA107_728x90.html
10 ms
clk
90 ms
runtime.js
17 ms
antenna2.js
67 ms
dvtp_src.js
160 ms
ca
86 ms
activeview
39 ms
index.html
78 ms
159 ms
210 ms
areamap_kanto_bg.gif
2139 ms
firstevent
29 ms
easeljs-0.8.1.min.js
74 ms
tweenjs-0.6.1.min.js
80 ms
movieclip-0.8.1.min.js
80 ms
preloadjs-0.6.1.min.js
83 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250.js
50 ms
areamap_koshinetsu_bg.gif
2122 ms
161 ms
areamap_tokai_bg.gif
2098 ms
dvtp_src_internal25.js
44 ms
4.gif
40 ms
ba.html
99 ms
areamap_chugoku_bg.gif
2118 ms
areamap_kyushu_bg.gif
2243 ms
hospital_search_tab_bg.gif
2248 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.json
4 ms
CCT6738_3_Q1_LC_Lifestyle_ACQ_Sp_NED69.99x12_X1DVR10_300x250_atlas_.png
53 ms
t2tv7.html
54 ms
visit.js
51 ms
4311.js
32 ms
avs5634.js
39 ms
query.js
46 ms
activeview
42 ms
activeview
36 ms
event.gif
60 ms
event.jpg
39 ms
activeview
12 ms
query.js
42 ms
hospital_search_tab.gif
2139 ms
box_19_top-right.png
39 ms
ci.png
32 ms
event.gif
25 ms
hospital_search_contents_bg.gif
2143 ms
hospital_search_contents_foot.gif
2158 ms
hospital_search_inner_bg.gif
2163 ms
activeview
14 ms
activeview
14 ms
activeview
19 ms
hospital_search_inner_foot.gif
2248 ms
hospital_search_box1_input.gif
2232 ms
hospital_search_btn_tel.gif
2139 ms
hospital_search_btn_hospital.gif
2210 ms
feature_title.gif
2182 ms
arrow_green_right.gif
2196 ms
home_what_bg.gif
2575 ms
side_box_bg.gif
2231 ms
side_box_head.gif
2117 ms
cap
27 ms
ca
16 ms
ca
23 ms
ca
20 ms
side_box_foot.gif
2179 ms
h5_pagetitle.gif
2197 ms
footer_bg.gif
2192 ms
footer_upcome_bg.gif
2305 ms
footer_upcome.gif
2274 ms
arrow_white_dot_right.gif
2239 ms
footer_sep.gif
2214 ms
header_btn_login_over.gif
2191 ms
header_btn_regist_over.gif
2220 ms
globalnav_top_over.gif
2304 ms
globalnav_new_over.gif
2278 ms
globalnav_regist_over.gif
2249 ms
areamap_hokkaido_over.gif
2209 ms
areamap_aomori_over.gif
2201 ms
get
6 ms
get
6 ms
areamap_iwate_over.gif
2161 ms
areamap_miyagi_over.gif
2176 ms
areamap_akita_over.gif
2203 ms
areamap_yamagata_over.gif
2227 ms
areamap_fukushima_over.gif
2170 ms
areamap_ibaragi_over.gif
2185 ms
areamap_tochigi_over.gif
2181 ms
areamap_gunma_over.gif
2115 ms
areamap_saitama_over.gif
2210 ms
areamap_chiba_over.gif
2252 ms
areamap_tokyo_over.gif
2167 ms
areamap_kanagawa_over.gif
2177 ms
areamap_niigata_over.gif
2191 ms
areamap_toyama_over.gif
2108 ms
areamap_ishikawa_over.gif
2185 ms
areamap_fukui_over.gif
2266 ms
areamap_yamanashi_over.gif
2164 ms
areamap_nagano_over.gif
2137 ms
areamap_gifu_over.gif
2175 ms
areamap_shizuoka_over.gif
2081 ms
areamap_aichi_over.gif
2119 ms
areamap_mie_over.gif
2172 ms
areamap_osaka_over.gif
2133 ms
areamap_hyogo_over.gif
2142 ms
areamap_kyoto_over.gif
2149 ms
areamap_shiga_over.gif
2065 ms
areamap_nara_over.gif
2126 ms
areamap_wakayama_over.gif
2156 ms
areamap_tottori_over.gif
2175 ms
areamap_shimane_over.gif
2161 ms
areamap_okayama_over.gif
2163 ms
areamap_hiroshima_over.gif
2069 ms
areamap_yamaguchi_over.gif
2136 ms
areamap_tokushima_over.gif
2160 ms
areamap_kagawa_over.gif
2143 ms
areamap_ehime_over.gif
2175 ms
areamap_kochi_over.gif
2187 ms
areamap_fukuoka_over.gif
2069 ms
areamap_saga_over.gif
2111 ms
areamap_nagasaki_over.gif
2164 ms
areamap_kumamoto_over.gif
2162 ms
areamap_oita_over.gif
2181 ms
areamap_miyazaki_over.gif
2143 ms
areamap_kagoshima_over.gif
2098 ms
areamap_okinawa_over.gif
2113 ms
tusinbo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
<object> elements do not have alternate text
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tusinbo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
tusinbo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Tusinbo.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 Tusinbo.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.
tusinbo.com
Open Graph description is not detected on the main page of Tusinbo. 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: