13.1 sec in total
526 ms
11.3 sec
1.3 sec
Welcome to harold-frosch.jp homepage info - get ready to check Harold Frosch best content right away, or after learning these important things about harold-frosch.jp
メンズ・ファッション・ブランド≪Harold Frosch≫直営の通販|飾らずに生きる大人の男の服|Made in Japan
Visit harold-frosch.jpWe analyzed Harold-frosch.jp page load time and found that the first response time was 526 ms and then it took 12.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.
harold-frosch.jp performance score
526 ms
700 ms
336 ms
1267 ms
73 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 69% of them (62 requests) were addressed to the original Harold-frosch.jp, 22% (20 requests) were made to Image1.shopserve.jp and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (8.8 sec) relates to the external source Image1.shopserve.jp.
Page size can be reduced by 1.4 MB (21%)
6.6 MB
5.2 MB
In fact, the total size of Harold-frosch.jp main page is 6.6 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. 20% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 53.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 9.0 kB, which is 14% 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 82% of the original size.
Potential reduce by 345.8 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. Harold Frosch images are well optimized though.
Potential reduce by 60.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 60.2 kB or 65% of the original size.
Potential reduce by 917.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. Harold-frosch.jp needs all CSS files to be minified and compressed as it can save up to 917.2 kB or 88% of the original size.
Number of requests can be reduced by 13 (15%)
87
74
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Harold Frosch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
harold-frosch.jp
526 ms
www.harold-frosch.jp
700 ms
sps_common.css
336 ms
default.css
1267 ms
jquery.min.js
73 ms
jquery.tile.js
353 ms
jquery.distile.js
362 ms
jquery.slider.min.js
379 ms
jquery.colorbox-min.js
506 ms
colorbox.css
684 ms
jquery.slider.css
690 ms
item_style.css
709 ms
pcsmpflg.js
726 ms
cal.js
692 ms
analytics.js
22 ms
OP008J24_309.jpg
2120 ms
logo.jpg
664 ms
gnav_all.jpg
336 ms
gnav_jacket.jpg
357 ms
gnav_shirt.jpg
358 ms
gnav_pants.jpg
360 ms
gnav_polo.jpg
374 ms
gnav_cut.jpg
672 ms
gnav_others.jpg
719 ms
gnav_outlet.jpg
708 ms
slide_11-50.jpg
2042 ms
slide_03-50.jpg
1765 ms
slide_12-50.jpg
1994 ms
slide_07-50.jpg
2143 ms
slide_13-50.jpg
2159 ms
slide_14-50.jpg
2157 ms
slide_15-50.jpg
3270 ms
snav_allitems.jpg
2346 ms
snav_jacket2.jpg
2712 ms
snav_shirt2.jpg
2488 ms
snav_pants2.jpg
2523 ms
snav_polo2.jpg
2528 ms
snav_cut2.jpg
2672 ms
snav_others.jpg
2857 ms
snav_outlet.jpg
2869 ms
bnr_freesipping.jpg
3278 ms
bnr_new.jpg
3333 ms
wellcome.jpg
3675 ms
t_item_zig.jpg
3519 ms
t_item_couturejk.jpg
3557 ms
t_item_suvindigger.jpg
3985 ms
t_item_airdigger.jpg
4019 ms
t_item_stritch.jpg
3996 ms
t_item_camp.jpg
4209 ms
t_item_johnspolo.jpg
4243 ms
t_item_crispypants.jpg
4424 ms
HFC-NP002C-8-1.jpg
1806 ms
HFS-NP001S-9.jpg
1559 ms
OP005T49_398.jpg
1578 ms
OP009J29_319.jpg
1374 ms
HFV-NP003V-7-1.jpg
1835 ms
OP006S12_329.jpg
3046 ms
OP005T33_389.jpg
3135 ms
HFJ-NP003J-1.jpg
3319 ms
HFR-NP001R-9-1.jpg
3468 ms
HFS-NP002S-1.jpg
3360 ms
OP004U33_410.jpg
3975 ms
HFJ-NP003J-10.jpg
8801 ms
HFR-NP004R-8-1.jpg
4820 ms
OP007G24_364.jpg
5331 ms
OP004U49_413.jpg
5189 ms
C-NA006C26R_157.jpg
5498 ms
OP004U29_407.jpg
5653 ms
OP007G12_356.jpg
6508 ms
HFU-NP002U-1.jpg
7044 ms
t_item_piercespolo.jpg
4701 ms
linkid.js
92 ms
ec.js
94 ms
collect
14 ms
tracking.php
944 ms
collect
33 ms
collect
65 ms
mijapan.jpg
4410 ms
icon_new.png
4024 ms
fb_icon.jpg
4228 ms
tw_icon.jpg
4386 ms
hate_icon.jpg
4366 ms
gp_icon.jpg
4127 ms
copyright.jpg
4270 ms
pagetop.gif
4337 ms
bg_gnav.jpg
4389 ms
icon_home_pkz.png
3342 ms
end_cart.png
3113 ms
bg_top_img.jpg
3128 ms
bg_footer.jpg
3172 ms
harold-frosch.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Harold-frosch.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 Harold-frosch.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.
harold-frosch.jp
Open Graph description is not detected on the main page of Harold Frosch. 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: