4.6 sec in total
713 ms
3.5 sec
333 ms
Click here to check amazing Piu E content. Otherwise, check out these important facts you probably never knew about piuepiu.jp
マツオインターナショナルが展開するショップブランド「Piu e Piu (ピュウ エ ピュウ)」のサイトです。
Visit piuepiu.jpWe analyzed Piuepiu.jp page load time and found that the first response time was 713 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 60% of websites can load faster.
piuepiu.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value10.5 s
0/100
25%
Value19.4 s
0/100
10%
Value30 ms
100/100
30%
Value0.225
55/100
15%
Value10.5 s
24/100
10%
713 ms
321 ms
347 ms
1178 ms
509 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 56% of them (40 requests) were addressed to the original Piuepiu.jp, 32% (23 requests) were made to Static.xx.fbcdn.net and 7% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Piuepiu.jp.
Page size can be reduced by 132.7 kB (11%)
1.2 MB
1.1 MB
In fact, the total size of Piuepiu.jp main page is 1.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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 3.8 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 811 B, which is 15% 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 3.8 kB or 72% of the original size.
Potential reduce by 50.4 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. Piu E images are well optimized though.
Potential reduce by 69.1 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 69.1 kB or 66% of the original size.
Potential reduce by 9.5 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. Piuepiu.jp needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 79% of the original size.
Number of requests can be reduced by 28 (39%)
71
43
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Piu E. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
piuepiu.jp
713 ms
import.css
321 ms
top.css
347 ms
jquery-1.8.3.min.js
1178 ms
yuga.js
509 ms
mv.js
349 ms
default.css
181 ms
util.css
159 ms
common.css
196 ms
bg.gif
182 ms
bg_left.gif
183 ms
bg_right.gif
170 ms
bg.png
173 ms
logo.png
161 ms
bg.png
173 ms
nav1.png
326 ms
nav2.png
343 ms
nav3.png
346 ms
sns_title.png
347 ms
facebook_btn.png
357 ms
twitter_btn.png
360 ms
instagram_btn.png
564 ms
img2.jpg
1717 ms
img3.jpg
1684 ms
img1.jpg
1230 ms
bg.png
701 ms
title.png
702 ms
bg.png
770 ms
twitter_title.png
771 ms
twitter_btn.png
915 ms
fb_title.png
918 ms
fb_btn.png
917 ms
bg.png
1267 ms
title.png
1092 ms
btn.png
1070 ms
bg.png
1229 ms
copyright.png
1271 ms
nav1_on.png
1402 ms
nav2_on.png
1390 ms
nav3_on.png
1455 ms
likebox.php
287 ms
410ucuAGgaJ.css
92 ms
tSbl8xBI27R.css
113 ms
Czh0gDTFcBt.css
135 ms
Ek6lpayKeeB.css
172 ms
EoarYgA68t4.css
191 ms
6fhPFsydUm0.css
160 ms
q68gy-v_YMF.js
212 ms
FJmpeSpHpjS.js
211 ms
0wM5s1Khldu.js
157 ms
1bNoFZUdlYZ.js
210 ms
njO1TPvGzoR.js
210 ms
1QuX41zDRrx.js
268 ms
Oagsvfb4VWi.js
275 ms
LTv6ZK-5zxz.js
283 ms
1FCa-btixu2.js
280 ms
12507473_447488712118503_6635117059044393251_n.jpg
269 ms
safe_image.php
693 ms
safe_image.php
326 ms
safe_image.php
732 ms
1934383_447488768785164_5174008985622530665_n.jpg
255 ms
12742420_462228853977822_8371854477437475378_n.jpg
447 ms
12745980_460026207531420_2230997568427428129_n.jpg
314 ms
12717264_460026220864752_530719234844292177_n.jpg
366 ms
wL6VQj7Ab77.png
218 ms
s7jcwEQH7Sx.png
217 ms
QijIVO3ZIrO.png
218 ms
waRE02Xq1bm.png
216 ms
QDwYpIaRyfG.png
216 ms
K00K-UgnsKu.png
217 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
29 ms
piuepiu.jp accessibility score
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
piuepiu.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
piuepiu.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piuepiu.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 Piuepiu.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.
piuepiu.jp
Open Graph description is not detected on the main page of Piu E. 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: