Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

webmoney.jp

電子マネーWebMoney(ウェブマネー)

Page Load Speed

21.7 sec in total

First Response

540 ms

Resources Loaded

20.8 sec

Page Rendered

367 ms

About Website

Click here to check amazing Webmoney content for Japan. Otherwise, check out these important facts you probably never knew about webmoney.jp

電子マネーWebMoney(ウェブマネー)は、オンラインゲームや音楽ダウンロードなどインターネット決済で最も標準的なプリペイド電子マネー。コンビニで誰でも購入OK&個人情報不要でセキュリティ面でも安心です。

Visit webmoney.jp

Key Findings

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

Performance Metrics

webmoney.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.102

89/100

15%

TTI (Time to Interactive)

Value14.5 s

9/100

10%

Network Requests Diagram

webmoney.jp

540 ms

www.webmoney.jp

1669 ms

common.css

507 ms

frontpage.css

715 ms

modernizr.flexbox.min.js

514 ms

Our browser made a total of 191 requests to load all elements on the main page. We found that 87% of them (167 requests) were addressed to the original Webmoney.jp, 4% (7 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Webmoney.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.2 kB (14%)

Content Size

2.0 MB

After Optimization

1.7 MB

In fact, the total size of Webmoney.jp main page is 2.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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 127.3 kB

  • Original 141.5 kB
  • After minification 110.3 kB
  • After compression 14.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 31.1 kB, which is 22% 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 127.3 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 93.2 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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. Webmoney images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 30.8 kB

  • Original 198.8 kB
  • After minification 193.2 kB
  • After compression 168.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 30.8 kB or 16% of the original size.

CSS Optimization

-37%

Potential reduce by 21.9 kB

  • Original 59.4 kB
  • After minification 56.8 kB
  • After compression 37.6 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. Webmoney.jp needs all CSS files to be minified and compressed as it can save up to 21.9 kB or 37% of the original size.

Requests Breakdown

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

Requests Now

189

After Optimization

128

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

Accessibility Review

webmoney.jp accessibility score

93

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-hidden="true"] elements contain focusable descendents

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

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

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

High

Browser errors were logged to the console

SEO Factors

webmoney.jp SEO score

90

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

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

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