Tools & Wizards About Us
punyus.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    28% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

punyus.jp

PUNYUS Online Store / 公式通販 | 渡辺直美がプロデュースするレディースファッションブランド

Page Load Speed

3.6 sec in total

First Response

579 ms

Resources Loaded

2.8 sec

Page Rendered

147 ms

punyus.jp screenshot

About Website

Visit punyus.jp now to see the best up-to-date PUNYUS content for Japan and also check out these interesting facts you probably never knew about punyus.jp

PUNYUS(プニュズ)の通販サイトです。「女の子の持つ感情を表現する」をテーマにジャンルに捉われない様々なスタイルを提案するブランド。豊富なサイズ展開が特徴で、フリーから6Lまでのサイズが揃う。

Visit punyus.jp

Key Findings

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

Performance Metrics

punyus.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value13.7 s

1/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.338

33/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

punyus.jp

579 ms

style.css

186 ms

top3.css

327 ms

jquery-1.9.1.min.js

876 ms

jquery.easing.1.3.js

352 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 37% of them (32 requests) were addressed to the original Punyus.jp, 41% (36 requests) were made to Static.xx.fbcdn.net and 7% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (876 ms) belongs to the original domain Punyus.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.1 kB (48%)

Content Size

932.2 kB

After Optimization

483.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-64%

Potential reduce by 5.9 kB

  • Original 9.2 kB
  • After minification 8.3 kB
  • After compression 3.3 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 5.9 kB or 64% of the original size.

Image Optimization

-1%

Potential reduce by 2.9 kB

  • Original 308.5 kB
  • After minification 305.6 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. PUNYUS images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 202.7 kB

  • Original 328.5 kB
  • After minification 324.0 kB
  • After compression 125.8 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 202.7 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 237.6 kB

  • Original 286.1 kB
  • After minification 273.8 kB
  • After compression 48.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. Punyus.jp needs all CSS files to be minified and compressed as it can save up to 237.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (66%)

Requests Now

86

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

punyus.jp

punyus.jp

579 ms

style.css

style.css

186 ms

top3.css

top3.css

327 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

876 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

352 ms

script.js

script.js

371 ms

common.css

common.css

185 ms

container.css

container.css

465 ms

navigation.css

navigation.css

329 ms

parts.css

parts.css

341 ms

table.css

table.css

369 ms

header.css

header.css

185 ms

footer.css

footer.css

164 ms

h_logo.png

h_logo.png

219 ms

h_about.gif

h_about.gif

178 ms

h_news.gif

h_news.gif

163 ms

h_collection.gif

h_collection.gif

177 ms

h_onlinestore.gif

h_onlinestore.gif

219 ms

h_staff.gif

h_staff.gif

165 ms

h_shoplist.gif

h_shoplist.gif

333 ms

h_mailmagazine.gif

h_mailmagazine.gif

333 ms

h_sns.gif

h_sns.gif

362 ms

top_news.gif

top_news.gif

359 ms

2016022915412203990_1.jpg

2016022915412203990_1.jpg

552 ms

2016021919231322832_1.jpg

2016021919231322832_1.jpg

550 ms

facebook.gif

facebook.gif

491 ms

punyus_app.gif

punyus_app.gif

493 ms

punyuskukuko_banner.jpg

punyuskukuko_banner.jpg

522 ms

top_zozotown.gif

top_zozotown.gif

522 ms

f_faq.png

f_faq.png

655 ms

f_privacy.gif

f_privacy.gif

656 ms

sdk.js

sdk.js

167 ms

copy.png

copy.png

714 ms

analytics.js

analytics.js

30 ms

rZeMs13ORug

rZeMs13ORug

108 ms

like_box.php

like_box.php

263 ms

collect

collect

26 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

85 ms

www-embed-player.js

www-embed-player.js

108 ms

73 ms

xd_arbiter.php

xd_arbiter.php

175 ms

xd_arbiter.php

xd_arbiter.php

258 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

37 ms

ad_status.js

ad_status.js

40 ms

4eLkuXhPSoa.css

4eLkuXhPSoa.css

201 ms

_NRPEwYtJf4.css

_NRPEwYtJf4.css

240 ms

hQmscEHMX7G.css

hQmscEHMX7G.css

283 ms

XI4oPVvuKf2.css

XI4oPVvuKf2.css

357 ms

vcQPCRI3o-G.css

vcQPCRI3o-G.css

370 ms

Rme9emFKEkh.css

Rme9emFKEkh.css

377 ms

4gbUYBc5YEH.css

4gbUYBc5YEH.css

320 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

391 ms

b94UUzHjapV.js

b94UUzHjapV.js

427 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

411 ms

TTCre3391I0.js

TTCre3391I0.js

413 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

413 ms

b_6HNn_J2BZ.js

b_6HNn_J2BZ.js

414 ms

6kb4qPGfoPa.js

6kb4qPGfoPa.js

460 ms

ezSeJz80WmZ.js

ezSeJz80WmZ.js

520 ms

B9x7unvN8Hn.js

B9x7unvN8Hn.js

476 ms

OCkothPJhqg.js

OCkothPJhqg.js

476 ms

D6JJJzT-tB6.js

D6JJJzT-tB6.js

469 ms

hQyBJD7FRta.js

hQyBJD7FRta.js

475 ms

ThxFh2GztJe.js

ThxFh2GztJe.js

478 ms

_UYztdBNTjs.js

_UYztdBNTjs.js

482 ms

VpVLc1dkyZp.js

VpVLc1dkyZp.js

568 ms

DULOQLY-aiv.js

DULOQLY-aiv.js

513 ms

-AWXRi4rrMJ.js

-AWXRi4rrMJ.js

517 ms

11889456_1018060481559726_431318609425389690_n.jpg

11889456_1018060481559726_431318609425389690_n.jpg

204 ms

safe_image.php

safe_image.php

199 ms

10171013_737254829640294_1873142059_n.jpg

10171013_737254829640294_1873142059_n.jpg

234 ms

12717319_1116255008406939_5232228162685724889_n.jpg

12717319_1116255008406939_5232228162685724889_n.jpg

314 ms

12743698_1114118348620605_23802195632794233_n.jpg

12743698_1114118348620605_23802195632794233_n.jpg

313 ms

12402681_1099762583388017_375375278_n.jpg

12402681_1099762583388017_375375278_n.jpg

315 ms

12651100_1105059019526538_6187785017196483627_n.jpg

12651100_1105059019526538_6187785017196483627_n.jpg

351 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

137 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

139 ms

GkQW5XA9c-c.png

GkQW5XA9c-c.png

137 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

137 ms

aeO1ik7i7-T.png

aeO1ik7i7-T.png

265 ms

Fl1c2TVhCj-.png

Fl1c2TVhCj-.png

137 ms

bNvHN6v1NeH.png

bNvHN6v1NeH.png

138 ms

b53Ajb4ihCP.gif

b53Ajb4ihCP.gif

144 ms

sOQnlBB68lt.png

sOQnlBB68lt.png

138 ms

tIFXiEZJgab.js

tIFXiEZJgab.js

44 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

41 ms

f6T91Deal_q.js

f6T91Deal_q.js

54 ms

Accessibility Review

punyus.jp accessibility score

62

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

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

punyus.jp SEO score

86

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

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

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

punyus.jp

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