Tools & Wizards About Us
pay.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

pay.jp

PAY.JP

Page Load Speed

4 sec in total

First Response

10 ms

Resources Loaded

2.9 sec

Page Rendered

1 sec

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 10 ms and then it took 4 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

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,440 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

pay.jp

10 ms

pay.jp

996 ms

js

79 ms

gtm.js

142 ms

scrollMonitor.js

362 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original Pay.jp, 7% (2 requests) were made to Googletagmanager.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Pay.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 186.4 kB (38%)

Content Size

487.5 kB

After Optimization

301.2 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-81%

Potential reduce by 180.1 kB

  • Original 222.9 kB
  • After minification 222.7 kB
  • After compression 42.8 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 180.1 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 255.8 kB
  • After minification 255.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

-71%

Potential reduce by 6.3 kB

  • Original 8.8 kB
  • After minification 8.8 kB
  • After compression 2.5 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 6.3 kB or 71% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

  • 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

10 ms

pay.jp

pay.jp

996 ms

js

js

79 ms

gtm.js

gtm.js

142 ms

scrollMonitor.js

scrollMonitor.js

362 ms

notosansjp.css

notosansjp.css

36 ms

img-ticker.oqhzbmsj.png

img-ticker.oqhzbmsj.png

531 ms

img_sec01.04drHi_w.svg

img_sec01.04drHi_w.svg

1276 ms

img_sec02.ANYovLW7.svg

img_sec02.ANYovLW7.svg

622 ms

ic_account.MOago3au.svg

ic_account.MOago3au.svg

404 ms

ic_application.NqqQicYi.svg

ic_application.NqqQicYi.svg

340 ms

ic_api.oCJVOGeK.svg

ic_api.oCJVOGeK.svg

673 ms

img_sec03.979rPcOM.svg

img_sec03.979rPcOM.svg

840 ms

img_visa.IwIbqUCm.svg

img_visa.IwIbqUCm.svg

722 ms

img_jcb.1g-QDzg4.svg

img_jcb.1g-QDzg4.svg

879 ms

img_ae.PUlUPFdn.svg

img_ae.PUlUPFdn.svg

1007 ms

img_dc.Z9w8lw4l.svg

img_dc.Z9w8lw4l.svg

1171 ms

img_dcv.HRVg3bwl.svg

img_dcv.HRVg3bwl.svg

1259 ms

img_apple.qav_E2I6.svg

img_apple.qav_E2I6.svg

1205 ms

img_sec04.n1KLlad0.svg

img_sec04.n1KLlad0.svg

1350 ms

ic_token.UoiPpxyO.svg

ic_token.UoiPpxyO.svg

1187 ms

ic_monitoring.RrVqhiHP.svg

ic_monitoring.RrVqhiHP.svg

1680 ms

img_sec06.9nB6nlDx.svg

img_sec06.9nB6nlDx.svg

1509 ms

b-monster.MZChNwRy.png

b-monster.MZChNwRy.png

2066 ms

img_esa.Oz0VPDza.png

img_esa.Oz0VPDza.png

1439 ms

img_rollcake.xn-xM022.png

img_rollcake.xn-xM022.png

1754 ms

img_flamingo.b7c_7gjl.png

img_flamingo.b7c_7gjl.png

1861 ms

img_hacomono.yVi1h1YE.png

img_hacomono.yVi1h1YE.png

1951 ms

Accessibility Review

pay.jp accessibility score

84

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pay.jp SEO score

92

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

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 Pay.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 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: