14.8 sec in total
1.2 sec
13.2 sec
401 ms
Welcome to hairwork.jp homepage info - get ready to check Hairwork best content right away, or after learning these important things about hairwork.jp
増毛の専門店ヘアーワーク(東京・池袋)では1本20円の増毛から、かつらや女性用ウィッグ・育毛までお客様の頭髪に関してのお悩みを高い技術力でサポートさせて頂いております。
Visit hairwork.jpWe analyzed Hairwork.jp page load time and found that the first response time was 1.2 sec and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hairwork.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.5 s
37/100
25%
Value7.4 s
27/100
10%
Value40 ms
100/100
30%
Value0.329
35/100
15%
Value7.8 s
44/100
10%
1224 ms
349 ms
354 ms
29 ms
1037 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 95% of them (99 requests) were addressed to the original Hairwork.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Hairwork.jp.
Page size can be reduced by 227.1 kB (9%)
2.7 MB
2.4 MB
In fact, the total size of Hairwork.jp main page is 2.7 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. 25% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 25.0 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 25.0 kB or 76% of the original size.
Potential reduce by 112.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. Hairwork images are well optimized though.
Potential reduce by 35.9 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 35.9 kB or 61% of the original size.
Potential reduce by 53.8 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. Hairwork.jp needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 85% of the original size.
Number of requests can be reduced by 11 (11%)
103
92
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hairwork. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hairwork.jp
1224 ms
styles.css
349 ms
smartRollover.js
354 ms
jquery.min.js
29 ms
jquery.flexslider.js
1037 ms
oritatami.js
441 ms
blog.css
516 ms
hw_top.css
698 ms
hw_page.css
809 ms
gnavi.css
510 ms
flexslider.css
652 ms
jquery.lightbox.css
862 ms
hw_top.css
835 ms
header_back.jpg
347 ms
header_logo-thumb-450x60-1.jpg
697 ms
spacer-thumb-1x1-2.png
992 ms
header_info.jpg
613 ms
header_bt_off.jpg
623 ms
gnavi01_off.jpg
781 ms
gnavi02_off.jpg
978 ms
gnavi03_off.jpg
974 ms
gnavi04_off.jpg
1335 ms
gnavi05_off.jpg
1177 ms
gnavi06_off.jpg
1177 ms
top_katsura_off.jpg
2682 ms
top_jq05.jpg
3082 ms
top_jq01.jpg
3331 ms
top_jq02.jpg
3356 ms
zm_top01.jpg
1957 ms
zm_top02.jpg
2257 ms
zm_top_back01.jpg
2378 ms
zm_top_bt01_off.jpg
2771 ms
zm_top_back02.jpg
3207 ms
zm_top_bt02_off.jpg
3055 ms
zm_top_bar.jpg
3315 ms
main_info_back.jpg
4625 ms
main_info_bt_off.jpg
3866 ms
side_begin_off.jpg
4188 ms
side_jirei_off.jpg
4408 ms
side_blog.jpg
4160 ms
dotline.png
3748 ms
main_qa_bt_off.jpg
4144 ms
main_blog_bt_off.jpg
4233 ms
side_menu.jpg
4707 ms
side_list10_off.jpg
4817 ms
side_list11_off.jpg
4810 ms
side_list12_off.jpg
4655 ms
side_list13_off.jpg
4738 ms
ga.js
9 ms
__utm.gif
10 ms
side_list14_off.jpg
4875 ms
beacon.gif
171 ms
side_list15_off.jpg
4425 ms
side_list20_off.jpg
4652 ms
side_list21_off.jpg
4680 ms
side_list22_off.jpg
4618 ms
side_list23_off.jpg
4411 ms
side_list24_off.jpg
4482 ms
side_list25_off.jpg
4591 ms
side_list30_off.jpg
4874 ms
side_list31_off.jpg
4472 ms
side_list32_off.jpg
4758 ms
166 ms
side_list33_off.jpg
4689 ms
side_list34_off.jpg
4090 ms
side_list35_off.jpg
3654 ms
side_list40_off.jpg
4056 ms
side_list41_off.jpg
3790 ms
side_list42_off.jpg
3712 ms
side_list43_off.jpg
3482 ms
side_list44_off.jpg
3598 ms
side_list45_off.jpg
3231 ms
side_list50_off.jpg
3711 ms
side_list51_off.jpg
3731 ms
side_list52_off.jpg
3515 ms
side_list53_off.jpg
3140 ms
side_list54_off.jpg
3264 ms
side_list55_off.jpg
2898 ms
side_list60_off.jpg
3258 ms
side_list61_off.jpg
3324 ms
side_list62_off.jpg
3214 ms
side_list63_off.jpg
3020 ms
side_list64_off.jpg
2837 ms
side_list65_off.jpg
2881 ms
side_women02_off.jpg
3565 ms
side_deal_off.jpg
3208 ms
side_mr_off.jpg
3238 ms
side_zero_off.jpg
3484 ms
side_shop.jpg
3263 ms
side_honten.jpg
3093 ms
dotline295.jpg
3145 ms
side_gj_off.jpg
3631 ms
footer_jirei.jpg
4634 ms
main_zoumou_off.gif
3276 ms
footer_jirei01_off.jpg
3230 ms
main_wig_off.gif
3167 ms
footer_jirei02_off.jpg
3132 ms
main_care_off.gif
3153 ms
footer_jirei03_off.jpg
3144 ms
footer_navi_back.jpg
3478 ms
footer_navi_title.png
3933 ms
footer_info.jpg
3728 ms
bg_control_nav.png
187 ms
bg_direction_nav.png
1277 ms
hairwork.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
hairwork.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
hairwork.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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hairwork.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 Hairwork.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.
hairwork.jp
Open Graph description is not detected on the main page of Hairwork. 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: