7.2 sec in total
512 ms
6.1 sec
534 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 512 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
haishasan.net performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value6.1 s
12/100
25%
Value11.9 s
4/100
10%
Value580 ms
51/100
30%
Value0
100/100
15%
Value10.6 s
23/100
10%
512 ms
1470 ms
678 ms
342 ms
513 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 72% of them (115 requests) were addressed to the original Haishasan.net, 4% (6 requests) were made to Tag.ladsp.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Haishasan.net.
Page size can be reduced by 194.6 kB (13%)
1.5 MB
1.3 MB
In fact, the total size of Haishasan.net main page is 1.5 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 42.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 8.6 kB, which is 16% 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 42.9 kB or 78% of the original size.
Potential reduce by 71.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. Haishasan images are well optimized though.
Potential reduce by 47.6 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 47.6 kB or 29% of the original size.
Potential reduce by 32.2 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.2 kB or 82% of the original size.
Number of requests can be reduced by 52 (34%)
151
99
The browser has sent 151 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 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
haishasan.net
512 ms
www.haishasan.net
1470 ms
haisha_top_new.css
678 ms
gmenu_dropdown.css
342 ms
common.css
513 ms
module.css
518 ms
index_new.css
715 ms
widgets.js
8 ms
dc.js
38 ms
widget.js
64 ms
lf.js
519 ms
jquery.min.js
50 ms
top_main_rotation_banner.js
678 ms
smartrollover.js
684 ms
AC_RunActiveContent.js
861 ms
analytics.js
78 ms
fbds.js
99 ms
logo.gif
175 ms
btn_mypage.gif
178 ms
facebook.jpg
349 ms
twitter.jpg
335 ms
menu01_off.gif
179 ms
menu02_off.gif
187 ms
menu02_01.gif
343 ms
menu02_02.gif
351 ms
menu02_03.gif
352 ms
menu02_04.gif
355 ms
menu02_05.gif
501 ms
menu02_06.gif
510 ms
menu03_off.gif
517 ms
menu04_off.gif
527 ms
menu04_01.gif
522 ms
menu04_02.gif
525 ms
menu04_03.gif
668 ms
menu04_04.gif
677 ms
menu04_05.gif
688 ms
menu05_off.gif
693 ms
menu05_01.gif
692 ms
menu05_03.gif
698 ms
menu06_off.gif
834 ms
menu07_off.gif
844 ms
menu07_01.gif
852 ms
menu07_02.gif
876 ms
bg_kv.gif
876 ms
kv_04.jpg
2037 ms
kv_01.jpg
2206 ms
kv_trivia.jpg
1712 ms
kv_calendar.jpg
1660 ms
kv_btn_04.gif
1401 ms
kv_btn_01.gif
1044 ms
kv_btn_trivia.gif
1240 ms
kv_btn_calendar.gif
1371 ms
q
176 ms
ga.js
28 ms
conversion.js
25 ms
pixel.js
366 ms
pixel.js
25 ms
25 ms
bg_main_02.gif
1616 ms
collect
25 ms
22 ms
26 ms
20 ms
new_rumor.gif
1493 ms
rumor_contribution.gif
1661 ms
rumor_watch.gif
1704 ms
bg_main_03.gif
1699 ms
flash._V1363208047_.js
17 ms
__utm.gif
18 ms
36 ms
40 ms
clinic_search.gif
1582 ms
clinic_serach_map.gif
1670 ms
clinic_search_button.gif
1706 ms
bg_main_bottom.gif
1705 ms
bg_main.gif
1746 ms
title_tooth-read.gif
1830 ms
34 ms
img_tooth-decay.gif
1718 ms
img_periodontal-disease.gif
1719 ms
title_tooth-pain.gif
1711 ms
img_tooth-pain.gif
1745 ms
title_basic-knowledge.gif
1828 ms
img_basic-knowledge.gif
1850 ms
title_haisha-qa.gif
1727 ms
img_haisha-qa.gif
1720 ms
title_baby-teeth-care.gif
1714 ms
img_baby-teeth-care.gif
1747 ms
title_baby-teeth.gif
1827 ms
img_baby-teeth.gif
1847 ms
pixel
155 ms
title_tooth-begin.gif
1736 ms
img_tooth-begin.gif
1727 ms
title_tooth-health.gif
1721 ms
pixel
24 ms
Pug
18 ms
sync.ad-stir.com
297 ms
sync
7 ms
sync
426 ms
is
368 ms
pixel
153 ms
img_tooth-health.gif
1736 ms
sd
5 ms
title_tooth-encyclopedia.gif
1811 ms
286 ms
pixel
186 ms
img_tooth-encyclopedia.gif
1669 ms
xrost
154 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
26 ms
adfunnel
154 ms
title_tooth-glossary.gif
1500 ms
syndication
106 ms
306617547753668609
245 ms
img_tooth-glossary.gif
1340 ms
00053.jpg
1754 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
4023e51e9a03cbd8e9425da2c14d3ccc_normal.jpeg
123 ms
CM1t7OHUcAANzpL.png:small
146 ms
CKFYO-VVEAYzGoH.png:small
123 ms
00052.jpg
1140 ms
00051.jpg
1203 ms
00050.jpg
1264 ms
00049.jpg
1765 ms
00048.jpg
1321 ms
jot
28 ms
00047.jpg
1304 ms
00046.jpg
1359 ms
00045.jpg
1221 ms
00044.jpg
1327 ms
title_update-info.gif
1320 ms
icon_05.gif
1305 ms
icon_new.gif
1299 ms
icon_arrow.gif
1315 ms
title_clinic-info.gif
1324 ms
sp_banner_01.gif
1332 ms
sp_banner_02.gif
1505 ms
sp_banner_03.gif
1354 ms
sab_tit_trivia.jpg
1354 ms
trivia.jpg
1388 ms
sab_tit_01.gif
1324 ms
ill_topics_03.gif
1333 ms
ill_topics_02.gif
1364 ms
bn.png
1361 ms
shizui.gif
1426 ms
banner01.gif
1410 ms
banner02.gif
1360 ms
ask_banner.gif
1351 ms
banner_4hc_216x62.gif
1369 ms
fb_banner.gif
1364 ms
footer_pageup.gif
1434 ms
bg_sab_bottom.gif
1404 ms
bg_sab.gif
1361 ms
bolg_title_216.gif
1356 ms
blog_side_dot_216.gif
1362 ms
blog_bottom_216.gif
1369 ms
bg_footer.gif
1369 ms
kv_btn_03_active.gif
1326 ms
3 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
Issues were logged in the Issues panel in Chrome Devtools
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: