4.5 sec in total
308 ms
3.9 sec
280 ms
Welcome to medpeer.co.jp homepage info - get ready to check Medpeer best content for Japan right away, or after learning these important things about medpeer.co.jp
メドピア株式会社は「Supporting Doctors, Helping Patients」をミッションに、医師プラットフォーム『MedPeer』を基盤とした医師向け臨床支援サービスや一般向け健康増進・予防サービスを提供しています。
Visit medpeer.co.jpWe analyzed Medpeer.co.jp page load time and found that the first response time was 308 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
medpeer.co.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value11.2 s
0/100
25%
Value6.4 s
40/100
10%
Value920 ms
30/100
30%
Value0.393
26/100
15%
Value11.3 s
19/100
10%
308 ms
900 ms
59 ms
151 ms
298 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 57% of them (67 requests) were addressed to the original Medpeer.co.jp, 21% (25 requests) were made to Static.xx.fbcdn.net and 13% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Medpeer.co.jp.
Page size can be reduced by 499.8 kB (54%)
930.1 kB
430.3 kB
In fact, the total size of Medpeer.co.jp main page is 930.1 kB. 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 591.3 kB which makes up the majority of the site volume.
Potential reduce by 24.0 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 3.6 kB, which is 11% 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 24.0 kB or 75% of the original size.
Potential reduce by 260.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. Obviously, Medpeer needs image optimization as it can save up to 260.9 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 138.7 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 138.7 kB or 64% of the original size.
Potential reduce by 76.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. Medpeer.co.jp needs all CSS files to be minified and compressed as it can save up to 76.2 kB or 84% of the original size.
Number of requests can be reduced by 42 (36%)
116
74
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medpeer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
medpeer.co.jp
308 ms
medpeer.co.jp
900 ms
css
59 ms
kube.css
151 ms
global.css
298 ms
top.css
463 ms
perfect-scrollbar.css
591 ms
animation.css
593 ms
modernizr.js
594 ms
jquery-1.9.0.min.js
1172 ms
breakpoints.js
614 ms
responsive-nav.js
806 ms
jquery.scrollFade.js
740 ms
jquery.easing.1.3.js
740 ms
global.js
740 ms
jquery.mousewheel.js
741 ms
perfect-scrollbar.js
1030 ms
main.js
885 ms
imagesloaded.pkgd.js
1030 ms
animation.js
889 ms
bg.png
348 ms
logo.png
655 ms
txt1.png
445 ms
txt2.png
493 ms
txt3-1.png
727 ms
txt3-2.png
728 ms
txt4.png
746 ms
txt5-1.png
786 ms
txt5-2.png
721 ms
btn1.png
731 ms
btn2.png
868 ms
btn3.png
873 ms
txt1_sp.png
874 ms
txt2_sp.png
1105 ms
txt3_sp.png
1218 ms
txt4_sp.png
1219 ms
txt5_sp.png
1219 ms
img_aside01.jpg
1220 ms
img_aside02.jpg
1104 ms
img_aside03.jpg
1349 ms
img_aside04.jpg
1286 ms
img_blog.jpg
1286 ms
img_site.jpg
1287 ms
img_recruit.png
1311 ms
gtm.js
97 ms
gnav01.png
1301 ms
sdk.js
125 ms
gnav02.png
1323 ms
analytics.js
90 ms
gnav03.png
1228 ms
gnav04.png
1228 ms
gnav05.png
1311 ms
gnav06.png
1315 ms
179 ms
linkid.js
12 ms
icon_contact.png
1279 ms
xd_arbiter.php
123 ms
collect
15 ms
step1.png
1229 ms
step2.png
1225 ms
step3.png
1179 ms
step4.png
1167 ms
step5.png
1172 ms
icon_arrow01.png
1200 ms
bg_title.png
1172 ms
like_box.php
215 ms
like.php
180 ms
bottomAd.html
1020 ms
icon_arrow06.png
1028 ms
hamburger.gif
1026 ms
top_animation1.gif
1318 ms
step_line_gray.png
1065 ms
vpc6VNjRPXV.js
153 ms
LVx-xkvaJ0b.png
95 ms
0liJMUxv-Fj.css
92 ms
_er37g1kpMx.css
94 ms
KPiL0RlbWpg.css
98 ms
_rx8naC75Dy.js
127 ms
x5F9OMjKyLw.js
152 ms
ICDbTSzjQEg.js
108 ms
TTCre3391I0.js
115 ms
C-h3nYPqETO.js
151 ms
rFmE1g6Dkoz.js
182 ms
7cm7D75Y0Sf.js
175 ms
oRoBXlHCpEy.js
173 ms
336JejShbZp.js
173 ms
sj-JwAJi4AH.js
177 ms
DKRU1bYTkTw.js
174 ms
ZNPAadQNc33.js
175 ms
W0OV23mIOyO.js
177 ms
36TdwhIHusi.js
177 ms
vpc6VNjRPXV.js
296 ms
11140327_851779051524628_574387820747393318_n.jpg
196 ms
1487348_607165182652684_696291091_n.jpg
214 ms
1907582_709226879178238_1347901110937113825_n.jpg
220 ms
281353_106039826161896_8363863_n.jpg
235 ms
10256560_1508743299402427_1141233758755516095_n.jpg
236 ms
154777_437212963012581_2007228333_n.jpg
239 ms
1175208_458195564288667_934420589_n.jpg
240 ms
149071_1227676869637_6802181_n.jpg
239 ms
536548_265860113511902_1782043877_n.jpg
238 ms
10599235_806919109351107_6928404437823716308_n.jpg
251 ms
154218_376235842457287_1330029697_n.jpg
252 ms
10354686_10150004552801856_220367501106153455_n.jpg
253 ms
10157379_308855565987123_2552925395233457418_n.jpg
256 ms
12096591_1021470374551436_8484015252827149553_n.jpg
254 ms
263394_115488741992346_9999736_n.jpg
256 ms
wL6VQj7Ab77.png
117 ms
s7jcwEQH7Sx.png
186 ms
pUFVdPjIRct.png
72 ms
I6-MnjEovm5.js
19 ms
vlXaquuXMrr.js
20 ms
logo.png
149 ms
txt_circle_01.png
152 ms
txt_circle_02.png
148 ms
txt_circle_03.png
219 ms
arrow.png
263 ms
nr-632.min.js
61 ms
medpeer.co.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
medpeer.co.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
medpeer.co.jp 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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Medpeer.co.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 Medpeer.co.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.
medpeer.co.jp
Open Graph data is detected on the main page of Medpeer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: