7.7 sec in total
1.1 sec
6.1 sec
405 ms
Visit wellshop.jp now to see the best up-to-date Wellshop content for Japan and also check out these interesting facts you probably never knew about wellshop.jp
美容と健康の「ナチュラルガーデン」公式通販サイトです。白酵プラセンタ化粧品、美容ドリンク、健康食品などのオリジナル商品の販売を通じ、お客様の健やかで若々しい人生を応援します。
Visit wellshop.jpWe analyzed Wellshop.jp page load time and found that the first response time was 1.1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wellshop.jp performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value14.9 s
0/100
25%
Value21.7 s
0/100
10%
Value2,100 ms
7/100
30%
Value0.353
31/100
15%
Value27.4 s
0/100
10%
1139 ms
25 ms
193 ms
382 ms
389 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 70% of them (80 requests) were addressed to the original Wellshop.jp, 5% (6 requests) were made to Api.flipdesk.jp and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Wellshop.jp.
Page size can be reduced by 1.1 MB (28%)
4.0 MB
2.9 MB
In fact, the total size of Wellshop.jp main page is 4.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. 55% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 52.5 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 7.8 kB, which is 12% 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 52.5 kB or 80% of the original size.
Potential reduce by 113.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. Wellshop images are well optimized though.
Potential reduce by 675.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 675.5 kB or 67% of the original size.
Potential reduce by 271.1 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. Wellshop.jp needs all CSS files to be minified and compressed as it can save up to 271.1 kB or 87% of the original size.
Number of requests can be reduced by 40 (37%)
107
67
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellshop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wellshop.jp
1139 ms
analytics.js
25 ms
se-styles.css
193 ms
reset.css
382 ms
style.css
389 ms
smart.css
395 ms
easyselectbox.css
393 ms
jquery.selectbox.css
397 ms
default.css
440 ms
nivo-slider.css
568 ms
default.min.css
579 ms
jetpack.css
586 ms
uamAdmin.css
582 ms
uamLoginForm.css
585 ms
jquery.min.js
48 ms
jquery.cookie.js
658 ms
3519251703.js
285 ms
functions.js
755 ms
cal.ntg.js
793 ms
photon.js
794 ms
jquery.heightLine.js
795 ms
jquery.easing.1.3.js
794 ms
slides.min.jquery.js
873 ms
jquery.smoothScroll.js
942 ms
jquery.selectbox.js
959 ms
jquery.nivo.slider.js
970 ms
jquery.carouFredSel-6.2.0-packed.js
974 ms
ranking.js
986 ms
main.js
1092 ms
devicepx-jetpack.js
59 ms
s_retargeting.js
561 ms
conversion.js
25 ms
flipdesk_chat.js
1006 ms
ld.js
25 ms
ec.js
10 ms
collect
9 ms
collect
57 ms
menubar_back.gif
401 ms
sprite.png
773 ms
tmg-tel-ntg.png
406 ms
btn_overlay.png
406 ms
search_icon.png
405 ms
keywords_arrow.gif
545 ms
hdr_ranking_back.gif
577 ms
loading.gif
600 ms
bn-fasty_yo-04.jpg
1377 ms
bn-app-cp-09.gif
986 ms
bn-fasty-08.jpg
1901 ms
bn-swcl-03.jpg
1530 ms
slider_fasty_sm-02.png
2363 ms
bn-nata-02.jpg
1349 ms
bn-egpl_pre-02.jpg
1575 ms
bn-swcl-05.jpg
1755 ms
s_slider_fasty_sm.jpg
1770 ms
bn-nata-03.jpg
2097 ms
bn-egpl_pre-03.jpg
1970 ms
bnr_regular_purchase.gif
1929 ms
bn-fasty-09.jpg
1968 ms
bn-swcl-04.jpg
2121 ms
bn-pana-02.jpg
2120 ms
swbn_ezotama.jpg
2163 ms
swbn_bbn.jpg
2148 ms
swbn_lifesupport.jpg
2272 ms
facebook_fasty.gif
2294 ms
bn-app_cp-01.gif
2322 ms
bn-mgz-01.jpg
2521 ms
bn-niwatori-03.gif
2262 ms
lwbn_nafr.gif
2312 ms
lwbn_egpl_pre.jpg
2325 ms
bn-cbgc-04.jpg
2368 ms
lwbn_blca.jpg
2343 ms
bn-soi-02.jpg
2350 ms
tag.js
51 ms
65 ms
gtm.js
86 ms
uiprepare
232 ms
40 ms
33 ms
40 ms
bn-pana-03.gif
2299 ms
event
21 ms
tag
11 ms
cart_fasty_250.jpg
2314 ms
88 ms
cart-nata-meb.jpg
2361 ms
cart-egpl-01.jpg
2363 ms
cart-some-04.jpg
2564 ms
event
362 ms
89 ms
89 ms
89 ms
conversion_async.js
12 ms
15 ms
37 ms
cart-hkgen-04.jpg
2252 ms
cart-fasty_yo-01.jpg
2493 ms
flipdesk.min.js
1111 ms
cart-befit-02_02.jpg
2312 ms
cart-swcl-02.jpg
2193 ms
niwa_tojo.gif
1987 ms
notice_pay_card.gif
1666 ms
notice_pay_np.gif
1727 ms
notice_shipping_time.gif
1632 ms
home_cont_title_back.gif
1589 ms
chat_loading.gif
162 ms
flipdesk.css
323 ms
setting
835 ms
select_icons.png
1466 ms
print.css
193 ms
pv
338 ms
dis.aspx
396 ms
x.png
709 ms
wellshop.jp
703 ms
slider_arrow.gif
191 ms
wellshop.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 input fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
wellshop.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
wellshop.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wellshop.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 Wellshop.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.
wellshop.jp
Open Graph description is not detected on the main page of Wellshop. 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: