Tools & Wizards About Us
packageinsert.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

packageinsert.jp

医薬情報QLifePro

Page Load Speed

4.6 sec in total

First Response

352 ms

Resources Loaded

4.1 sec

Page Rendered

102 ms

packageinsert.jp screenshot

About Website

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

製剤写真付きの添付文書を、疾患別処方ランキング、適応症から検索する事ができます。PC版では相互作用チェック、飲食品相互作用チェック、薬価比較など医療者にとって便利なツールが揃っています。

Visit packageinsert.jp

Key Findings

We analyzed Packageinsert.jp page load time and found that the first response time was 352 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 70% of websites can load faster.

Performance Metrics

packageinsert.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.17

70/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

packageinsert.jp

352 ms

meds.qlifepro.com

532 ms

meds.qlifepro.com

1113 ms

base.css

916 ms

skeleton.css

920 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Packageinsert.jp, 54% (32 requests) were made to Meds.qlifepro.com and 19% (11 requests) were made to Qlifepro.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Meds.qlifepro.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 626.1 kB (61%)

Content Size

1.0 MB

After Optimization

393.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 123.6 kB

  • Original 144.7 kB
  • After minification 125.8 kB
  • After compression 21.2 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 19.0 kB, which is 13% 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 123.6 kB or 85% of the original size.

Image Optimization

-12%

Potential reduce by 2.0 kB

  • Original 16.6 kB
  • After minification 14.5 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, Packageinsert needs image optimization as it can save up to 2.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 367.2 kB

  • Original 694.2 kB
  • After minification 679.0 kB
  • After compression 327.0 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 367.2 kB or 53% of the original size.

CSS Optimization

-81%

Potential reduce by 133.3 kB

  • Original 164.3 kB
  • After minification 132.5 kB
  • After compression 31.1 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. Packageinsert.jp needs all CSS files to be minified and compressed as it can save up to 133.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (65%)

Requests Now

55

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

packageinsert.jp

packageinsert.jp

352 ms

meds.qlifepro.com

meds.qlifepro.com

532 ms

meds.qlifepro.com

meds.qlifepro.com

1113 ms

base.css

base.css

916 ms

skeleton.css

skeleton.css

920 ms

layout.css

layout.css

924 ms

jquery-ui.min.css

jquery-ui.min.css

348 ms

font-awesome.min.css

font-awesome.min.css

519 ms

perfect-scrollbar.css

perfect-scrollbar.css

547 ms

photoswipe.css

photoswipe.css

586 ms

default-skin.css

default-skin.css

585 ms

jquery.bxslider.css

jquery.bxslider.css

585 ms

slick.css

slick.css

586 ms

slick-theme.css

slick-theme.css

662 ms

common.css

common.css

878 ms

elements.css

elements.css

754 ms

insertjs.css

insertjs.css

755 ms

insert.css

insert.css

926 ms

medicalPersonnelAuthentication.css

medicalPersonnelAuthentication.css

937 ms

gpt.js

gpt.js

219 ms

jquery-2.2.0.min.js

jquery-2.2.0.min.js

1097 ms

jquery-ui.min.js

jquery-ui.min.js

1494 ms

photoswipe.min.js

photoswipe.min.js

1096 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

926 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

1043 ms

slick.min.js

slick.min.js

1269 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1105 ms

common.js

common.js

1209 ms

insert.js

insert.js

1266 ms

insertdata.js

insertdata.js

1267 ms

favorite.js

favorite.js

1269 ms

medsga.js

medsga.js

1375 ms

qlifepro_header.php

qlifepro_header.php

941 ms

medicalPersonnelAuthentication.js

medicalPersonnelAuthentication.js

946 ms

set-photoswipe.js

set-photoswipe.js

1282 ms

pubads_impl.js

pubads_impl.js

20 ms

4108249

4108249

117 ms

logout.png

logout.png

194 ms

logo_packageinsert.png

logo_packageinsert.png

193 ms

qlm.png

qlm.png

193 ms

ava.png

ava.png

193 ms

menu.png

menu.png

177 ms

ads

ads

160 ms

container.html

container.html

124 ms

logo_pro.png

logo_pro.png

183 ms

analytics.js

analytics.js

74 ms

diseasename

diseasename

393 ms

ajax-loader.gif

ajax-loader.gif

198 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

196 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

518 ms

linkid.js

linkid.js

8 ms

collect

collect

20 ms

collect

collect

34 ms

collect

collect

28 ms

js

js

142 ms

collect

collect

17 ms

js

js

57 ms

ga-audiences

ga-audiences

129 ms

ga-audiences

ga-audiences

115 ms

Accessibility Review

packageinsert.jp accessibility score

68

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

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

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

Page has valid source maps

SEO Factors

packageinsert.jp SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

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

packageinsert.jp

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