Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

pca.jp

サブスクやクラウドで使える会計ソフト | ピー・シー・エー株式会社

Page Load Speed

6.6 sec in total

First Response

953 ms

Resources Loaded

5.4 sec

Page Rendered

267 ms

pca.jp screenshot

About Website

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

複数使えばどんどんオトクなサブスク会計。創業40年、会計ソフトの先駆者PCAが会計ソフト,給与・人事管理ソフト,販売管理ソフトを、サブスクリプションやテレワークに最適なクラウドでご提供。豊富な連携サービスで中小企業の課題解決を支えます。

Visit pca.jp

Key Findings

We analyzed Pca.jp page load time and found that the first response time was 953 ms and then it took 5.7 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

pca.jp performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value22.0 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.301

39/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

pca.jp

953 ms

import.css

352 ms

top.css

528 ms

constructed.css

905 ms

jquery.js

1106 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 78% of them (80 requests) were addressed to the original Pca.jp, 3% (3 requests) were made to Googleadservices.com and 3% (3 requests) were made to Cache.dga.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Pca.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 619.0 kB (42%)

Content Size

1.5 MB

After Optimization

840.3 kB

In fact, the total size of Pca.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. 50% of websites need less resources to load. Images take 616.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 25.1 kB

  • Original 33.7 kB
  • After minification 30.4 kB
  • After compression 8.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 25.1 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 36.0 kB

  • Original 616.9 kB
  • After minification 580.9 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. Pca images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 303.0 kB

  • Original 500.9 kB
  • After minification 483.6 kB
  • After compression 197.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 303.0 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 255.0 kB

  • Original 307.7 kB
  • After minification 294.6 kB
  • After compression 52.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. Pca.jp needs all CSS files to be minified and compressed as it can save up to 255.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (27%)

Requests Now

98

After Optimization

72

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

Accessibility Review

pca.jp accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

pca.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pca.jp SEO score

91

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

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pca.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 Pca.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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