Tools & Wizards About Us
coffeedoctors.jp screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

coffeedoctors.jp

coFFee doctors -コーヒードクターズ-

Page Load Speed

6.3 sec in total

First Response

709 ms

Resources Loaded

5.3 sec

Page Rendered

302 ms

coffeedoctors.jp screenshot

About Website

Click here to check amazing CoFFee Doctors content for Japan. Otherwise, check out these important facts you probably never knew about coffeedoctors.jp

coFFee doctors（コーヒードクターズ）は、医師へのインタビューから、気軽に「医療＋α」が知れるウェブマガジンです。「私服」の「医師」と「コーヒー」という異色の組み合わせで、医療情報や医師の診療以外の活動を聞いていきます。

Visit coffeedoctors.jp

Key Findings

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

Performance Metrics

coffeedoctors.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.259

48/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

coffeedoctors.jp

709 ms

coffeedoctors.jp

1179 ms

style.css

406 ms

jsapi

26 ms

jquery.js

1215 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 71% of them (65 requests) were addressed to the original Coffeedoctors.jp, 7% (6 requests) were made to Apis.google.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Coffeedoctors.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.1 kB (10%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Coffeedoctors.jp main page is 2.2 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.7 kB

  • Original 48.5 kB
  • After minification 40.7 kB
  • After compression 9.8 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 7.8 kB, which is 16% 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 38.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 5.1 kB

  • Original 1.7 MB
  • After minification 1.7 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. CoFFee Doctors images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 133.8 kB

  • Original 400.4 kB
  • After minification 389.8 kB
  • After compression 266.6 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 133.8 kB or 33% of the original size.

CSS Optimization

-83%

Potential reduce by 36.6 kB

  • Original 43.8 kB
  • After minification 29.5 kB
  • After compression 7.3 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. Coffeedoctors.jp needs all CSS files to be minified and compressed as it can save up to 36.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (37%)

Requests Now

86

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

coffeedoctors.jp

coffeedoctors.jp

709 ms

coffeedoctors.jp

coffeedoctors.jp

1179 ms

style.css

style.css

406 ms

jsapi

jsapi

26 ms

jquery.js

jquery.js

1215 ms

jquery-migrate.min.js

jquery-migrate.min.js

528 ms

ga-scroll-events.js

ga-scroll-events.js

563 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

24 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

564 ms

jquery.watermark.js

jquery.watermark.js

584 ms

jquery.bannerRotation.js

jquery.bannerRotation.js

599 ms

jquery.infinitescroll.min.js

jquery.infinitescroll.min.js

877 ms

jquery.sidr.min.js

jquery.sidr.min.js

750 ms

jquery.heightLine.js

jquery.heightLine.js

751 ms

common.js

common.js

778 ms

js

js

74 ms

loader.js

loader.js

21 ms

bookmark_button.js

bookmark_button.js

21 ms

reset.css

reset.css

390 ms

base.css

base.css

533 ms

top.css

top.css

535 ms

detail.css

detail.css

570 ms

contact.css

contact.css

584 ms

about.css

about.css

648 ms

company.css

company.css

721 ms

dc.js

dc.js

132 ms

analytics.js

analytics.js

202 ms

button-only@2x.png

button-only@2x.png

120 ms

btnMenu.gif

btnMenu.gif

221 ms

hd_title.gif

hd_title.gif

201 ms

mainVisualBg.jpg

mainVisualBg.jpg

220 ms

main1.jpg

main1.jpg

527 ms

main.jpg

main.jpg

402 ms

main.jpg

main.jpg

396 ms

main.jpg

main.jpg

526 ms

main.jpg

main.jpg

985 ms

main1.jpg

main1.jpg

764 ms

82f222360e7a81fa1988c28351be2382.jpg

82f222360e7a81fa1988c28351be2382.jpg

1701 ms

S__4587524.jpg

S__4587524.jpg

597 ms

6c278e70-3531-488a-b3fa-be5bc85bd038.jpeg

6c278e70-3531-488a-b3fa-be5bc85bd038.jpeg

698 ms

21.jpg

21.jpg

702 ms

82f222360e7a81fa1988c28351be2382.jpg

82f222360e7a81fa1988c28351be2382.jpg

1764 ms

P1010113.jpg

P1010113.jpg

872 ms

82f222360e7a81fa1988c28351be23821.jpg

82f222360e7a81fa1988c28351be23821.jpg

1402 ms

31f0702bde33a86aa73fe9315fca73be.jpg

31f0702bde33a86aa73fe9315fca73be.jpg

952 ms

82f222360e7a81fa1988c28351be2382.jpg

82f222360e7a81fa1988c28351be2382.jpg

1738 ms

abb53b33aae59cd357e3b0959ce5554d.jpg

abb53b33aae59cd357e3b0959ce5554d.jpg

1139 ms

logo_dmenu.gif

logo_dmenu.gif

1179 ms

logo_goo.gif

logo_goo.gif

1328 ms

logo_yahoo.gif

logo_yahoo.gif

1375 ms

logo_nikkeimedical.gif

logo_nikkeimedical.gif

1516 ms

logo_nikkei.gif

logo_nikkei.gif

1570 ms

logo_huffpost.gif

logo_huffpost.gif

1578 ms

logo_qlife.gif

logo_qlife.gif

1703 ms

logo_koudan.gif

logo_koudan.gif

1764 ms

logo_forbes.gif

logo_forbes.gif

1753 ms

logo_m3carrer.gif

logo_m3carrer.gif

1889 ms

logo_medpeer.svg

logo_medpeer.svg

1891 ms

s_logo_dmenu.gif

s_logo_dmenu.gif

1912 ms

s_logo_goo.gif

s_logo_goo.gif

1928 ms

s_logo_yahoo.gif

s_logo_yahoo.gif

1958 ms

s_logo_nikkeimedical.gif

s_logo_nikkeimedical.gif

1958 ms

s_logo_nikkei.gif

s_logo_nikkei.gif

2075 ms

sdk.js

sdk.js

165 ms

s_logo_huffpost.gif

s_logo_huffpost.gif

2045 ms

platform.js

platform.js

61 ms

s_logo_qlife.gif

s_logo_qlife.gif

1888 ms

widgets.js

widgets.js

112 ms

sdk.js

sdk.js

34 ms

collect

collect

40 ms

s_logo_koudan.gif

s_logo_koudan.gif

1887 ms

sb_fb_title.png

sb_fb_title.png

1935 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

25 ms

fastbutton

fastbutton

35 ms

postmessageRelay

postmessageRelay

94 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

59 ms

settings

settings

97 ms

developers.google.com

developers.google.com

349 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

28 ms

rpc:shindig_random.js

rpc:shindig_random.js

15 ms

pagetop.png

pagetop.png

1759 ms

btn_link_icon.png

btn_link_icon.png

1865 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

19 ms

embeds

embeds

48 ms

titleIcon01.gif

titleIcon01.gif

1742 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

44 ms

sidebar_category_icon.gif

sidebar_category_icon.gif

1735 ms

titleIcon02.gif

titleIcon02.gif

1685 ms

footer_link_icon.gif

footer_link_icon.gif

1652 ms

Accessibility Review

coffeedoctors.jp accessibility score

55

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

coffeedoctors.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

coffeedoctors.jp SEO score

78

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

coffeedoctors.jp

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