7.7 sec in total
1.1 sec
6 sec
538 ms
Welcome to niigata-kome.jp homepage info - get ready to check Niigata Kome best content right away, or after learning these important things about niigata-kome.jp
新潟の棚田米、岩船産コシヒカリ(大毎産)を販売。新潟県山北地区から低農薬で育てた、はさかけ米を産地直送でお届けいたします!
Visit niigata-kome.jpWe analyzed Niigata-kome.jp page load time and found that the first response time was 1.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
niigata-kome.jp performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value13.1 s
0/100
25%
Value8.2 s
20/100
10%
Value60 ms
100/100
30%
Value0.174
69/100
15%
Value16.2 s
5/100
10%
1098 ms
1644 ms
1791 ms
1636 ms
1815 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Niigata-kome.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Niigata-kome.jp.
Page size can be reduced by 221.0 kB (5%)
4.2 MB
4.0 MB
In fact, the total size of Niigata-kome.jp main page is 4.2 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. 40% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.1 kB or 76% of the original size.
Potential reduce by 17.3 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. Niigata Kome images are well optimized though.
Potential reduce by 167.3 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 167.3 kB or 76% of the original size.
Potential reduce by 10.3 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. Niigata-kome.jp needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 79% of the original size.
Number of requests can be reduced by 10 (17%)
59
49
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Niigata Kome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
niigata-kome.jp
1098 ms
styles.css
1644 ms
navi.css
1791 ms
index.css
1636 ms
calendar.css
1815 ms
external.js
1954 ms
addbm.js
714 ms
jquery-1.4.2.js
1796 ms
jquery.easing.1.3.js
1995 ms
jquery.galleryview-1.1.js
2146 ms
jquery.timers-1.1.2.js
1972 ms
calendar.js
1624 ms
ga.js
54 ms
header-bg.jpg
543 ms
logo.jpg
788 ms
btn-home-off.gif
183 ms
btn-sanpoku-off.gif
198 ms
btn-tanada-mai-off.gif
172 ms
btn-hasakake-mai-off.gif
170 ms
btn-reserve-off.gif
339 ms
btn-cart-off.gif
341 ms
01.jpg
1813 ms
02.jpg
2390 ms
03-1.jpg
1933 ms
04.jpg
2206 ms
05.jpg
1445 ms
06.jpg
2362 ms
sanpoku-map.gif
1627 ms
ban-sanchoku.gif
1809 ms
itagaki-comment.jpg
2169 ms
h27-comment-20150925.gif
1993 ms
index-sub.gif
2102 ms
ban-sanpoku-01.jpg
2356 ms
ban-tanadamai.jpg
2271 ms
h26-soldout-tanada.gif
2350 ms
ban-hasakake.jpg
2544 ms
top-goto-hasakake-saibai.jpg
2441 ms
seimai-img.jpg
2530 ms
shipping-free-ban.jpg
2537 ms
navi-left-sub.gif
2557 ms
rank-no1.gif
2584 ms
rank-ogoto.jpg
2610 ms
rank-no2.gif
2711 ms
rank-sanpoku.jpg
2719 ms
rank-no3.gif
2713 ms
rank-hasakake.jpg
2754 ms
sensor.jpg
2779 ms
shopping-guide-1.gif
2920 ms
nl-btn-sanpoku.gif
2899 ms
logset.cgi
2486 ms
__utm.gif
10 ms
nl-btn-ogoto.gif
2756 ms
nl-btn-hasakake.gif
2767 ms
nl-btn-reserve.gif
2774 ms
qr-code.gif
2780 ms
3m-cooking-2012-10.jpg
2758 ms
ban-oogoto-tv.jpg
2755 ms
ban-blog.gif
2579 ms
ban-ganba-wwn-200-54.gif
2333 ms
footer-bg.jpg
1707 ms
next.png
1548 ms
prev.png
1456 ms
panel-nav-next.png
1454 ms
panel-nav-prev.png
1368 ms
niigata-kome.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
niigata-kome.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
Browser errors were logged to the console
niigata-kome.jp SEO score
![]()
JA
![]()
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Niigata-kome.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 Niigata-kome.jp main page’s claimed encoding is shift_jis. 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.
niigata-kome.jp
Open Graph description is not detected on the main page of Niigata Kome. 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: