5.7 sec in total
823 ms
4.5 sec
313 ms
Click here to check amazing Fdoc content for Japan. Otherwise, check out these important facts you probably never knew about fdoc.jp
全国の医療機関でネット受付予約・検索するならEPARKクリニック・病院。土日や19時以降診療、電話診療/オンライン診療などの条件検索やユーザーの口コミ、写真をもとに目的に合ったクリニック・病院の情報を検索できます。
Visit fdoc.jpWe analyzed Fdoc.jp page load time and found that the first response time was 823 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fdoc.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.3 s
22/100
25%
Value9.7 s
11/100
10%
Value600 ms
49/100
30%
Value0.069
96/100
15%
Value13.2 s
12/100
10%
823 ms
1032 ms
1133 ms
547 ms
548 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 55% of them (38 requests) were addressed to the original Fdoc.jp, 20% (14 requests) were made to Web.xaas.jp and 7% (5 requests) were made to D229s2sntbxd5j.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fdoc.jp.
Page size can be reduced by 763.3 kB (37%)
2.0 MB
1.3 MB
In fact, the total size of Fdoc.jp main page is 2.0 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.1 MB which makes up the majority of the site volume.
Potential reduce by 28.6 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.6 kB or 74% of the original size.
Potential reduce by 39.5 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. Fdoc images are well optimized though.
Potential reduce by 409.5 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 409.5 kB or 71% of the original size.
Potential reduce by 285.7 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. Fdoc.jp needs all CSS files to be minified and compressed as it can save up to 285.7 kB or 84% of the original size.
Number of requests can be reduced by 33 (49%)
67
34
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fdoc. 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 4 to 1 for CSS and as a result speed up the page load time.
fdoc.jp
823 ms
A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css
1032 ms
jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js
1133 ms
ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js
547 ms
jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js
548 ms
mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js
555 ms
jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js
747 ms
treeview.js.pagespeed.jm.Ccxdh7coVu.js
740 ms
common_v2016.js.pagespeed.jm.6iGU-6_f5J.js
956 ms
prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js
928 ms
theme.css
584 ms
addStyle.css
405 ms
roundTable.js
754 ms
placeholder.js
605 ms
epark_portal_global_pc.css
15 ms
epark_portal_global_html.js
15 ms
epark_portal_global.js
1271 ms
satelliteLib-029da011d9a5806548398232eab8c5de37cba442.js
61 ms
sessionStorageCache.js.pagespeed.jm.sO8NkBNyTZ.js
921 ms
recommendViewClinic.js.pagespeed.jm.gPVvI1onCX.js
926 ms
body-back.png
607 ms
mainImage_hospital-search.png
792 ms
recipe_carousel.png
972 ms
mainImage_net-reserve.png
1127 ms
mainImage_sick-symptoms.png
1097 ms
fine_doctor_menber.png
1252 ms
recipe_banner.png
1257 ms
bg-symptoms-mainImage.png
1166 ms
bg-kininaru-mainImage.png
1369 ms
bg-president-column-mainImage.png
1491 ms
bg-worries-mainImage.png
1504 ms
analytics.js
18 ms
mbox.js
1459 ms
collect
24 ms
collect
55 ms
target.js
38 ms
ajax
8 ms
head-logo.png
388 ms
arrow-brown02.png
204 ms
head-nav_back.png
222 ms
head-nav_hospital-search.png
225 ms
head-nav_resv.png
220 ms
head-nav_special.png
219 ms
head-nav_medicine-search.png
410 ms
top-border.png
410 ms
top-icon_search.png
414 ms
map_all.png
614 ms
top-btn_station_gray.png
433 ms
top-btn_course.png
582 ms
top-btn_emergency.png
600 ms
form-icon-medicine-search.png
610 ms
top-icon_reserve.png
628 ms
top-btn_net.png
648 ms
top-icon_feature.png
780 ms
top-icon_medicine.png
777 ms
top-btn_medicine.png
798 ms
top-sicon_house.png
807 ms
footer-back.png
829 ms
s-code-contents-1083697477d5a8fde1e1e2cd1720ac06bcdf99e4.js
83 ms
loading_icon.gif
598 ms
eparkLoginCheck.js
454 ms
epark_portal_global_header.json
30 ms
epark_portal_global_footer.json
24 ms
space.gif
345 ms
navigation.png
996 ms
arrow-carousel.png
1013 ms
arrow.png
6 ms
s97640700403135
16 ms
standard
33 ms
fdoc.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
fdoc.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fdoc.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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fdoc.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fdoc.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.
fdoc.jp
Open Graph description is not detected on the main page of Fdoc. 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: