13.7 sec in total
560 ms
12.6 sec
545 ms
Welcome to harney.jp homepage info - get ready to check HARNEY best content for Japan right away, or after learning these important things about harney.jp
【ハーニーアンドサンズ公式オンラインショップ】ニューヨーク発プレミアムティーブランドHARNEY & SONS。NY直営工場から最新の商品を常時入荷!公式サイト限定商品も多数展開!
Visit harney.jpWe analyzed Harney.jp page load time and found that the first response time was 560 ms and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
harney.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value17.2 s
0/100
25%
Value27.7 s
0/100
10%
Value5,540 ms
0/100
30%
Value1.774
0/100
15%
Value32.1 s
0/100
10%
560 ms
569 ms
1307 ms
1311 ms
518 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 7% of them (13 requests) were addressed to the original Harney.jp, 47% (86 requests) were made to Gigaplus.makeshop.jp and 14% (25 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Gigaplus.makeshop.jp.
Page size can be reduced by 475.1 kB (9%)
5.0 MB
4.6 MB
In fact, the total size of Harney.jp main page is 5.0 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. 65% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 61.4 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 61.4 kB or 78% of the original size.
Potential reduce by 151.7 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. HARNEY images are well optimized though.
Potential reduce by 160.7 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 160.7 kB or 67% of the original size.
Potential reduce by 101.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. Harney.jp needs all CSS files to be minified and compressed as it can save up to 101.2 kB or 84% of the original size.
Number of requests can be reduced by 92 (52%)
177
85
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HARNEY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
harney.jp
560 ms
m_sys_common.css
569 ms
import.css
1307 ms
script.js
1311 ms
jquery.bxslider.css
518 ms
flexslider.css
518 ms
css
68 ms
jquery-1.8.2.min.js
690 ms
jquery.flexslider-min.js
543 ms
jquery.simpleTicker.js
546 ms
jquery.bxslider.min.js
547 ms
jquery.event.hover.js
679 ms
jquery.megamenu.js
681 ms
heightLine.js
719 ms
jquery.pagination.js
724 ms
jTabs.js
726 ms
easyselectbox.min.js
843 ms
bace.js
844 ms
sideFixed.js
851 ms
check_history.css
334 ms
pager.css
332 ms
shopdetail.css
336 ms
ranking.css
334 ms
basket.css
339 ms
security.css
354 ms
category_menu.css
660 ms
topicpath.css
662 ms
catalog.css
675 ms
analytics.js
35 ms
logo.png
183 ms
cartBtn_off.png
167 ms
soBtn01_off.png
178 ms
soBtn02_off.png
169 ms
soBtn03_off.png
166 ms
hs160312_1.jpg
919 ms
mainImg04.jpg
2006 ms
ban_paris.jpg
1326 ms
mainImg01_02.jpg
1171 ms
mainImg02.jpg
7458 ms
mainImg03.jpg
4556 ms
newsTi.png
1102 ms
ban_pic_wrapping.jpg
1474 ms
ban_pic_event_2_3.jpg
1348 ms
hs_seasonal_financier_2.jpg
1658 ms
ban_pickup_3.jpg
1682 ms
ban_pic_nagoya.jpg
1837 ms
hs160309_ooo.jpg
1825 ms
hs160309_oo.jpg
1851 ms
hs160312_2.jpg
2995 ms
catTi.png
2027 ms
catImg01.png
2031 ms
catImg02.png
2180 ms
catImg03.png
2395 ms
catImg04.png
2207 ms
catImg05.png
2348 ms
catImg06.png
2387 ms
catImg07.png
2516 ms
catImg08.png
2563 ms
teaListImg01.jpg
2757 ms
teaListImg02.jpg
3401 ms
teaListImg03.jpg
2743 ms
teaListImg04.jpg
2913 ms
teaListImg05.jpg
3304 ms
teaListImg06.jpg
3083 ms
topMenuImg01.jpg
3505 ms
sdk.js
279 ms
aq_tag_aos.js
158 ms
437 ms
collect
45 ms
collect
90 ms
JzRrPKdwEnE8F1TDmDLMUhxcROG_7vu2ubkyRjqgeRY.ttf
46 ms
topMenuImg02.jpg
3095 ms
topMenuImg03.jpg
3264 ms
rankTi.png
3323 ms
EM34BYVZ46DUGEQNJE6A
135 ms
rankImg01.png
3939 ms
H-005-0016_HotCinnamonGiftSet.jpg
3433 ms
60 ms
xd_arbiter.php
221 ms
xd_arbiter.php
433 ms
gmsync
296 ms
segmentation.js
79 ms
300 ms
cnt
357 ms
H-002-0002_WWEarlGrey_main.jpg
2936 ms
rankImg06.png
2574 ms
rankImg05.png
3777 ms
flagTi.png
3521 ms
flagshipImg01.jpg
3415 ms
flag-cinnamon.jpg
2981 ms
flagshipImg02.jpg
5779 ms
flag-paris.jpg
3247 ms
newsTi2.png
3119 ms
guideTi.png
3175 ms
card.png
3260 ms
fBnr01.png
3123 ms
fBnr02.png
3252 ms
followTi.png
3146 ms
pageTop.png
3113 ms
headerBg.png
3100 ms
gnavi01_off.png
2994 ms
gnavi02_off.png
3059 ms
gnavi03_off.png
3081 ms
gnavi04_off.png
2973 ms
gnavi05_off.png
2944 ms
searchBtn.png
2868 ms
rankBg.png
2908 ms
rLabel.png
2763 ms
g_arrow.png
2679 ms
maru.png
2697 ms
bx_loader.gif
2591 ms
f_prev.png
2536 ms
f_next.png
2459 ms
beacon.html
150 ms
prev.png
327 ms
next.png
827 ms
page.php
252 ms
pixel
17 ms
cs
297 ms
Pug
21 ms
set
302 ms
sd
4 ms
tap.php
4 ms
pixel
15 ms
sync
11 ms
sync
381 ms
hQThvcX2PmE.css
282 ms
t3u7Vo4PVNb.css
377 ms
7AWqDdXAHeD.css
445 ms
0phBHPJ2e_-.css
567 ms
SLxnvG7M_YW.css
494 ms
EMZLZpchgDl.css
488 ms
yr3ddLX9-yj.css
553 ms
q68gy-v_YMF.js
618 ms
ehA1CqzHyzE.js
643 ms
0wM5s1Khldu.js
570 ms
1bNoFZUdlYZ.js
570 ms
njO1TPvGzoR.js
633 ms
1QuX41zDRrx.js
633 ms
Oagsvfb4VWi.js
691 ms
LTv6ZK-5zxz.js
829 ms
1FCa-btixu2.js
683 ms
DVtj8v6ogQI.js
690 ms
IjqSyiwKeaX.js
697 ms
n6VgtouijQL.js
711 ms
mapuser
149 ms
sync
248 ms
sync
261 ms
972344_430869790361725_290737721_n.jpg
468 ms
safe_image.php
359 ms
safe_image.php
421 ms
safe_image.php
554 ms
safe_image.php
621 ms
safe_image.php
622 ms
1001104_430865707028800_1166236893_n.png
601 ms
10419379_1037135776349739_3809328631042585265_n.jpg
665 ms
563301_867213786734449_1022949842920362614_n.jpg
666 ms
10891680_437717406378940_9168783640278857416_n.jpg
663 ms
11951313_692829167516556_7824062510220181687_n.jpg
668 ms
321190_140831952691337_553792938_n.jpg
666 ms
12524031_872327489551936_7224172610514861276_n.jpg
669 ms
1379841_10150004552801901_469209496895221757_n.jpg
730 ms
10405459_607968312646808_8754325430129007537_n.jpg
731 ms
1229880_1399663713623810_1945906479_n.jpg
734 ms
254322_160110907390166_1767328_n.jpg
733 ms
12508890_910093342401829_346330065188756551_n.jpg
733 ms
10374876_1020486944664450_6477502345913948807_n.jpg
736 ms
1001104_430865707028800_1166236893_n.png
864 ms
1916715_917055578409808_7018690466788736076_n.png
1200 ms
11988662_917055585076474_7057964174523868127_n.png
1024 ms
10325787_917055581743141_6188972406258225743_n.png
1202 ms
10455918_916900785091954_17533250282868130_n.jpg
953 ms
12096625_916900748425291_1109616448182053191_n.jpg
801 ms
10373819_916900751758624_3187903456733082676_n.jpg
1053 ms
1932290_916901075091925_8904551636484361607_n.jpg
990 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
78 ms
K00K-UgnsKu.png
79 ms
QDwYpIaRyfG.png
79 ms
50 ms
I6-MnjEovm5.js
70 ms
pQrUxxo5oQp.js
135 ms
harney.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-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
harney.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
harney.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
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Harney.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 Harney.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
harney.jp
Open Graph description is not detected on the main page of HARNEY. 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: