7.3 sec in total
548 ms
6.5 sec
256 ms
Visit dentalx.jp now to see the best up-to-date Dental X content and also check out these interesting facts you probably never knew about dentalx.jp
株式会社プラネットは、歯科の患者データを一元管理し、患者さん目線で作られた診断書や資料が提供できる、Mac専用ソフトウェア「Dental X[R](デンタルテン アール)」を制作・販売しています。歯科医院のコミュニケーションツールとしてご活用下さい。
Visit dentalx.jpWe analyzed Dentalx.jp page load time and found that the first response time was 548 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dentalx.jp performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value22.4 s
0/100
25%
Value19.0 s
0/100
10%
Value1,960 ms
8/100
30%
Value0.198
62/100
15%
Value27.5 s
0/100
10%
548 ms
1029 ms
47 ms
822 ms
60 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 46% of them (32 requests) were addressed to the original Dentalx.jp, 13% (9 requests) were made to App.chatplus.jp and 10% (7 requests) were made to Appimg.chatplus.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Dentalx.jp.
Page size can be reduced by 1.0 MB (24%)
4.3 MB
3.2 MB
In fact, the total size of Dentalx.jp main page is 4.3 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 47.1 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 20.3 kB, which is 35% 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 47.1 kB or 82% of the original size.
Potential reduce by 25.9 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. Dental X images are well optimized though.
Potential reduce by 869.0 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 869.0 kB or 62% of the original size.
Potential reduce by 80.6 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. Dentalx.jp needs all CSS files to be minified and compressed as it can save up to 80.6 kB or 62% of the original size.
Number of requests can be reduced by 30 (46%)
65
35
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dental X. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
dentalx.jp
548 ms
dentalx.jp
1029 ms
gtm.js
47 ms
styles.css
822 ms
js
60 ms
analytics.js
17 ms
collect
13 ms
collect
118 ms
plugin.js
2678 ms
script.js
870 ms
fbevents.js
59 ms
logo_w.svg
191 ms
arw-primary.svg
380 ms
mission.png
468 ms
docs-banner.png
648 ms
request04.png
495 ms
dentale-top-banner-240215.png
1503 ms
hara-movie.png
1136 ms
opensp-b.png
1337 ms
icon-02.jpg
1153 ms
icon-01.jpg
2587 ms
icon-03.jpg
1516 ms
icon-04.jpg
1646 ms
icon-05.jpg
1686 ms
icon-06.jpg
1880 ms
icon-07.jpg
1707 ms
icon-08.jpg
2213 ms
icon-09.jpg
2251 ms
icon-13.jpg
1899 ms
icon-10.jpg
2280 ms
icon-11.jpg
2089 ms
cafe.png
2302 ms
ISO_IEC27001.jpg
2280 ms
isms_ac_iso27001_color.jpg
2325 ms
logo_f.svg
2423 ms
www.dentalx.jp
712 ms
www.dentalx.jp
900 ms
widgets.js
57 ms
sdk.js
12 ms
cp.js
688 ms
22552979.js
135 ms
iframe_api
79 ms
sdk.js
33 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
44 ms
98 ms
settings
113 ms
www-widgetapi.js
12 ms
banner.js
85 ms
collectedforms.js
73 ms
web-interactives-embed.js
87 ms
fb.js
56 ms
22552979.js
94 ms
print.css
198 ms
chatplusscript.min.js
172 ms
jqueryc.min.js
32 ms
riot%2Bcompiler_2.min.js
24 ms
underscorec.min.js
31 ms
c
549 ms
json
629 ms
a34e44b6_5
202 ms
all-cp.min.css
2 ms
chat_common.min.css
168 ms
chat.min.css
338 ms
design.1664872994.css
692 ms
custom.1618387465.css
686 ms
onerror.min.js
344 ms
visitor-client.min.js
666 ms
slick.min.js
7 ms
startup
580 ms
dentalx.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
dentalx.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
dentalx.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dentalx.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 Dentalx.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.
dentalx.jp
Open Graph data is detected on the main page of Dental X. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: