Access pinkhouse-webshop.jp. ピンクハウスオフィシャルオンラインストア

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.768

5/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

pinkhouse-webshop.jp

1599 ms

26.css

836 ms

smartrollover.js

333 ms

AJS.js

697 ms

AJS_fx.js

563 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 96% of them (93 requests) were addressed to the original Pinkhouse-webshop.jp, 2% (2 requests) were made to Sec.wisecart.ne.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Sec.wisecart.ne.jp.

Content Size

938.2 kB

After Optimization

571.6 kB

In fact, the total size of Pinkhouse-webshop.jp main page is 938.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. 20% of websites need less resources to load. Images take 473.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 53.6 kB

Original 60.2 kB
After minification 31.2 kB
After compression 6.6 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 29.0 kB, which is 48% 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 53.6 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 32.1 kB

Original 473.2 kB
After minification 441.1 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. PINK HOUSE Webshop images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 250.8 kB

Original 370.5 kB
After minification 321.5 kB
After compression 119.7 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 250.8 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 30.0 kB

Original 34.3 kB
After minification 23.6 kB
After compression 4.2 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. Pinkhouse-webshop.jp needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 88% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pinkhouse-webshop.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pinkhouse-webshop.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

pinkhouse-webshop.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

ピンクハウスオフィシャルオンラインストア｜PINK HOUSE OFFICIAL ONLINE STORE

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

pinkhouse-webshop.jp

26.css

smartrollover.js

AJS.js

AJS_fx.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

pinkhouse-webshop.jp

26.css

smartrollover.js

AJS.js

AJS_fx.js

gb_scripts.js

gb_styles.css

mootools.js

slimbox.js

slimbox.css

encoding.js

wc_log.js

top.gif

mail_off.gif

size_off.gif

guide_off.gif

inquiry_off.gif

top_side.gif

search.gif

login_off.gif

mypage_off.gif

shoppingcart_off.gif

201604_ib_fair2.jpg

chelsea.jpg

201512_%E5%A4%A7%E5%80%89%E9%99%B6%E5%9C%92_icon.jpg

IB_COLLABO.jpg

NEGRIN.jpg

brandlist.gif

pinkhouse_off.gif

ingeborg_off.gif

phbasic_off.gif

PHchelsea_off.gif

karlhelmut_off.gif

happySET.jpg

fuwamoko.jpg

item_list.gif

item_mk.gif

catarogue_PH.gif

catalogue_ib.gif

catarogue_KH.gif

links.gif

pinkhouseJP_off.gif

fb-ph.gif