Tools & Wizards About Us
yokai-punipuni.jp screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

yokai-punipuni.jp

妖怪ウォッチ ぷにぷに｜スマホゲーム 公式サイト

Page Load Speed

5.5 sec in total

First Response

600 ms

Resources Loaded

4.2 sec

Page Rendered

660 ms

yokai-punipuni.jp screenshot

About Website

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

「妖怪ウォッチ」が“ぷにっ”とパズルでスマホゲームに登場！妖怪ぷにをたくさんつなげて、あの妖怪たちを倒しちゃおう！

Visit yokai-punipuni.jp

Key Findings

We analyzed Yokai-punipuni.jp page load time and found that the first response time was 600 ms and then it took 4.9 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

yokai-punipuni.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value22.2 s

0/100

10%

TBT (Total Blocking Time)

Value31,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value40.6 s

0/100

10%

Network Requests Diagram

yokai-punipuni.jp

600 ms

yokai-punipuni.jp

669 ms

main.css

206 ms

sdk.js

26 ms

widgets.js

28 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Yokai-punipuni.jp, 56% (61 requests) were made to S.nhn-playart.com and 13% (14 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source S.nhn-playart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.3 kB (9%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yokai-punipuni.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. Only a small number of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 23.0 kB

  • Original 31.0 kB
  • After minification 29.3 kB
  • After compression 8.0 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 23.0 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 94.1 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. Yokai Punipuni images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 44.1 kB

  • Original 430.4 kB
  • After minification 430.4 kB
  • After compression 386.4 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

-25%

Potential reduce by 42.1 kB

  • Original 168.0 kB
  • After minification 167.4 kB
  • After compression 125.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. Yokai-punipuni.jp needs all CSS files to be minified and compressed as it can save up to 42.1 kB or 25% of the original size.

Requests Breakdown

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

Requests Now

105

After Optimization

79

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yokai-punipuni.jp

yokai-punipuni.jp

600 ms

yokai-punipuni.jp

yokai-punipuni.jp

669 ms

main.css

main.css

206 ms

sdk.js

sdk.js

26 ms

widgets.js

widgets.js

28 ms

jquery.min.js

jquery.min.js

29 ms

main.min.js

main.min.js

187 ms

adv.js

adv.js

31 ms

analytics.js

analytics.js

106 ms

PAjTnjjScIE

PAjTnjjScIE

355 ms

Lp3_sEPgrsc

Lp3_sEPgrsc

284 ms

JfLtNfn2cb0

JfLtNfn2cb0

318 ms

7QQRnAKNaVE

7QQRnAKNaVE

243 ms

Load_chara.png

Load_chara.png

83 ms

Load_yo.png

Load_yo.png

110 ms

Load_mi.png

Load_mi.png

86 ms

Load_ko.png

Load_ko.png

111 ms

Load_chu.png

Load_chu.png

110 ms

BG.png

BG.png

111 ms

bg_body_mdl.png

bg_body_mdl.png

131 ms

bg_body_top.png

bg_body_top.png

1460 ms

bg_body_btm.png

bg_body_btm.png

124 ms

logo_l5.svg

logo_l5.svg

126 ms

logo_punipuni.png

logo_punipuni.png

510 ms

txt_top.png

txt_top.png

124 ms

pic_top_deco.png

pic_top_deco.png

151 ms

btn_android.png

btn_android.png

858 ms

btn_ios.png

btn_ios.png

139 ms

btn_amazon.png

btn_amazon.png

133 ms

0801_comeback_cp.png

0801_comeback_cp.png

166 ms

bg_tw.png

bg_tw.png

167 ms

ttl_tw.png

ttl_tw.png

180 ms

bg_tw_frame.png

bg_tw_frame.png

211 ms

pic_sec01_more.png

pic_sec01_more.png

190 ms

ttl_sec01.png

ttl_sec01.png

256 ms

pic_sec01.png

pic_sec01.png

257 ms

pic_sec01_star.png

pic_sec01_star.png

255 ms

bg_phone.png

bg_phone.png

508 ms

pic_sec02_more.png

pic_sec02_more.png

468 ms

ttl_sec02.png

ttl_sec02.png

313 ms

pic_sec02.png

pic_sec02.png

674 ms

pic_sec02_2.png

pic_sec02_2.png

674 ms

pic_sec02_star.png

pic_sec02_star.png

1458 ms

pic_sec03_more.png

pic_sec03_more.png

674 ms

ttl_sec03.png

ttl_sec03.png

832 ms

pic_sec03.png

pic_sec03.png

833 ms

pic_sec03_star.png

pic_sec03_star.png

834 ms

btn_medal.svg

btn_medal.svg

834 ms

sdk.js

sdk.js

78 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

63 ms

btn_medal_txt.png

btn_medal_txt.png

825 ms

collect

collect

34 ms

settings

settings

105 ms

btn_medal_ico.png

btn_medal_ico.png

760 ms

js

js

137 ms

63 ms

btn_scword.svg

btn_scword.svg

733 ms

btn_scword_txt.png

btn_scword_txt.png

734 ms

btn_scword_ico.png

btn_scword_ico.png

732 ms

btn_movie.svg

btn_movie.svg

736 ms

btn_movie_txt.png

btn_movie_txt.png

723 ms

btn_movie_ico.png

btn_movie_ico.png

725 ms

ttl_sns.png

ttl_sns.png

728 ms

btn_sns.svg

btn_sns.svg

720 ms

btn_tw_txt.png

btn_tw_txt.png

722 ms

btn_fb_txt.png

btn_fb_txt.png

718 ms

ttl_share.png

ttl_share.png

713 ms

btn_tw.svg

btn_tw.svg

701 ms

btn_fb.svg

btn_fb.svg

689 ms

btn_line.svg

btn_line.svg

689 ms

www-player.css

www-player.css

15 ms

www-embed-player.js

www-embed-player.js

44 ms

base.js

base.js

135 ms

pic_bottom_puni.png

pic_bottom_puni.png

677 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

32 ms

pic_footer.png

pic_footer.png

1466 ms

btn_parents_txt.svg

btn_parents_txt.svg

763 ms

www-player.css

www-player.css

70 ms

www-embed-player.js

www-embed-player.js

252 ms

base.js

base.js

296 ms

btn_guideline_txt.svg

btn_guideline_txt.svg

605 ms

logo_l5_w.svg

logo_l5_w.svg

601 ms

logo_S_PA_w_all.svg

logo_S_PA_w_all.svg

579 ms

ad_status.js

ad_status.js

845 ms

ico_mail.svg

ico_mail.svg

516 ms

btn_top.svg

btn_top.svg

478 ms

yokai_punipuni

yokai_punipuni

1242 ms

-iaWypUxMAwVmZo986mMThLjwUu_f6uBwRf76o5foO4.js

-iaWypUxMAwVmZo986mMThLjwUu_f6uBwRf76o5foO4.js

548 ms

embed.js

embed.js

178 ms

AIdro_l2mwqCRkdVyadrTtTTa6zc4WZos5nWhQMAc0dAb5glQw=s68-c-k-c0x00ffffff-no-rj

AIdro_l2mwqCRkdVyadrTtTTa6zc4WZos5nWhQMAc0dAb5glQw=s68-c-k-c0x00ffffff-no-rj

450 ms

id

id

321 ms

embed.js

embed.js

104 ms

iframe_api

iframe_api

110 ms

Create

Create

488 ms

Create

Create

490 ms

Create

Create

609 ms

id

id

141 ms

Create

Create

578 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

460 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

461 ms

www-widgetapi.js

www-widgetapi.js

302 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

211 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

566 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

665 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

663 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

664 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

734 ms

_buildManifest.js

_buildManifest.js

746 ms

_ssgManifest.js

_ssgManifest.js

744 ms

Accessibility Review

yokai-punipuni.jp accessibility score

75

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

yokai-punipuni.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

High

Page has valid source maps

SEO Factors

yokai-punipuni.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

robots.txt is not valid

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 Yokai-punipuni.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 Yokai-punipuni.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

yokai-punipuni.jp

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