5.3 sec in total
520 ms
4.6 sec
204 ms
Visit nakazen.co.jp now to see the best up-to-date Nakazen content for Japan and also check out these interesting facts you probably never knew about nakazen.co.jp
ノニ・春ウコンの仲善へようこそ。全て自社で一括管理されるノニ100%の製品とミネラルたっぷり健康を実感する本物のウコン(春ウコン)製品をご提供。仲善は皆様の健康づくり(ノニ、春ウコンなど)のお手伝いを続けて参ります。初めての方は初回お試し価格でご提供!
Visit nakazen.co.jpWe analyzed Nakazen.co.jp page load time and found that the first response time was 520 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nakazen.co.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value10.5 s
0/100
25%
Value11.7 s
4/100
10%
Value440 ms
64/100
30%
Value0.292
41/100
15%
Value7.1 s
52/100
10%
520 ms
1229 ms
343 ms
344 ms
353 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 45% of them (35 requests) were addressed to the original Nakazen.co.jp, 21% (16 requests) were made to Scontent.xx.fbcdn.net and 13% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Nakazen.co.jp.
Page size can be reduced by 455.5 kB (17%)
2.6 MB
2.1 MB
In fact, the total size of Nakazen.co.jp main page is 2.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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 21.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 5.0 kB, which is 18% 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 21.6 kB or 76% of the original size.
Potential reduce by 17.5 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. Nakazen images are well optimized though.
Potential reduce by 203.1 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 203.1 kB or 63% of the original size.
Potential reduce by 213.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. Nakazen.co.jp needs all CSS files to be minified and compressed as it can save up to 213.3 kB or 83% of the original size.
Number of requests can be reduced by 30 (41%)
73
43
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nakazen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
nakazen.co.jp
520 ms
www.nakazen.co.jp
1229 ms
import.css
343 ms
share.css
344 ms
index.css
353 ms
jquery.js
365 ms
jquery.min.js
1124 ms
jquery.easing.1.3.js
681 ms
slides.min.jquery.js
682 ms
top.js
518 ms
window.js
527 ms
reset.css
206 ms
utility.css
352 ms
typography.css
363 ms
ar.css
388 ms
body_bg_top.gif
177 ms
logo2014.jpg
381 ms
img01.jpg
1359 ms
img02.jpg
615 ms
img03.jpg
684 ms
img04.jpg
966 ms
houjin-annai.jpg
618 ms
omasu3.jpg
1102 ms
noni.jpg
783 ms
haru.jpg
788 ms
sta.jpg
855 ms
tbana-curcumin.jpg
1292 ms
tbana-curcumanomori.jpg
1313 ms
tbana-noniblog.jpg
1196 ms
tbana-kaichoblog.jpg
1141 ms
all.js
24 ms
slide_bg.png
1279 ms
title_bg.jpg
1312 ms
ga.js
20 ms
img01.jpg
1979 ms
loading.gif
1391 ms
pagination.png
1386 ms
__utm.gif
22 ms
__utm.gif
22 ms
cGysy4DYy3Y
116 ms
147 ms
xd_arbiter.php
31 ms
xd_arbiter.php
56 ms
ping
185 ms
like_box.php
256 ms
www-embed-player-vflfNyN_r.css
63 ms
www-embed-player.js
84 ms
like_box.php
135 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
64 ms
ad_status.js
68 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
116 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
117 ms
SwWqNEM2GQB.css
103 ms
qfDTH5pB6Ut.css
108 ms
q68gy-v_YMF.js
114 ms
ehA1CqzHyzE.js
143 ms
0wM5s1Khldu.js
141 ms
1bNoFZUdlYZ.js
141 ms
549318_353973414638992_690954539_n.jpg
126 ms
268405_218733248163010_1592863_n.jpg
39 ms
10678813_10152681517058571_2361104085421667418_n.jpg
40 ms
11215730_699651193494890_4145795022753389993_n.jpg
42 ms
10615458_1576206482598214_9171265107346720940_n.jpg
43 ms
1379841_10150004552801901_469209496895221757_n.jpg
41 ms
12274398_554673678017742_2633465609064733675_n.jpg
40 ms
12495044_949165525161486_6610163697464777323_n.jpg
75 ms
523713_339820619404963_1240274218_n.jpg
56 ms
224122_171972856189741_1566505_n.jpg
45 ms
1928757_131736797219381_5297894889481788478_n.jpg
45 ms
12662428_820986738012365_4329115575241379074_n.jpg
44 ms
10354686_10150004552801856_220367501106153455_n.jpg
44 ms
12369242_10102270374039387_1591120922161636419_n.jpg
48 ms
734993_1729757080588951_4693611694770106310_n.jpg
49 ms
11221957_10207405444273783_2300148382739549349_n.jpg
44 ms
wL6VQj7Ab77.png
33 ms
s7jcwEQH7Sx.png
32 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
3 ms
nakazen.co.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 match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
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
Links do not have a discernible name
nakazen.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
Page has valid source maps
nakazen.co.jp SEO score
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nakazen.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 Nakazen.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.
nakazen.co.jp
Open Graph description is not detected on the main page of Nakazen. 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: