7 sec in total
615 ms
5.4 sec
986 ms
Click here to check amazing Doclabo content for Japan. Otherwise, check out these important facts you probably never knew about doclabo.jp
歯医者の選び方や歯科にまつわる知識を学べて、検索できるサイト「どくらぼ」は全国の歯医者さんを掲載中です。それぞれの歯医者の口コミや評判をみて、あなたに合った歯医者さんを探すことができます!
Visit doclabo.jpWe analyzed Doclabo.jp page load time and found that the first response time was 615 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
doclabo.jp performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value5.6 s
18/100
25%
Value16.4 s
0/100
10%
Value150 ms
95/100
30%
Value0.021
100/100
15%
Value8.3 s
40/100
10%
615 ms
169 ms
319 ms
322 ms
321 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 82% of them (121 requests) were addressed to the original Doclabo.jp, 3% (5 requests) were made to Pagead2.googlesyndication.com and 3% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Doclabo.jp.
Page size can be reduced by 2.3 MB (51%)
4.5 MB
2.2 MB
In fact, the total size of Doclabo.jp main page is 4.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. 65% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 68.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 24.9 kB, which is 30% 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 68.4 kB or 82% of the original size.
Potential reduce by 1.9 MB
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. Obviously, Doclabo needs image optimization as it can save up to 1.9 MB or 49% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 281.8 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 281.8 kB or 60% of the original size.
Potential reduce by 35.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. Doclabo.jp needs all CSS files to be minified and compressed as it can save up to 35.2 kB or 82% of the original size.
Number of requests can be reduced by 50 (34%)
146
96
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doclabo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
doclabo.jp
615 ms
reset.css
169 ms
util.css
319 ms
main.css
322 ms
top.css
321 ms
flexslider.css
324 ms
accessibility.css
334 ms
eagingAD.css
344 ms
jquery.js
671 ms
adsbygoogle.js
6 ms
util.js
472 ms
main.js
475 ms
heightLine.js
479 ms
init.js
496 ms
eagingAD.js
511 ms
jquery.bxslider.js
633 ms
chase.js
631 ms
analytics.js
33 ms
gpt.js
31 ms
space.gif
229 ms
logo.gif
170 ms
cttl.gif
169 ms
bt-search.gif
171 ms
snav-station_o.gif
228 ms
snav-address.gif
171 ms
bg-map.gif
323 ms
snav-station.gif
324 ms
snav-address_o.gif
342 ms
snav-area.gif
341 ms
snav-map_o.gif
387 ms
ttl-01.gif
408 ms
img-01.jpg
472 ms
img-02.jpg
473 ms
img-03.jpg
489 ms
img-04.jpg
486 ms
ttl-02.gif
552 ms
bt-01.gif
562 ms
bt-02.gif
628 ms
bt-03.gif
633 ms
bt-04.gif
684 ms
bt-05.gif
685 ms
bt-06.gif
745 ms
bt-07.gif
746 ms
bt-08.gif
780 ms
bt-09.gif
783 ms
bt-10.gif
799 ms
bt-11.gif
843 ms
bt-12.gif
881 ms
bt-13.gif
901 ms
bt-14.gif
932 ms
bt-15.gif
934 ms
bt-16.gif
955 ms
ttl-03.gif
1002 ms
bt-all.gif
1046 ms
sdk.js
219 ms
thumb240_180_35cd0b069e7d42f5b743b4fe0676522d.jpeg
1054 ms
pubads_impl_81.js
30 ms
collect
214 ms
collect
213 ms
ads
485 ms
container.html
83 ms
ca-pub-2063017709356826.js
170 ms
zrt_lookup.html
179 ms
show_ads_impl.js
68 ms
thumb240_180_64cfe596c0649c48201e13816960d9f5.jpeg
927 ms
thumb240_180_acf3edec7d32430a8a5ed248efb6089a.png
1379 ms
thumb240_180_f50a13739f4791ab37750ff3680523d7.jpeg
951 ms
plusone.js
209 ms
thumb240_180_75cea1c28da23acfefcbf333cd6838b5.jpeg
962 ms
thumb240_180_98a547f8a119b8f3fd63607fad323e2d.jpeg
995 ms
thumb240_180_189ea854f723627e7d7db334d513ebe0.jpeg
1024 ms
ads
311 ms
osd.js
25 ms
166 ms
xd_arbiter.php
159 ms
xd_arbiter.php
317 ms
thumb240_180_066bec1b9f30947c1852ccaa770b6b1d.jpeg
926 ms
thumb240_180_dea73aa08b695b061512883c120dbea2.jpeg
956 ms
thumb240_180_5c3a0b72c0c075cd068f9f5e91f91ef1.jpeg
988 ms
thumb240_180_6aae580930787c1cc7929ddc33fd0f49.jpeg
1046 ms
thumb240_180_34395bed3d785085390ee11eb1ac867a.jpeg
1017 ms
cb=gapi.loaded_0
25 ms
thumb240_180_2bd9cccee353044e2eea6a2655c2704c.jpeg
1012 ms
thumb240_180_75a2e40e87826093b6e129b1651df315.jpeg
963 ms
thumb240_180_4720f801684200194d87e1aae2c7d1d7.jpeg
1017 ms
thumb240_180_cb2f85a64fce9e812ba874f51359167c.jpeg
1069 ms
thumb240_180_247914cc3aefaa42442d7329dbafc33a.jpeg
1066 ms
thumb240_180_22ff723d739e9b07bbe1f6476846e50e.jpeg
1041 ms
bt-all.gif
1031 ms
5171746271700867932
70 ms
abg.js
69 ms
m_js_controller.js
80 ms
googlelogo_color_112x36dp.png
117 ms
ttl-01.gif
1017 ms
DSC_0078.jpg
1368 ms
s
34 ms
x_button_blue2.png
36 ms
%EF%BC%92.png
3180 ms
5e92de3a9f7339ae46559f48bd0315b6.jpeg
1534 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
shika-lab_char_250_250.png
1005 ms
ttl-03.gif
1016 ms
thumb120_90_75cea1c28da23acfefcbf333cd6838b5.jpeg
1024 ms
blt-1.png
1127 ms
1d921d40-9dc5-11e3-8b94-0a191cb3e685.png
3263 ms
blt-2.png
1120 ms
thumb120_90_934c99e9035e2476d27822537a32b46a.jpeg
1184 ms
blt-3.png
1223 ms
956dbc50-d9bd-11e3-bef9-060a10b774b3.thumb.jpg
1219 ms
blt-4.png
1288 ms
thumb120_90_cbab12453d6d6e9148f1a79ffde650c3.jpeg
1328 ms
blt-5.png
1301 ms
ftr-logo.gif
1336 ms
thumb80_60_35cd0b069e7d42f5b743b4fe0676522d.jpeg
1309 ms
thumb80_60_64cfe596c0649c48201e13816960d9f5.jpeg
1357 ms
thumb80_60_acf3edec7d32430a8a5ed248efb6089a.png
1344 ms
pagetop.png
1377 ms
bg-mainvisual.gif
1336 ms
bg-fttl.gif
1363 ms
bg-frm.gif
1368 ms
bt-search_ov.gif
1425 ms
bg-snav.gif
1395 ms
bg-sbtn.gif
1383 ms
bg-box1.gif
1365 ms
bg-box2.gif
1439 ms
bg-box1.gif
1453 ms
snav-address_ov.gif
1430 ms
snav-station_ov.gif
1383 ms
snav-area_ov.gif
1462 ms
bt-01_ov.gif
1500 ms
bt-02_ov.gif
1480 ms
bt-03_ov.gif
1495 ms
bt-04_ov.gif
1528 ms
bt-05_ov.gif
1469 ms
bt-06_ov.gif
1462 ms
bt-07_ov.gif
1442 ms
bt-08_ov.gif
1420 ms
bt-09_ov.gif
1422 ms
bt-10_ov.gif
1376 ms
bt-11_ov.gif
1340 ms
bt-12_ov.gif
1362 ms
bt-13_ov.gif
1375 ms
bt-14_ov.gif
1335 ms
bt-15_ov.gif
1342 ms
bt-16_ov.gif
1361 ms
bt-all_ov.gif
1376 ms
pagetop_ov.png
1340 ms
doclabo.jp 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 IDs are not unique
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
Links do not have a discernible name
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.
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.
doclabo.jp 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
doclabo.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doclabo.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 Doclabo.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.
doclabo.jp
Open Graph description is not detected on the main page of Doclabo. 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: