Tools & Wizards About Us
ponta.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ponta.jp

PontaWeb［Pontaカード/Pontaポイント］

Page Load Speed

5.5 sec in total

First Response

820 ms

Resources Loaded

4.3 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 820 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ponta.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.602

10/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

ponta.jp

820 ms

971 ms

base_pc.css

177 ms

dynamic_pc.css

353 ms

insertion.css

502 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ponta.jp, 30% (29 requests) were made to Point.recruit.co.jp and 24% (23 requests) were made to Cdn.r-adimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Point.recruit.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 505.3 kB (23%)

Content Size

2.2 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-68%

Potential reduce by 71.5 kB

  • Original 105.5 kB
  • After minification 102.6 kB
  • After compression 33.9 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 71.5 kB or 68% of the original size.

Image Optimization

-22%

Potential reduce by 403.4 kB

  • Original 1.8 MB
  • After minification 1.4 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. Obviously, Ponta needs image optimization as it can save up to 403.4 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-14%

Potential reduce by 30.2 kB

  • Original 221.2 kB
  • After minification 221.1 kB
  • After compression 190.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 30.2 kB or 14% of the original size.

CSS Optimization

-0%

Potential reduce by 70 B

  • Original 29.5 kB
  • After minification 29.5 kB
  • After compression 29.4 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 has all CSS files already compressed.

Requests Breakdown

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

Requests Now

92

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 92 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 22 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ponta.jp

ponta.jp

820 ms

971 ms

base_pc.css

base_pc.css

177 ms

dynamic_pc.css

dynamic_pc.css

353 ms

insertion.css

insertion.css

502 ms

modernizr-latest.js

modernizr-latest.js

686 ms

launch-ENa7a864b53235464eb98f71e7b452cbd4.min.js

launch-ENa7a864b53235464eb98f71e7b452cbd4.min.js

20 ms

default.js

default.js

682 ms

rcoas.js

rcoas.js

525 ms

jquery.min.js

jquery.min.js

772 ms

cmn-fnc_pc.js

cmn-fnc_pc.js

808 ms

dynamic_pc.js

dynamic_pc.js

823 ms

insertion.js

insertion.js

669 ms

site01_a.svg

site01_a.svg

195 ms

sprite-header.svg

sprite-header.svg

192 ms

sprite-ico.svg

sprite-ico.svg

332 ms

ponpare_mall730-110.jpg

ponpare_mall730-110.jpg

809 ms

img_intro_shop.png

img_intro_shop.png

302 ms

img_intro_net.png

img_intro_net.png

314 ms

img_id_ponta.png

img_id_ponta.png

516 ms

img_id_recruit.png

img_id_recruit.png

349 ms

bnr_aside_right_3.png

bnr_aside_right_3.png

500 ms

view_point_use_service-pc.png

view_point_use_service-pc.png

921 ms

bnr-LINE.jpg

bnr-LINE.jpg

664 ms

bnr-twitter.jpg

bnr-twitter.jpg

695 ms

bnr-facebook.jpg

bnr-facebook.jpg

1091 ms

bnr-Instagram.jpg

bnr-Instagram.jpg

858 ms

bnr-YouTube.jpg

bnr-YouTube.jpg

998 ms

footer_logo.png

footer_logo.png

869 ms

loyaltymarketing01_a.svg

loyaltymarketing01_a.svg

995 ms

insight.js

insight.js

175 ms

td_pttd_sync.js

td_pttd_sync.js

823 ms

tr.js

tr.js

177 ms

td.min.js

td.min.js

53 ms

dd

dd

237 ms

fbevents.js

fbevents.js

88 ms

js

js

161 ms

ytag.js

ytag.js

745 ms

cv

cv

200 ms

ics

ics

712 ms

f

f

714 ms

f

f

720 ms

f

f

726 ms

f

f

729 ms

f

f

730 ms

f

f

730 ms

f

f

878 ms

f

f

884 ms

sprite_diagonal-ico.svg

sprite_diagonal-ico.svg

987 ms

ico_pagetop01.svg

ico_pagetop01.svg

968 ms

json

json

786 ms

json

json

789 ms

collect

collect

698 ms

log

log

709 ms

s61512436186894

s61512436186894

25 ms

168 ms

td_ponta

td_ponta

16 ms

pixel

pixel

32 ms

pixel

pixel

20 ms

sync

sync

7 ms

json

json

547 ms

json

json

548 ms

json

json

690 ms

json

json

698 ms

json

json

702 ms

json

json

704 ms

json

json

710 ms

json

json

710 ms

json

json

853 ms

10014690_0_54e80ca846e366d262ddd100cea70762.png

10014690_0_54e80ca846e366d262ddd100cea70762.png

264 ms

10014690_0_9204cc4b07fd9ac6a7594308b297a9c5.jpg

10014690_0_9204cc4b07fd9ac6a7594308b297a9c5.jpg

380 ms

10014690_0_b77695603b1dd13b12c2555cfbe72775.png

10014690_0_b77695603b1dd13b12c2555cfbe72775.png

298 ms

aid

aid

849 ms

10014690_0_af30a964111e4ee02bda557568b73799.png

10014690_0_af30a964111e4ee02bda557568b73799.png

194 ms

10014690_0_1ff9c2482636fad8cb3ecd7e6f8d7bc1.png

10014690_0_1ff9c2482636fad8cb3ecd7e6f8d7bc1.png

188 ms

10014690_0_e2302b82abc310d589f6402ca5be92aa.png

10014690_0_e2302b82abc310d589f6402ca5be92aa.png

46 ms

sync

sync

3 ms

10014690_0_d1a5cc701e6d00bba94159ba64649ca9.png

10014690_0_d1a5cc701e6d00bba94159ba64649ca9.png

678 ms

10014690_0_e7c9fc69d86c2a8d0afe8298c4c7fc6d.png

10014690_0_e7c9fc69d86c2a8d0afe8298c4c7fc6d.png

237 ms

10014690_0_955aeacfaec4eb51a5de0ad4a7b414d9.png

10014690_0_955aeacfaec4eb51a5de0ad4a7b414d9.png

196 ms

10014690_0_8e185f544db035ac8252ed35909255d4.png

10014690_0_8e185f544db035ac8252ed35909255d4.png

324 ms

10014690_0_f8f750bd9485408ae4e092f3a5beb706.png

10014690_0_f8f750bd9485408ae4e092f3a5beb706.png

218 ms

10014690_0_f7b955bd51a762b3fb8be91f2396a891.png

10014690_0_f7b955bd51a762b3fb8be91f2396a891.png

246 ms

10014690_0_ee649b1896331df2ce5f1860b012cd41.png

10014690_0_ee649b1896331df2ce5f1860b012cd41.png

384 ms

10014690_0_18fd177b128ee7e1c30d5b30f6060207.jpg

10014690_0_18fd177b128ee7e1c30d5b30f6060207.jpg

546 ms

10014690_0_4df4db885046ae52801d4b58cf958fb6.png

10014690_0_4df4db885046ae52801d4b58cf958fb6.png

389 ms

10014690_0_f60ba8e06520e5bc25876951f2702438.png

10014690_0_f60ba8e06520e5bc25876951f2702438.png

482 ms

10014690_0_dad5aa1cae31367cbc54c03d2ab24a41.png

10014690_0_dad5aa1cae31367cbc54c03d2ab24a41.png

473 ms

10014690_0_aeae3c27a8e8883455703d11991511ff.png

10014690_0_aeae3c27a8e8883455703d11991511ff.png

554 ms

10014690_0_86ba64d2e14b8485bb03e05631b5250f.jpg

10014690_0_86ba64d2e14b8485bb03e05631b5250f.jpg

539 ms

10014690_0_ce9c0cdf4299ad625002ff33d0791fdd.png

10014690_0_ce9c0cdf4299ad625002ff33d0791fdd.png

648 ms

10014690_0_05334d7e40b27953c81b3e2de0eaf09c.png

10014690_0_05334d7e40b27953c81b3e2de0eaf09c.png

662 ms

10014690_0_cacf2b4648ddb504e15288a5165d1391.png

10014690_0_cacf2b4648ddb504e15288a5165d1391.png

718 ms

10014690_0_7183a68725ff1f1cdee5885f3d36e931.png

10014690_0_7183a68725ff1f1cdee5885f3d36e931.png

570 ms

td_user_mapping_log

td_user_mapping_log

3 ms

RC944d7e02337c4309b41f6facec514ebf-source.min.js

RC944d7e02337c4309b41f6facec514ebf-source.min.js

4 ms

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

ponta.jp

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: