8.6 sec in total
528 ms
7.5 sec
519 ms
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 528 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pique.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value16.6 s
0/100
25%
Value14.6 s
1/100
10%
Value3,850 ms
1/100
30%
Value0.709
7/100
15%
Value17.0 s
4/100
10%
528 ms
869 ms
339 ms
501 ms
338 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 91% of them (82 requests) were addressed to the original Pique.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Pique.jp.
Page size can be reduced by 2.4 MB (42%)
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. 70% of websites need less resources to load. 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 328.2 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 328.2 kB or 72% 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 19 (22%)
86
67
The browser has sent 86 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 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pique.jp
528 ms
www.pique.jp
869 ms
import.css
339 ms
top.css
501 ms
default.css
338 ms
jquery.js
1870 ms
mobilyslider.js
515 ms
jquery-ui.min.js
8 ms
jquery.easing.js
514 ms
jquery.mousewheel.js
672 ms
ext.js
507 ms
smartRollover.js
670 ms
gotop.js
675 ms
yuga.js
688 ms
jquery.cycle.all.pack.js
860 ms
141.js
845 ms
reset.css
507 ms
common.css
835 ms
layout.css
527 ms
ga.js
385 ms
old-paper02.jpg
823 ms
iikoto.png
1585 ms
logo.png
395 ms
all.js
442 ms
icon_arrow_01.png
436 ms
shop_kari.png
1202 ms
h2_catch.png
437 ms
yakusoku_title_01.png
436 ms
yakusoku_pic_01.png
1197 ms
yakusoku_txt_01.png
1195 ms
yakusoku_pic_02.png
1197 ms
yakusoku_txt_02.png
1195 ms
yakusoku_pic_03.png
1201 ms
yakusoku_txt_03.png
1195 ms
yakusoku_pic_04.png
1199 ms
yakusoku_txt_04.png
1198 ms
yakusoku_pic_05.png
1941 ms
yakusoku_txt_05.png
1200 ms
yakusoku_pic_06.png
1940 ms
yakusoku_txt_06.png
1200 ms
yakusoku_pic_07.png
1938 ms
yakusoku_txt_07.png
1938 ms
yakusoku_pic_08.png
1940 ms
yakusoku_txt_08.png
1941 ms
yakusoku_pic_09.png
1943 ms
yakusoku_txt_09.png
1940 ms
h2_campaign.png
1941 ms
h2_hairstyle.png
1941 ms
h2_shopinfo.png
1941 ms
shop_pique2.jpg
1944 ms
shop_logo.gif
1942 ms
tel.gif
1942 ms
web.gif
1942 ms
webcontact_off.png
1942 ms
h2_salonmenu.png
1943 ms
course.png
1943 ms
standerd.png
1943 ms
__utm.gif
763 ms
bnr_gallery.png
1518 ms
bnr_recruit.png
1516 ms
bnr_blog.png
1515 ms
gnavi01_off.png
1517 ms
gnavi02_off.png
1514 ms
all.js
755 ms
gnavi03_off.png
757 ms
logo3_off.png
1170 ms
gnavi04_off.png
1176 ms
gnavi05_off.png
1177 ms
gnavi06_off.png
1174 ms
tsuta2.png
1679 ms
border690.gif
1174 ms
embed
444 ms
pic1.jpg
434 ms
price_off.png
608 ms
gal_off.png
604 ms
pic1.jpg
1427 ms
pic1.jpg
2242 ms
pic1.jpg
1253 ms
pic1.jpg
784 ms
pic1.jpg
1292 ms
shop_bak.png
960 ms
right_line.gif
1112 ms
left_line.gif
1137 ms
box_01a.gif
1289 ms
503 ms
bottom.png
892 ms
1000 ms
gotop3_off.png
1046 ms
layout.css
1041 ms
js
68 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: