Tools & Wizards About Us
qlife.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

qlife.jp

医療総合サイトQLife（キューライフ）

Page Load Speed

6.6 sec in total

First Response

341 ms

Resources Loaded

6 sec

Page Rendered

287 ms

qlife.jp screenshot

About Website

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

医療に関する様々な情報を取り扱う医療総合QLife（キューライフ）です。患者さん・医師・看護師・薬剤師による病院口コミ・評判、処方薬・市販薬や病気・検査・治療法などの情報、医療ニュース・特集など医療に関する情報を多数掲載しています。

Visit qlife.jp

Key Findings

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

Performance Metrics

qlife.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value3,970 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.138

79/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

qlife.jp

341 ms

qlife.jp

693 ms

www.qlife.jp

875 ms

base_pc.css

173 ms

global_pc.css

346 ms

Our browser made a total of 141 requests to load all elements on the main page. We found that 50% of them (71 requests) were addressed to the original Qlife.jp, 9% (12 requests) were made to Tpc.googlesyndication.com and 4% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Qlife-atopy.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 258.5 kB (13%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qlife.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 70.0 kB

  • Original 86.7 kB
  • After minification 82.0 kB
  • After compression 16.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 70.0 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 42.7 kB

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

JavaScript Optimization

-22%

Potential reduce by 142.8 kB

  • Original 653.6 kB
  • After minification 653.6 kB
  • After compression 510.9 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 142.8 kB or 22% of the original size.

CSS Optimization

-12%

Potential reduce by 3.0 kB

  • Original 24.5 kB
  • After minification 24.5 kB
  • After compression 21.6 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. Qlife.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 12% of the original size.

Requests Breakdown

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

Requests Now

130

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qlife.jp

qlife.jp

341 ms

qlife.jp

qlife.jp

693 ms

www.qlife.jp

www.qlife.jp

875 ms

base_pc.css

base_pc.css

173 ms

global_pc.css

global_pc.css

346 ms

utility.css

utility.css

502 ms

top_element_pc.css

top_element_pc.css

505 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

27 ms

jquery-ui.min.js

jquery-ui.min.js

35 ms

html5shiv.min.js

html5shiv.min.js

537 ms

jquery.colorimazer.min.js

jquery.colorimazer.min.js

536 ms

featherlight.js

featherlight.js

536 ms

jquery.cookie.min.js

jquery.cookie.min.js

538 ms

global_pc.js

global_pc.js

670 ms

top_pc.js

top_pc.js

671 ms

jbox-combined.min.css

jbox-combined.min.css

683 ms

badge_pc.css

badge_pc.css

685 ms

jbox-combined.min.js

jbox-combined.min.js

799 ms

OneSignalSDK.js

OneSignalSDK.js

50 ms

gtm.js

gtm.js

78 ms

js

js

160 ms

destination

destination

160 ms

analytics.js

analytics.js

1023 ms

gpt.js

gpt.js

1020 ms

jyuzen1img_100.jpg

jyuzen1img_100.jpg

1615 ms

1809_01_01.jpg

1809_01_01.jpg

1680 ms

ikebukuro_square.png

ikebukuro_square.png

2301 ms

yokukansan3img_100.jpg

yokukansan3img_100.jpg

1678 ms

kamopnews_rounen1_100.jpg

kamopnews_rounen1_100.jpg

1615 ms

kamopnews_rounen2_100.jpg

kamopnews_rounen2_100.jpg

1616 ms

kampo_eye07_100.jpg

kampo_eye07_100.jpg

1617 ms

takayamakampo_clinic_100.jpg

takayamakampo_clinic_100.jpg

1616 ms

shinjyuku_square.png

shinjyuku_square.png

2302 ms

btn_badge_close.png

btn_badge_close.png

1018 ms

icon_header_badge.png

icon_header_badge.png

1019 ms

icon_header_fb.png

icon_header_fb.png

1016 ms

icon_header_tw.png

icon_header_tw.png

1017 ms

header_icon_lock.png

header_icon_lock.png

1018 ms

header_icon_user.png

header_icon_user.png

1016 ms

header_btn_search.png

header_btn_search.png

1093 ms

btn_search_100x40.png

btn_search_100x40.png

1092 ms

bnr_orphan_180_110.png

bnr_orphan_180_110.png

1091 ms

behcets_180-110.png

behcets_180-110.png

1091 ms

pharmony_180x110_v2.png

pharmony_180x110_v2.png

1092 ms

sscoc_180x110.png

sscoc_180x110.png

1092 ms

icon_site_ibd.png

icon_site_ibd.png

1345 ms

icon_site_gene.png

icon_site_gene.png

1344 ms

hcn2405021_100.jpg

hcn2405021_100.jpg

1343 ms

icon_site_cancer.png

icon_site_cancer.png

1343 ms

banner_IBD_728_90.png

banner_IBD_728_90.png

1444 ms

sscoc_200x200.png

sscoc_200x200.png

1343 ms

atrialfibrillation_bnr_200_200.png

atrialfibrillation_bnr_200_200.png

1616 ms

pharmony_148x148C.png

pharmony_148x148C.png

1877 ms

bnr_lilli_genetictest_156x156.jpg

bnr_lilli_genetictest_156x156.jpg

1615 ms

mirueru_200_200.jpg

mirueru_200_200.jpg

1616 ms

feature_ibd_special_top100_100.jpg

feature_ibd_special_top100_100.jpg

1614 ms

gl100.jpg

gl100.jpg

1615 ms

locomo_100.jpg

locomo_100.jpg

1692 ms

n1005.jpg

n1005.jpg

1689 ms

k1.jpg

k1.jpg

1690 ms

st_list016.jpg

st_list016.jpg

1690 ms

st_list001.jpg

st_list001.jpg

1773 ms

icon_site_atopy.png

icon_site_atopy.png

1876 ms

ban_disease_ex_728_90.png

ban_disease_ex_728_90.png

1877 ms

btn_search_30x30.png

btn_search_30x30.png

1877 ms

1809_02_01.jpg

1809_02_01.jpg

1872 ms

1809_03_01.jpg

1809_03_01.jpg

1672 ms

1809_04_01.jpg

1809_04_01.jpg

1671 ms

1809_05_01.jpg

1809_05_01.jpg

1670 ms

side_banner_photo.png

side_banner_photo.png

1874 ms

side_banner_dtcsites.png

side_banner_dtcsites.png

1912 ms

side_banner_%20medicommi.png

side_banner_%20medicommi.png

1898 ms

logo_qlife_basic.png

logo_qlife_basic.png

2057 ms

lt.js

lt.js

793 ms

notice.jsonp

notice.jsonp

1167 ms

body_bg.png

body_bg.png

1154 ms

circle_m_00.png

circle_m_00.png

1153 ms

mark_doctor_g.png

mark_doctor_g.png

1153 ms

mark_nurse_g.png

mark_nurse_g.png

1385 ms

mark_pharma_g.png

mark_pharma_g.png

1432 ms

ytag.js

ytag.js

1016 ms

pubads_impl.js

pubads_impl.js

56 ms

collect

collect

30 ms

js

js

112 ms

comments_mark.png

comments_mark.png

1359 ms

mark_patient_g.png

mark_patient_g.png

1358 ms

map_japan.png

map_japan.png

1361 ms

side_title.png

side_title.png

1361 ms

side_icon_kampo.png

side_icon_kampo.png

1665 ms

btn_backtop.png

btn_backtop.png

1661 ms

err.gif

err.gif

781 ms

collect

collect

84 ms

js

js

86 ms

4108249

4108249

191 ms

collect

collect

79 ms

icon_hosp_g.png

icon_hosp_g.png

1414 ms

icon_meds_g.png

icon_meds_g.png

1414 ms

icon_dict_g.png

icon_dict_g.png

1412 ms

icon_hosp_w.png

icon_hosp_w.png

1409 ms

icon_meds_w.png

icon_meds_w.png

1622 ms

collect

collect

15 ms

ga-audiences

ga-audiences

75 ms

icon_dict_w.png

icon_dict_w.png

1518 ms

ads

ads

575 ms

container.html

container.html

37 ms

fbevents.js

fbevents.js

21 ms

uwt.js

uwt.js

123 ms

2213615218677320

2213615218677320

273 ms

516718982931829230

516718982931829230

310 ms

icon.png

icon.png

135 ms

abg_lite.js

abg_lite.js

298 ms

s

s

287 ms

window_focus.js

window_focus.js

298 ms

qs_click_protection.js

qs_click_protection.js

309 ms

ufs_web_display.js

ufs_web_display.js

313 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

297 ms

18128009837513259605

18128009837513259605

463 ms

10690081541133930722

10690081541133930722

455 ms

icon.png

icon.png

668 ms

ext.js

ext.js

211 ms

css

css

345 ms

icon.png

icon.png

45 ms

css

css

545 ms

css

css

599 ms

m_js_controller.js

m_js_controller.js

204 ms

adsct

adsct

734 ms

adsct

adsct

739 ms

326083939580892

326083939580892

307 ms

9590477003167593759

9590477003167593759

312 ms

13700371256121435428

13700371256121435428

312 ms

icon.png

icon.png

129 ms

activeview

activeview

276 ms

activeview

activeview

236 ms

activeview

activeview

231 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

209 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

300 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

301 ms

14763004658117789537

14763004658117789537

250 ms

icon.png

icon.png

137 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

138 ms

activeview

activeview

84 ms

Accessibility Review

qlife.jp accessibility score

64

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

qlife.jp best practices score

67

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

Page has valid source maps

SEO Factors

qlife.jp SEO score

91

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

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 Qlife.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 Qlife.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

qlife.jp

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