5 sec in total
916 ms
3.8 sec
253 ms
Visit hishidai.co.jp now to see the best up-to-date Hishidai content and also check out these interesting facts you probably never knew about hishidai.co.jp
ほうじ茶といえば、ひしだい製茶。職人による昔ながらの炭火焙煎ほうじ茶は、甘みがあり品のよい味わいです。お茶どころ静岡に工場を構え、ほうじ茶やその他日本茶の製造・卸を行っています。
Visit hishidai.co.jpWe analyzed Hishidai.co.jp page load time and found that the first response time was 916 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
hishidai.co.jp performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value3.6 s
61/100
25%
Value5.2 s
59/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
87/100
10%
916 ms
340 ms
1346 ms
508 ms
508 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Hishidai.co.jp, 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Hishidai.co.jp.
Page size can be reduced by 98.1 kB (16%)
630.7 kB
532.6 kB
In fact, the total size of Hishidai.co.jp main page is 630.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 486.7 kB which makes up the majority of the site volume.
Potential reduce by 12.3 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 12.3 kB or 74% of the original size.
Potential reduce by 11.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. Hishidai images are well optimized though.
Potential reduce by 64.5 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 64.5 kB or 56% of the original size.
Potential reduce by 9.6 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. Hishidai.co.jp needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 76% of the original size.
Number of requests can be reduced by 3 (5%)
57
54
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hishidai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
hishidai.co.jp
916 ms
import.css
340 ms
jquery1.5.1.js
1346 ms
common.js
508 ms
swfobject.js
508 ms
base.css
172 ms
common.css
335 ms
top_footerlogo.gif
510 ms
top_footercorp_photo.png
1520 ms
copyright.gif
512 ms
bodybg.gif
173 ms
logo.gif
174 ms
arrow_icon.gif
171 ms
main-visual.jpg
669 ms
topcontentbg.gif
172 ms
topaboutbg.png
845 ms
top_navi_lineup.gif
342 ms
top_navi_icon.gif
342 ms
top_navi_aboutus.gif
343 ms
top_navi_recruit.gif
343 ms
top_navi_factory.gif
510 ms
top_navi_img4.jpg
679 ms
top_navi_img1.jpg
680 ms
top_navi_img2.jpg
512 ms
top_navi_img0.jpg
679 ms
top_navi_img5.jpg
851 ms
toplineup_h.gif
837 ms
toplineup_1.gif
852 ms
toplineup_2.gif
851 ms
toplineup_3.gif
852 ms
toplineup_4.gif
1007 ms
toplineup_5.gif
1014 ms
toplineup_8.gif
1020 ms
houjicomlink.jpg
1019 ms
youtubelink.jpg
1021 ms
top_iritate.jpg
1022 ms
bnr-yahoo.jpg
1175 ms
bnr-rakuten.jpg
1184 ms
topnews_h.gif
1191 ms
topnews_icon1_news.gif
1190 ms
top_sampleinq.gif
1191 ms
topfooterbg.gif
1191 ms
top_footerbg.gif
1345 ms
top_footerarrow_a.gif
1354 ms
top_footerarrow_b.gif
1360 ms
ga.js
8 ms
__utm.gif
19 ms
__utm.gif
7 ms
toplineup_1_o.gif
172 ms
toplineup_2_o.gif
174 ms
toplineup_3_o.gif
172 ms
toplineup_4_o.gif
170 ms
toplineup_5_o.gif
173 ms
toplineup_8_o.gif
173 ms
houjicomlink_o.jpg
339 ms
youtubelink_o.jpg
341 ms
top_iritate_o.jpg
341 ms
top_sampleinq_o.gif
341 ms
hishidai.co.jp accessibility score
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
Form elements do not have associated labels
hishidai.co.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
hishidai.co.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hishidai.co.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 Hishidai.co.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.
hishidai.co.jp
Open Graph description is not detected on the main page of Hishidai. 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: