9.3 sec in total
513 ms
8.3 sec
489 ms
Click here to check amazing Ulunom content for Japan. Otherwise, check out these important facts you probably never knew about ulunom.jp
ウォーターサーバー宅配水サービス『おいしい水の贈りもの うるのん』(TOKAIグループ)の公式サイトです。静岡・富士山のふもとで採れた極上の天然水。採水からボトリングまで自社工場で一貫して行っている安全・安心の管理体制。赤ちゃんからお年寄りまでご愛飲いただける天然水をワンウェイ方式で提供しています。ご利用用途に合わせて3プランの契約プランをご用意。ウォーターサーバーのある暮らしを始めてみませんか?
Visit ulunom.jpWe analyzed Ulunom.jp page load time and found that the first response time was 513 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ulunom.jp performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value21.8 s
0/100
25%
Value22.8 s
0/100
10%
Value17,480 ms
0/100
30%
Value1.06
2/100
15%
Value70.9 s
0/100
10%
513 ms
530 ms
175 ms
315 ms
338 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ulunom.jp, 64% (108 requests) were made to Ulunom.tokai.jp and 8% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Ulunom.tokai.jp.
Page size can be reduced by 223.6 kB (6%)
4.0 MB
3.8 MB
In fact, the total size of Ulunom.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. 60% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 44.8 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 10.7 kB, which is 19% 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 44.8 kB or 78% of the original size.
Potential reduce by 77.1 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. Ulunom images are well optimized though.
Potential reduce by 82.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 82.9 kB or 48% of the original size.
Potential reduce by 18.8 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. Ulunom.jp needs all CSS files to be minified and compressed as it can save up to 18.8 kB or 78% of the original size.
Number of requests can be reduced by 56 (35%)
162
106
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ulunom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ulunom.jp
513 ms
ulunom.tokai.jp
530 ms
html5reset-1.6.1.css
175 ms
base.css
315 ms
top.css
338 ms
jquery.min.js
26 ms
easing.js
356 ms
lofslider.js
358 ms
common.js
334 ms
jquery.gafunc.js
361 ms
analytics.js
470 ms
thickbox.css
499 ms
thickbox-compressed.js
514 ms
news.js
503 ms
conversion.js
22 ms
s_retargeting.js
605 ms
bl_track.js
382 ms
NavicastApi.js
764 ms
ga.js
8 ms
head_logo.gif
259 ms
head_tel.gif
259 ms
head_order_tit.gif
169 ms
head_order_btn1_off.gif
259 ms
head_order_btn2_off.gif
194 ms
nav01_on.gif
259 ms
nav02_off.gif
346 ms
nav03_off.gif
353 ms
nav04_off.gif
417 ms
nav05_off.gif
423 ms
nav06_off.gif
421 ms
nav07_off.gif
420 ms
slider_img33.jpg
1837 ms
slider_img32.jpg
1901 ms
slider_img27.jpg
1574 ms
slider_img31.jpg
1319 ms
slider_img30.jpg
1967 ms
slider_img25.jpg
1787 ms
slider_img18.jpg
2433 ms
slider_img_sarari.jpg
3301 ms
slider_img14.jpg
3039 ms
slider_img12.jpg
3163 ms
slider_img01.jpg
2704 ms
slider_img03.jpg
2842 ms
slider_thum33.jpg
2705 ms
slider_thum32.jpg
2940 ms
slider_thum27.jpg
2942 ms
slider_thum31.jpg
3007 ms
slider_thum30.jpg
3164 ms
slider_thum25.jpg
3178 ms
slider_thum18.jpg
3216 ms
slider_thum_sarari.jpg
3271 ms
slider_thum14.jpg
3340 ms
slider_thum12.jpg
3378 ms
slider_thum01.jpg
3342 ms
gtm.js
89 ms
gtm.js
132 ms
slider_thum03.jpg
3395 ms
sdk.js
19 ms
widgets.js
18 ms
208 ms
xd_arbiter.php
93 ms
xd_arbiter.php
160 ms
conversion_async.js
73 ms
analytics.js
70 ms
news.html
3268 ms
important_icon.gif
3206 ms
safety_bnr.jpg
3294 ms
top_bnr06.jpg
3378 ms
top_bnr02.jpg
3376 ms
top_bnr03.jpg
3389 ms
collect
49 ms
123 ms
like.php
130 ms
collect
106 ms
bl_track.cgi
373 ms
corporation_bnr.jpg
3425 ms
tag.js
26 ms
tokai.js
524 ms
box1_tit.gif
3289 ms
66 ms
47 ms
box_btn_off.gif
3287 ms
box2_tit.gif
3397 ms
box3_tit.gif
3395 ms
box4_tit.gif
3397 ms
45 ms
TY3MhkXpWJ-.js
38 ms
LVx-xkvaJ0b.png
36 ms
NavicastTmg.php
170 ms
NavicastApi2.php
172 ms
NavicastApi2.php
543 ms
box5_btn_off.gif
2521 ms
box6_btn_off.gif
2298 ms
fbevents.js
67 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
22 ms
30 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
27 ms
page.php
176 ms
jot
111 ms
voice_title.gif
2166 ms
voice_img02.jpg
2168 ms
yIdHYsCA3B1.css
5 ms
1kPfZUdGrka.js
13 ms
AeiIQ53iqZ6.js
45 ms
Qd7TTBR3F_S.js
44 ms
jot
103 ms
1011927_293377934141223_622278800_n.png
66 ms
voice_btn01.gif
2028 ms
941276_261265480685802_819563639_n.png
25 ms
12669480_783545501791299_5716509802462167483_n.jpg
29 ms
1379841_10150004552801901_469209496895221757_n.jpg
28 ms
9241_469851903123090_615302433_n.jpg
31 ms
10303754_662163830522816_4634530821100215256_n.jpg
28 ms
11224368_940090479410622_8094678290312856529_n.jpg
29 ms
12669509_855518297892939_395158125818489657_n.jpg
31 ms
11796424_1629824510592987_2093783788029997469_n.jpg
34 ms
10424332_658010730940704_2563362259171444523_n.jpg
32 ms
11230107_154483041573521_4496132668196623376_n.jpg
94 ms
3520_854409128002285_6728748198803779216_n.jpg
34 ms
10171298_649880395093045_4146072115031358088_n.jpg
34 ms
wL6VQj7Ab77.png
21 ms
s7jcwEQH7Sx.png
21 ms
voice_btn02.gif
2009 ms
R9GKCzjAnbk.js
7 ms
AWWjhOengNF.js
8 ms
YnSasnyq68i.js
4 ms
kQf_jlUv-kX.js
4 ms
voice_btm.gif
1572 ms
news_tit.gif
1320 ms
news_btn.gif
1425 ms
news_oshirase.gif
1288 ms
fair_info_bnr.gif
1209 ms
side_bnr_cm_tit.gif
1223 ms
side_bnr_cm_img03.jpg
1185 ms
side_bnr_cm_btn.gif
1146 ms
side_bnr_bakaure.jpg
1295 ms
tokai_225x100.gif
1187 ms
side_bnr_tlc4.jpg
1294 ms
side_bnr_shop.jpg
1174 ms
side_bnr_campaign_soda.jpg
1178 ms
side_bnr_fb.jpg
1128 ms
side_bnr_fb_article.jpg
1209 ms
side_bnr_fb_pc.jpg
1241 ms
side_bnr_factory02.jpg
1243 ms
side_bnr_tel24.jpg
1293 ms
side_bnr_ret.jpg
1189 ms
pagetop_off.png
1191 ms
foot_dora.png
1208 ms
foot_logo.gif
1129 ms
foot_tel.gif
1172 ms
nav_bg.gif
1264 ms
head_order_bg.gif
1172 ms
slider_bg.jpg
1254 ms
load_indicator.gif
1177 ms
slider_left.gif
1119 ms
slider_right.gif
1163 ms
important_bg.gif
1167 ms
box1_bg.jpg
1220 ms
box2_bg.jpg
1250 ms
box3_bg.jpg
1197 ms
box4_bg.jpg
1175 ms
news_bg.gif
1160 ms
side_bnr_cm_bg.gif
1153 ms
foot_bg1.png
2699 ms
arrow02.gif
1262 ms
arrow01.gif
1183 ms
foot_bg2.png
1697 ms
loadingAnimation.gif
1173 ms
slider_thumb_arrow.gif
1154 ms
ulunom.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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ulunom.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ulunom.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Ulunom.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 Ulunom.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.
ulunom.jp
Open Graph data is detected on the main page of Ulunom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: