Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ponta.jp

PontaWeb[Pontaカード/Pontaポイント]

Page Load Speed

6.8 sec in total

First Response

1.2 sec

Resources Loaded

5.2 sec

Page Rendered

364 ms

ponta.jp screenshot

About Website

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

PontaWebは、共通ポイント“Ponta[ポンタ]”の公式サイトです。ポイント、ポンポンたまる!つかえる!共通ポイント。活用すればするほど、トクする!みんなにうれしいサービス。いろいろなPonta提携店舗・WEBサービスで、利用する金額に応じてポイントをためる、つかうことのできる共通ポイントサービスです。

Visit ponta.jp

Key Findings

We analyzed Ponta.jp page load time and found that the first response time was 1.2 sec and then it took 5.6 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

ponta.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.506

16/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

ponta.jp

1228 ms

base_pc.css

717 ms

top_pc.css

727 ms

jquery.min.js

1040 ms

jquery.query.js

574 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 26% of them (37 requests) were addressed to the original Ponta.jp, 10% (14 requests) were made to Pntmail.sslcs.cdngc.net and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Pntmail.sslcs.cdngc.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.8 kB (36%)

Content Size

1.2 MB

After Optimization

742.0 kB

In fact, the total size of Ponta.jp main page is 1.2 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. 65% of websites need less resources to load. Javascripts take 572.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 35.5 kB

  • Original 48.1 kB
  • After minification 42.4 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 12% 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 35.5 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 11.0 kB

  • Original 499.8 kB
  • After minification 488.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. Ponta images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 338.8 kB

  • Original 572.3 kB
  • After minification 537.4 kB
  • After compression 233.6 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 338.8 kB or 59% of the original size.

CSS Optimization

-82%

Potential reduce by 30.6 kB

  • Original 37.5 kB
  • After minification 29.5 kB
  • After compression 6.9 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. Ponta.jp needs all CSS files to be minified and compressed as it can save up to 30.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

137

After Optimization

54

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

Accessibility Review

ponta.jp accessibility score

60

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

Image elements do not have [alt] attributes

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

ponta.jp best practices score

75

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

Browser errors were logged to the console

SEO Factors

ponta.jp SEO score

92

Search Engine Optimization Advices

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