12.6 sec in total
541 ms
11.1 sec
893 ms
Welcome to haishasan.net homepage info - get ready to check Haishasan best content for Japan right away, or after learning these important things about haishasan.net
全国6万件の歯科医院検索なら歯医者さんネット。歯医者さんネットは全国の歯科医院検索から虫歯・歯周病予防など歯の健康情報がわかるポータルサイトです。歯やお口のトラブルやお子様の歯の知識にお役立てください。
Visit haishasan.netWe analyzed Haishasan.net page load time and found that the first response time was 541 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
haishasan.net performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value11.3 s
0/100
25%
Value11.7 s
4/100
10%
Value460 ms
62/100
30%
Value0
100/100
15%
Value15.2 s
7/100
10%
541 ms
531 ms
2618 ms
1001 ms
519 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 72% of them (108 requests) were addressed to the original Haishasan.net, 2% (3 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Haishasan.net.
Page size can be reduced by 164.1 kB (5%)
3.1 MB
2.9 MB
In fact, the total size of Haishasan.net main page is 3.1 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. 55% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 44.4 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 8.0 kB, which is 14% 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 44.4 kB or 77% of the original size.
Potential reduce by 55.0 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. Haishasan images are well optimized though.
Potential reduce by 32.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 32.2 kB or 25% of the original size.
Potential reduce by 32.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. Haishasan.net needs all CSS files to be minified and compressed as it can save up to 32.5 kB or 82% of the original size.
Number of requests can be reduced by 44 (31%)
142
98
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haishasan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
haishasan.net
541 ms
www.haishasan.net
531 ms
www.haishasan.net
2618 ms
haisha_top_new.css
1001 ms
gmenu_dropdown.css
519 ms
common.css
695 ms
module.css
869 ms
index_new.css
895 ms
widgets.js
91 ms
dc.js
20 ms
widget.js
6 ms
jquery.min.js
27 ms
top_main_rotation_banner.js
693 ms
smartrollover.js
867 ms
js
62 ms
gtm.js
163 ms
fbds.js
162 ms
logo.gif
447 ms
facebook.jpg
441 ms
twitter.jpg
453 ms
menu01_off.gif
289 ms
menu02_off.gif
286 ms
menu02_01.gif
458 ms
menu02_02.gif
466 ms
menu02_03.gif
608 ms
menu02_04.gif
620 ms
menu02_05.gif
626 ms
menu02_06.gif
632 ms
menu04_off.gif
645 ms
menu04_01.gif
774 ms
menu04_02.gif
793 ms
menu04_03.gif
798 ms
menu04_04.gif
805 ms
menu04_05.gif
825 ms
menu05_off.gif
865 ms
menu05_01.gif
941 ms
menu05_03.gif
967 ms
menu06_off.gif
972 ms
menu07_off.gif
979 ms
menu07_01.gif
1003 ms
menu07_02.gif
1038 ms
bg_kv.gif
1110 ms
kv_calendar.jpg
2035 ms
kv_04.jpg
2247 ms
kv_01.jpg
2609 ms
kv_trivia.jpg
2301 ms
kv_btn_calendar.gif
1212 ms
kv_btn_04.gif
1445 ms
kv_btn_01.gif
1389 ms
kv_btn_trivia.gif
1562 ms
bg_main_02.gif
1613 ms
title_tooth-decat_periodontal-read.gif
1668 ms
analytics.js
29 ms
destination
46 ms
collect
47 ms
collect
13 ms
img_tooth-decay_s.gif
1502 ms
img_periodontal-disease_s.gif
1655 ms
ga-audiences
33 ms
bg_main_03.gif
1572 ms
clinic_search.gif
1717 ms
clinic_serach_map.gif
1752 ms
clinic_search_button.gif
1767 ms
bg_main_bottom.gif
1870 ms
bg_main.gif
1780 ms
title_tooth-read.gif
1782 ms
title_tooth-pain.gif
1798 ms
img_tooth-pain.gif
1857 ms
title_basic-knowledge.gif
1865 ms
q
6 ms
conversion.js
89 ms
pixel.js
690 ms
35 ms
img_basic-knowledge.gif
1868 ms
tag.js
54 ms
33 ms
18 ms
title_haisha-qa.gif
1803 ms
16 ms
img_haisha-qa.gif
1806 ms
title_baby-teeth-care.gif
1868 ms
24 ms
img_baby-teeth-care.gif
1882 ms
title_baby-teeth.gif
1902 ms
19 ms
img_baby-teeth.gif
1889 ms
title_tooth-begin.gif
1830 ms
img_tooth-begin.gif
1823 ms
title_tooth-health.gif
1874 ms
img_tooth-health.gif
1888 ms
title_tooth-encyclopedia.gif
1891 ms
img_tooth-encyclopedia.gif
1892 ms
title_tooth-glossary.gif
1834 ms
img_tooth-glossary.gif
1757 ms
00282.jpg
2226 ms
00281.jpg
3073 ms
00280.jpg
2442 ms
pixel
171 ms
00279.jpg
3642 ms
iframe
212 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
66 ms
00278.jpg
6353 ms
00277.jpg
3377 ms
settings
94 ms
00276.jpg
2773 ms
pixel
116 ms
Pug
91 ms
hs
702 ms
sync.ad-stir.com
695 ms
tap.php
115 ms
sync
818 ms
117 ms
cookiesync
754 ms
cs
768 ms
sync.ad
273 ms
cs
662 ms
sync
283 ms
sync
110 ms
00275.jpg
2758 ms
00274.jpg
3196 ms
174 ms
sd
10 ms
sync
19 ms
bounce
26 ms
00273.jpg
3218 ms
new_rumor.gif
2882 ms
rumor_watch.gif
3035 ms
title_update-info.gif
3095 ms
icon_05.gif
3103 ms
icon_arrow.gif
3095 ms
title_clinic-info.gif
3040 ms
sp_banner_01.gif
3136 ms
sp_banner_02.gif
3159 ms
sp_banner_03.gif
3108 ms
kyousei_banner.png
3282 ms
kyousei_plus_banner.png
3264 ms
implant_banner.png
3160 ms
implant_plus_banner.png
3340 ms
shinbi_banner.png
3362 ms
shizui.gif
3250 ms
banner01.gif
3280 ms
banner02.gif
3275 ms
ask_banner.gif
3342 ms
banner_4hc_216x62.png
3369 ms
fb_banner.gif
3348 ms
bnr_dtdw_200_90.jpg
3493 ms
footer_pageup.gif
3326 ms
bg_sab_bottom.gif
3374 ms
bg_sab.gif
3378 ms
bg_footer.gif
3375 ms
kv_btn_02_active.gif
3409 ms
haishasan.net accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
haishasan.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
haishasan.net 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
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haishasan.net 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 Haishasan.net main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
haishasan.net
Open Graph data is detected on the main page of Haishasan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: