Tools & Wizards About Us
pay.jp screenshot

Report Summary

  • 34

    Performance

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

  • 100

    SEO

    Google-friendlier than
    95% of websites

pay.jp

PAY.JP

Page Load Speed

4.7 sec in total

First Response

320 ms

Resources Loaded

4 sec

Page Rendered

340 ms

pay.jp screenshot

About Website

Welcome to pay.jp homepage info - get ready to check PAY best content for Japan right away, or after learning these important things about pay.jp

様々なサービスにクレジットカード決済を無料で簡単に導入できる開発者向けのオンライン決済サービスです。ビジネスに沿ったプラン、柔軟な料金体系、テスト環境、日本語の開発ドキュメントの公開など時間をかけることなく導入可能です。

Visit pay.jp

Key Findings

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

Performance Metrics

pay.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

pay.jp

320 ms

pay.jp

652 ms

pay.min.css

1097 ms

css

115 ms

tweet_button.420281f7dd393a35b17552fb11b499a9.ja.html

198 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Pay.jp, 55% (17 requests) were made to D3vq62w6khyz8s.cloudfront.net and 10% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source D3vq62w6khyz8s.cloudfront.net.

Page Optimization Overview & Recommendations

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

Content Size

445.1 kB

After Optimization

389.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pay.jp main page is 445.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 354.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 12.4 kB

  • Original 16.8 kB
  • After minification 15.2 kB
  • After compression 4.5 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 12.4 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 308 B

  • Original 354.1 kB
  • After minification 353.8 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. PAY images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 43.2 kB

  • Original 53.1 kB
  • After minification 53.0 kB
  • After compression 10.0 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. Pay.jp needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PAY. According to our analytics all requests are already optimized.

Network Requests Diagram

pay.jp

pay.jp

320 ms

pay.jp

pay.jp

652 ms

pay.min.css

pay.min.css

1097 ms

css

css

115 ms

tweet_button.420281f7dd393a35b17552fb11b499a9.ja.html

tweet_button.420281f7dd393a35b17552fb11b499a9.ja.html

198 ms

header-logo.png

header-logo.png

763 ms

logo.png

logo.png

756 ms

icon_feature_1.png

icon_feature_1.png

751 ms

free-icon.png

free-icon.png

808 ms

flex-icon.png

flex-icon.png

920 ms

fee.png

fee.png

1562 ms

visa.png

visa.png

1493 ms

mastercard.png

mastercard.png

1447 ms

jcb.png

jcb.png

1624 ms

americanexpress.png

americanexpress.png

1597 ms

dinersclub.png

dinersclub.png

1743 ms

discover.png

discover.png

2094 ms

payjp_feature_text.png

payjp_feature_text.png

2153 ms

sec_3_display.png

sec_3_display.png

2379 ms

like.php

like.php

153 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

150 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

152 ms

jot

jot

100 ms

count.json

count.json

63 ms

rU2ubZ6l1Q5.js

rU2ubZ6l1Q5.js

53 ms

analytics.js

analytics.js

72 ms

visual-hokusai.png

visual-hokusai.png

1946 ms

footer-social.png

footer-social.png

1186 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

44 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

83 ms

collect

collect

49 ms

Accessibility Review

pay.jp accessibility score

87

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

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

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

SEO Factors

pay.jp SEO score

100

Search Engine Optimization Advices

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

    JA

  • Encoding

    UTF-8

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

pay.jp

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