Tools & Wizards About Us
ptc.co.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    70% 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

  • 84

    SEO

    Google-friendlier than
    53% of websites

ptc.co.jp

薬剤師研修ならプラザコンサルティング株式会社

Page Load Speed

8.7 sec in total

First Response

2.5 sec

Resources Loaded

6 sec

Page Rendered

219 ms

ptc.co.jp screenshot

About Website

Welcome to ptc.co.jp homepage info - get ready to check Ptc best content right away, or after learning these important things about ptc.co.jp

プラザコンサルティングは、「健康サポート薬局」を実現する為の伴走者として、薬剤師の皆様のマネジメント・リーダーシップ・コミュニケーション（接遇）開発をご支援致します。

Visit ptc.co.jp

Key Findings

We analyzed Ptc.co.jp page load time and found that the first response time was 2.5 sec and then it took 6.2 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

ptc.co.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

ptc.co.jp

2522 ms

styles.css

352 ms

front.css

862 ms

bootstrap.css

1206 ms

font-awesome.min.css

710 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 87% of them (39 requests) were addressed to the original Ptc.co.jp, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Html5shiv.googlecode.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ptc.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.9 kB (29%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ptc.co.jp main page is 1.5 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. 20% of websites need less resources to load. Images take 992.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 32.3 kB

  • Original 39.7 kB
  • After minification 37.8 kB
  • After compression 7.3 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 32.3 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 27.1 kB

  • Original 992.6 kB
  • After minification 965.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. Ptc images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 177.6 kB

  • Original 262.4 kB
  • After minification 259.4 kB
  • After compression 84.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 177.6 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 200.8 kB

  • Original 240.5 kB
  • After minification 217.9 kB
  • After compression 39.7 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. Ptc.co.jp needs all CSS files to be minified and compressed as it can save up to 200.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ptc.co.jp

ptc.co.jp

2522 ms

styles.css

styles.css

352 ms

front.css

front.css

862 ms

bootstrap.css

bootstrap.css

1206 ms

font-awesome.min.css

font-awesome.min.css

710 ms

bizvektor_common_min.css

bizvektor_common_min.css

547 ms

001.css

001.css

696 ms

style_bizvektor_sns.css

style_bizvektor_sns.css

715 ms

css

css

26 ms

lightbox.min.css

lightbox.min.css

732 ms

jquery.js

jquery.js

1381 ms

jquery-migrate.min.js

jquery-migrate.min.js

886 ms

bootstrap.min.js

bootstrap.min.js

898 ms

front.js

front.js

917 ms

chosen.jquery.min.js

chosen.jquery.min.js

1033 ms

html5.js

html5.js

23 ms

style.css

style.css

902 ms

script.js

script.js

557 ms

wp-slimstat.min.js

wp-slimstat.min.js

10 ms

jquery.form.min.js

jquery.form.min.js

577 ms

scripts.js

scripts.js

685 ms

comment-reply.min.js

comment-reply.min.js

720 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

739 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

761 ms

biz-vektor-min.js

biz-vektor-min.js

847 ms

plain.css

plain.css

867 ms

iconMenuClose.png

iconMenuClose.png

187 ms

cropped-c55ccc4339046d448ccbb6d93aa2702a.jpg

cropped-c55ccc4339046d448ccbb6d93aa2702a.jpg

179 ms

solution.jpg

solution.jpg

369 ms

pr_image_demo_sq_1.jpg

pr_image_demo_sq_1.jpg

348 ms

icon_try1_white.gif

icon_try1_white.gif

180 ms

company.jpg

company.jpg

535 ms

inquiry.jpg

inquiry.jpg

355 ms

pr_image_demo_sq_3.jpg

pr_image_demo_sq_3.jpg

354 ms

bnr_contact_ja.png

bnr_contact_ja.png

371 ms

footer_pagetop.png

footer_pagetop.png

523 ms

icon_arrow1_white.gif

icon_arrow1_white.gif

527 ms

rogo2.jpg

rogo2.jpg

1217 ms

icon_arrow1_gray.gif

icon_arrow1_gray.gif

555 ms

icon_arrow2_gray.gif

icon_arrow2_gray.gif

559 ms

admin-ajax.php

admin-ajax.php

1021 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

6 ms

pta.js

pta.js

329 ms

admin-ajax.php

admin-ajax.php

567 ms

27413d01.js

27413d01.js

837 ms

Accessibility Review

ptc.co.jp accessibility score

68

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ptc.co.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

SEO Factors

ptc.co.jp SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

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

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 Ptc.co.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 Ptc.co.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

ptc.co.jp

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