Tools & Wizards About Us
punyus.jp screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

punyus.jp

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

Page Load Speed

4.2 sec in total

First Response

359 ms

Resources Loaded

3.3 sec

Page Rendered

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

Performance Metrics

punyus.jp performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.384

27/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

punyus.jp

359 ms

punyus.jp

636 ms

gtm.js

116 ms

reset.css.gz

82 ms

common.css.gz

90 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Punyus.jp, 36% (26 requests) were made to Cdn.thumb.punyus.jp and 31% (22 requests) were made to Cdn.img.punyus.jp. The less responsive or slowest element that took the longest time to load (895 ms) relates to the external source Jmp.c-rings.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.3 kB (8%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Punyus.jp main page is 1.8 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 102.6 kB

  • Original 116.9 kB
  • After minification 116.1 kB
  • After compression 14.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 102.6 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 4.0 kB

  • Original 1.5 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. PUNYUS images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 28.6 kB

  • Original 143.2 kB
  • After minification 142.5 kB
  • After compression 114.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 28.6 kB or 20% of the original size.

CSS Optimization

-0%

Potential reduce by 74 B

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

Requests Breakdown

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

Requests Now

69

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

punyus.jp

punyus.jp

359 ms

punyus.jp

punyus.jp

636 ms

gtm.js

gtm.js

116 ms

reset.css.gz

reset.css.gz

82 ms

common.css.gz

common.css.gz

90 ms

common_parts.css.gz

common_parts.css.gz

108 ms

index.css.gz

index.css.gz

86 ms

product.css.gz

product.css.gz

84 ms

tabs.css.gz

tabs.css.gz

106 ms

visumo.css.gz

visumo.css.gz

96 ms

favo.css.gz

favo.css.gz

91 ms

element.js

element.js

96 ms

cr_effectLog-v21i.min.js

cr_effectLog-v21i.min.js

895 ms

ld.js

ld.js

85 ms

Wego.js

Wego.js

91 ms

top.js

top.js

693 ms

ecbn-selection-widget.js

ecbn-selection-widget.js

87 ms

jquery.min.js

jquery.min.js

80 ms

jquery.lazyload.min.js.gz

jquery.lazyload.min.js.gz

84 ms

core.js.gz

core.js.gz

96 ms

common2.js.gz

common2.js.gz

88 ms

jquery.ah-placeholder.js.gz

jquery.ah-placeholder.js.gz

92 ms

favo.js.gz

favo.js.gz

91 ms

script

script

86 ms

6jtUnz0xKth520095FS.js

6jtUnz0xKth520095FS.js

637 ms

product.js.gz

product.js.gz

97 ms

tabs.js.gz

tabs.js.gz

96 ms

cr_effectLog-v21i.min.js

cr_effectLog-v21i.min.js

243 ms

lt.js

lt.js

271 ms

fbevents.js

fbevents.js

166 ms

souryou_pchd0403.jpg

souryou_pchd0403.jpg

265 ms

logo.png

logo.png

118 ms

apppush_line_nove_1180___.jpg

apppush_line_nove_1180___.jpg

279 ms

samune.jpg

samune.jpg

278 ms

memberrank-bn-259x77.jpg

memberrank-bn-259x77.jpg

257 ms

virtusixe_pcft0322.jpg

virtusixe_pcft0322.jpg

269 ms

7fd1e973f1825bcd26044427a3b7ca45e446d2cf.jpg

7fd1e973f1825bcd26044427a3b7ca45e446d2cf.jpg

270 ms

PN24SS-105-20240723145342.gif

PN24SS-105-20240723145342.gif

269 ms

PN24SS-098-1-20240717161023.gif

PN24SS-098-1-20240717161023.gif

295 ms

PN24SS-098-2-20240725121423.gif

PN24SS-098-2-20240725121423.gif

273 ms

PN24SS-104-20240725122537.gif

PN24SS-104-20240725122537.gif

273 ms

PN24SS-103-20240725184520.gif

PN24SS-103-20240725184520.gif

283 ms

PN24SS-094-20240708193412.gif

PN24SS-094-20240708193412.gif

294 ms

PN24SS-087-20240708192412.gif

PN24SS-087-20240708192412.gif

285 ms

PN24SS-043-2-20240725124820.gif

PN24SS-043-2-20240725124820.gif

285 ms

PN24SS-097-20240709153608.gif

PN24SS-097-20240709153608.gif

295 ms

PN24SS-095-20240703111059.gif

PN24SS-095-20240703111059.gif

288 ms

watch_list.png

watch_list.png

143 ms

common_sprite.png

common_sprite.png

245 ms

top_merit_01.png

top_merit_01.png

142 ms

top_merit_02.png

top_merit_02.png

142 ms

form_parts.png

form_parts.png

142 ms

stars_small_2.png

stars_small_2.png

142 ms

x.js

x.js

410 ms

provision

provision

839 ms

syncframe

syncframe

161 ms

jquery.min.js

jquery.min.js

94 ms

err.gif

err.gif

699 ms

sv

sv

415 ms

event

event

670 ms

collectionx

collectionx

711 ms

uu

uu

298 ms

IMG_1252_.jpg

IMG_1252_.jpg

19 ms

9f7968405dee857a43e20be4ce26a76f7f7ee87d.jpg

9f7968405dee857a43e20be4ce26a76f7f7ee87d.jpg

12 ms

2023_0221_punyus4685.jpg

2023_0221_punyus4685.jpg

12 ms

a51256fdf11ae635afd08a88bc23e549282ffc71.jpg

a51256fdf11ae635afd08a88bc23e549282ffc71.jpg

18 ms

20240425yu234_.jpg

20240425yu234_.jpg

11 ms

16c03e1876430a61e1d01e274bcc0846cac6518c.jpg

16c03e1876430a61e1d01e274bcc0846cac6518c.jpg

20 ms

IMG_5439_2.jpg

IMG_5439_2.jpg

19 ms

singara.jpg

singara.jpg

15 ms

IMG_0550_2.jpg

IMG_0550_2.jpg

13 ms

6872e0ebb7d592a3326890cc93c446d97bc96b15.jpg

6872e0ebb7d592a3326890cc93c446d97bc96b15.jpg

18 ms

Accessibility Review

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

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

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

punyus.jp SEO score

86

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 doesn't use 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 data is detected on the main page of PUNYUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: