Tools & Wizards About Us
e-doc.xii.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-doc.xii.jp

さくらのレンタルサーバ

Page Load Speed

6.4 sec in total

First Response

2.2 sec

Resources Loaded

3.9 sec

Page Rendered

320 ms

e-doc.xii.jp screenshot

About Website

Visit e-doc.xii.jp now to see the best up-to-date E Doc Xii content for Japan and also check out these interesting facts you probably never knew about e-doc.xii.jp

ガジェット好きでギークな産業医のブログ

Visit e-doc.xii.jp

Key Findings

We analyzed E-doc.xii.jp page load time and found that the first response time was 2.2 sec 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.

Performance Metrics

e-doc.xii.jp performance score

0

Network Requests Diagram

e-doc.xii.jp

2175 ms

wp-emoji-release.min.js

827 ms

styles.css

345 ms

css

70 ms

style.css

873 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 82% of them (27 requests) were addressed to the original E-doc.xii.jp, 6% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain E-doc.xii.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 347.2 kB (21%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-doc.xii.jp main page is 1.7 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 58.1 kB

  • Original 68.8 kB
  • After minification 62.6 kB
  • After compression 10.7 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 58.1 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 51.1 kB

  • Original 1.2 MB
  • After minification 1.2 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. E Doc Xii images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 113.9 kB

  • Original 173.7 kB
  • After minification 170.8 kB
  • After compression 59.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 113.9 kB or 66% of the original size.

CSS Optimization

-70%

Potential reduce by 124.1 kB

  • Original 176.1 kB
  • After minification 163.5 kB
  • After compression 52.0 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. E-doc.xii.jp needs all CSS files to be minified and compressed as it can save up to 124.1 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (52%)

Requests Now

29

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-doc.xii.jp

e-doc.xii.jp

2175 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

827 ms

styles.css

styles.css

345 ms

css

css

70 ms

style.css

style.css

873 ms

custom-style.css

custom-style.css

353 ms

dashicons.min.css

dashicons.min.css

885 ms

font-awesome.min.css

font-awesome.min.css

748 ms

jetpack.css

jetpack.css

951 ms

jquery.js

jquery.js

894 ms

jquery-migrate.min.js

jquery-migrate.min.js

846 ms

jquery.form.min.js

jquery.form.min.js

362 ms

scripts.js

scripts.js

376 ms

devicepx-jetpack.js

devicepx-jetpack.js

5 ms

navigation.js

navigation.js

376 ms

zg-toggle-search.js

zg-toggle-search.js

482 ms

wp-embed.min.js

wp-embed.min.js

559 ms

e-201611.js

e-201611.js

6 ms

20130820-P8200071.jpg

20130820-P8200071.jpg

882 ms

c89b3b959b15e7a8f4b78089f60157b3-1024x792-1-176x176.png

c89b3b959b15e7a8f4b78089f60157b3-1024x792-1-176x176.png

230 ms

0f5db7715d9a351d97ca76562af0f040-1024x768-1-176x176.jpeg

0f5db7715d9a351d97ca76562af0f040-1024x768-1-176x176.jpeg

230 ms

blog_160225_0001-1024x681-1-176x176.jpg

blog_160225_0001-1024x681-1-176x176.jpg

231 ms

blog_160226_0002-176x176.jpg

blog_160226_0002-176x176.jpg

231 ms

blog_160216_0001-176x176.jpg

blog_160216_0001-176x176.jpg

264 ms

kenkou_keiei13.jpeg

kenkou_keiei13.jpeg

856 ms

3a37d02ab71af6089667d8ed73dc8260.jpeg

3a37d02ab71af6089667d8ed73dc8260.jpeg

1047 ms

blog_160201_0001-2.jpg

blog_160201_0001-2.jpg

1238 ms

d5791476dffd4a9c0dbdc77e5871dd77.jpg

d5791476dffd4a9c0dbdc77e5871dd77.jpg

851 ms

2015-11-07-1.jpg

2015-11-07-1.jpg

441 ms

7XUFZ5tgS-tD6QamInJTcV7rzNbpW6Nj2hg-a3CqQCw.ttf

7XUFZ5tgS-tD6QamInJTcV7rzNbpW6Nj2hg-a3CqQCw.ttf

30 ms

anMUvcNT0H1YN4FII8wpr2-3NvDdcn-JtPTQTxuKc-Y.ttf

anMUvcNT0H1YN4FII8wpr2-3NvDdcn-JtPTQTxuKc-Y.ttf

45 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

578 ms

g.gif

g.gif

5 ms

SEO Factors

e-doc.xii.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-doc.xii.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 E-doc.xii.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.

Social Sharing Optimization

e-doc.xii.jp

Open Graph data is detected on the main page of E Doc Xii. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: