7.3 sec in total
537 ms
6.3 sec
461 ms
Visit e-oxygenizer.jp now to see the best up-to-date E Oxygenizer content and also check out these interesting facts you probably never knew about e-oxygenizer.jp
水道水の約36倍!高濃度酸素水オキシゲナイザー。軟水、ピュアウォータなど飲料水の販売サイト。
Visit e-oxygenizer.jpWe analyzed E-oxygenizer.jp page load time and found that the first response time was 537 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
e-oxygenizer.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value18.9 s
0/100
25%
Value11.0 s
6/100
10%
Value830 ms
35/100
30%
Value0.469
18/100
15%
Value26.7 s
0/100
10%
537 ms
708 ms
513 ms
356 ms
917 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 56% of them (54 requests) were addressed to the original E-oxygenizer.jp, 21% (20 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to External.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain E-oxygenizer.jp.
Page size can be reduced by 288.3 kB (20%)
1.4 MB
1.1 MB
In fact, the total size of E-oxygenizer.jp main page is 1.4 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 14.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. This page needs HTML code to be minified as it can gain 3.5 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 14.4 kB or 72% of the original size.
Potential reduce by 3.4 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. E Oxygenizer images are well optimized though.
Potential reduce by 247.9 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 247.9 kB or 79% of the original size.
Potential reduce by 22.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. E-oxygenizer.jp needs all CSS files to be minified and compressed as it can save up to 22.6 kB or 84% of the original size.
Number of requests can be reduced by 42 (44%)
95
53
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Oxygenizer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
e-oxygenizer.jp
537 ms
www.e-oxygenizer.jp
708 ms
default.css
513 ms
block.css
356 ms
jquery-1.7.1.min.js
917 ms
setting.js
378 ms
pcsmpflg.js
407 ms
jquery.SlideEffect.js
501 ms
analytics.js
29 ms
s_sb_20059.jpg
675 ms
head_bg.gif
343 ms
logo.gif
344 ms
head_copy.gif
357 ms
head_tel.gif
387 ms
head_nav_guide.gif
388 ms
head_nav_faq.gif
393 ms
head_nav_member.gif
705 ms
head_mypage.gif
721 ms
head_cart.gif
720 ms
head_contact.gif
725 ms
gnav_home.gif
733 ms
gnav_list.gif
747 ms
gnav_brand.gif
1152 ms
gnav_campaign.gif
1152 ms
gnav_media.gif
1152 ms
gnav_company.gif
1153 ms
gnav_voice.gif
1154 ms
btn_login.gif
1153 ms
bnr_delivery_free.gif
1480 ms
bnr_regular_purchase.jpg
1793 ms
item_list.gif
1423 ms
bnr_movie.jpg
1793 ms
bnr_blog.gif
1432 ms
bnr_twitter.gif
1442 ms
bnr_mobile.gif
1786 ms
bnr_leivy_naturally.jpg
2203 ms
main1.jpg
3171 ms
main2.jpg
3395 ms
main3.jpg
3195 ms
prev.png
2156 ms
next.png
2182 ms
main_thumb1.jpg
2933 ms
main_thumb2.jpg
2895 ms
main_thumb3.jpg
2552 ms
bnr_brand_introduction.jpg
3798 ms
w_wr_30073.jpg
659 ms
bnr_regular_purchase.jpg
4255 ms
linkid.js
39 ms
ec.js
42 ms
collect
91 ms
collect
15 ms
collect
71 ms
tracking.php
848 ms
likebox.php
299 ms
likebox.php
467 ms
pagetop.gif
2990 ms
payment_card.gif
3199 ms
payment_convini.gif
3212 ms
arrow1.gif
3284 ms
main_bg.gif
3389 ms
main_thumb_bg.gif
3517 ms
kyEKgjk51ZE.css
177 ms
xgj7bXhJNEH.css
220 ms
Czh0gDTFcBt.css
262 ms
N-k91nHCZS2.css
333 ms
ZeuPykSxSED.css
344 ms
q68gy-v_YMF.js
379 ms
FJmpeSpHpjS.js
405 ms
0wM5s1Khldu.js
301 ms
1bNoFZUdlYZ.js
307 ms
njO1TPvGzoR.js
360 ms
1QuX41zDRrx.js
361 ms
Oagsvfb4VWi.js
428 ms
LTv6ZK-5zxz.js
500 ms
1FCa-btixu2.js
436 ms
main_thumb_off.gif
3210 ms
foot_bg.gif
3273 ms
arrow2.gif
3401 ms
main_thumb_on.png
3455 ms
1005048_172514536254765_1819419071_n.jpg
406 ms
safe_image.php
399 ms
safe_image.php
456 ms
safe_image.php
558 ms
safe_image.php
647 ms
safe_image.php
584 ms
safe_image.php
1511 ms
safe_image.php
1669 ms
safe_image.php
528 ms
11461_172513972921488_403261443_n.jpg
477 ms
1005048_172514536254765_1819419071_n.jpg
536 ms
wL6VQj7Ab77.png
102 ms
s7jcwEQH7Sx.png
100 ms
QDwYpIaRyfG.png
101 ms
K00K-UgnsKu.png
103 ms
eff_convert.php
562 ms
I6-MnjEovm5.js
43 ms
pQrUxxo5oQp.js
79 ms
e-oxygenizer.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
e-oxygenizer.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
e-oxygenizer.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
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-oxygenizer.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that E-oxygenizer.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.
e-oxygenizer.jp
Open Graph description is not detected on the main page of E Oxygenizer. 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: