11.1 sec in total
602 ms
8.5 sec
2 sec
Click here to check amazing Pique content. Otherwise, check out these important facts you probably never knew about pique.jp
あなたらしさを引き出し、気分まで軽やかになれる美容室。最新の東京ヘアスタイルを静岡県浜松市中区鴨江で感じることのできるオンリーワンの美容室です。浜松で愛される美容室になるため、しっかりとしたカウンセリングと寛ぎの店内で、スタイリストが「髪にイイコト」をおすすめします。
Visit pique.jpWe analyzed Pique.jp page load time and found that the first response time was 602 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pique.jp performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value16.4 s
0/100
25%
Value14.6 s
1/100
10%
Value2,010 ms
7/100
30%
Value0.709
7/100
15%
Value15.4 s
7/100
10%
602 ms
879 ms
440 ms
598 ms
367 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 81% of them (82 requests) were addressed to the original Pique.jp, 9% (9 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Pique.jp.
Page size can be reduced by 2.4 MB (41%)
5.8 MB
3.4 MB
In fact, the total size of Pique.jp main page is 5.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 35.1 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 35.1 kB or 79% of the original size.
Potential reduce by 2.0 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. Obviously, Pique needs image optimization as it can save up to 2.0 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 329.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 329.1 kB or 65% of the original size.
Potential reduce by 38.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. Pique.jp needs all CSS files to be minified and compressed as it can save up to 38.0 kB or 83% of the original size.
Number of requests can be reduced by 29 (30%)
97
68
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pique. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
pique.jp
602 ms
www.pique.jp
879 ms
import.css
440 ms
top.css
598 ms
default.css
367 ms
jquery.js
2067 ms
mobilyslider.js
632 ms
jquery-ui.min.js
16 ms
jquery.easing.js
517 ms
jquery.mousewheel.js
732 ms
ext.js
614 ms
smartRollover.js
696 ms
gotop.js
780 ms
yuga.js
964 ms
jquery.cycle.all.pack.js
997 ms
141.js
873 ms
reset.css
498 ms
common.css
710 ms
layout.css
626 ms
ga.js
450 ms
all.js
460 ms
old-paper02.jpg
460 ms
iikoto.png
3229 ms
logo.png
458 ms
icon_arrow_01.png
417 ms
shop_kari.png
422 ms
h2_catch.png
418 ms
yakusoku_title_01.png
417 ms
yakusoku_pic_01.png
2739 ms
yakusoku_txt_01.png
418 ms
yakusoku_pic_02.png
2752 ms
yakusoku_txt_02.png
420 ms
yakusoku_pic_03.png
2751 ms
yakusoku_txt_03.png
1444 ms
yakusoku_pic_04.png
1445 ms
yakusoku_txt_04.png
2704 ms
yakusoku_pic_05.png
2753 ms
yakusoku_txt_05.png
2755 ms
yakusoku_pic_06.png
2756 ms
yakusoku_txt_06.png
2754 ms
yakusoku_pic_07.png
2759 ms
yakusoku_txt_07.png
2760 ms
yakusoku_pic_08.png
2768 ms
yakusoku_txt_08.png
2766 ms
yakusoku_pic_09.png
2764 ms
yakusoku_txt_09.png
2765 ms
h2_campaign.png
2767 ms
h2_hairstyle.png
2774 ms
h2_shopinfo.png
2772 ms
shop_pique2.jpg
2778 ms
shop_logo.gif
2776 ms
tel.gif
2776 ms
web.gif
2775 ms
webcontact_off.png
2775 ms
h2_salonmenu.png
2777 ms
course.png
2777 ms
standerd.png
2777 ms
bnr_gallery.png
2779 ms
bnr_recruit.png
2370 ms
bnr_blog.png
2370 ms
gnavi01_off.png
2369 ms
gnavi02_off.png
2371 ms
gnavi03_off.png
2371 ms
logo3_off.png
2369 ms
__utm.gif
901 ms
all.js
2208 ms
gnavi04_off.png
1404 ms
gnavi05_off.png
1843 ms
embed
594 ms
gnavi06_off.png
587 ms
tsuta2.png
569 ms
border690.gif
553 ms
pic1.jpg
1071 ms
price_off.png
551 ms
gal_off.png
550 ms
pic1.jpg
812 ms
pic1.jpg
1830 ms
pic1.jpg
1803 ms
pic1.jpg
707 ms
pic1.jpg
724 ms
shop_bak.png
953 ms
right_line.gif
952 ms
left_line.gif
952 ms
box_01a.gif
1094 ms
bottom.png
587 ms
595 ms
gotop3_off.png
1298 ms
layout.css
1275 ms
js
202 ms
125 ms
gen_204
25 ms
init_embed.js
58 ms
common.js
20 ms
util.js
51 ms
streetview.js
87 ms
marker.js
86 ms
imagery_viewer.js
27 ms
controls.js
18 ms
AuthenticationService.Authenticate
117 ms
css
620 ms
css
625 ms
pique.jp accessibility score
ARIA
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.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
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.
pique.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pique.jp SEO score
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pique.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 Pique.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.
pique.jp
Open Graph description is not detected on the main page of Pique. 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: