Page load speed analysis

  • 49/100

    Normal result
  • 5

    Successful tests
  • 3

    Failed tests
  • First response

    504 ms

  • Resources loaded

    7.8 sec

  • Page rendered

    2 sec

  • Total page load time

    10.3 sec

Visit now to see the best up-to-date Medipartner content for Japan and also check out these interesting facts you probably never knew about

We analyzed page load time and found that the first response time was 504 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Page optimization

  • HTML 36.1 kB
    Images 982.5 kB
    Javascripts 218.2 kB
    CSS 23.6 kB

    In fact, the total size of main page is 1.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. 15% of websites need less resources to load. Images take 982.5 kB which makes up the majority of the site volume.

    • Original 36.1 kB
    • After minification 31.1 kB
    • After compression 7.4 kB

    HTML optimization

    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 5.0 kB, which is 14% 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 28.7 kB or 79% of the original size.

    • Original 982.5 kB
    • After optimization 943.5 kB

    Image optimization

    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. Medipartner images are well optimized though.

    • Original 218.2 kB
    • After minification 217.3 kB
    • After compression 72.8 kB

    JavaScript optimization

    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 145.4 kB or 67% of the original size.

    • Original 23.6 kB
    • After minification 18.4 kB
    • After compression 5.8 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 75% of the original size.

Network requests diagram

  • layout.css
  • main2.css
  • hm.css
  • mn.css
  • mm.css
  • slick.css
  • jquery.min.js
  • slick.min.js
  • add.js
  • medi_login.js
  • jquery.jscrollpane.css
  • jquery.jscrollpane.min.js
  • si.js
  • analytics.js
  • bg.jpg
  • logo_mp.png
  • tit_loginmaster.png
  • img_login_header.jpg
  • tit_loginaff.png
  • bg_nav.jpg
  • bg_navmain.jpg
  • bg_globallist.png
  • btm_splogin_global.jpg
  • btm_sp_login_close.png
  • bg_topmainimg.jpg
  • bg_mainimg.jpg
  • btm_mainmaster.png
  • btm_mainaff.png
  • top-main.png
  • icon_01.jpg
  • icon_02.jpg
  • icon_03.jpg
  • icon_04.jpg
  • icon_06.jpg
  • icon_07.jpg
  • icon_08.jpg
  • icon_09.png
  • img_cm15.jpg
  • img_cm18.jpg
  • img_cm13.jpg
  • img_cm16.jpg
  • img_cm11.jpg
  • img_cm14.jpg
  • img_cm17.jpg
  • img_cm12.jpg
  • img_officelogo07.jpg
  • img_officelogo08.jpg
  • img_officelogo09.jpg
  • img_officelogo10.jpg
  • img_officelogo11.jpg
  • slick.woff
  • img_officelogo12.jpg
  • img_officelogo13.jpg
  • collect
  • 21000521_03_100_JP.png
  • smarticon
  • pta.js
  • p-mark_txt.png
  • gt_txt.png
  • ajax-loader.gif
  • bg_footermenu.jpg
  • 712e64c8.js
  • pn

Our browser made a total of 65 requests to load all elements on the main page. We found that 89% of them (58 requests) were addressed to the original, 3% (2 requests) were made to and 3% (2 requests) were made to The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain

Additional info on


The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Medipartner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.











Possible request optimization













Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address uses IP addresses which are currently shared with 16 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 58
NS 60
NS 60
NS 60
NS 60

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 99.6% of all visits is Japan. It lies approximately 4840 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to Japan or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Medipartner. 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:

Language and encoding

Normal result


N/A  language flag


JA ja language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that 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.

Share this report in social media

Analyze another website