6.8 sec in total
578 ms
6 sec
192 ms
Visit ucc.jp now to see the best up-to-date Ucc content for Japan and also check out these interesting facts you probably never knew about ucc.jp
コーヒーから生まれる笑顔のために。UCC上島珈琲のホームページでは、おいしいコーヒーの入れ方や豆知識、レシピ、キャンペーン、UCCコーヒークーポンなど毎日のコーヒーがもっとおいしくなる情報が満載です。
Visit ucc.jpWe analyzed Ucc.jp page load time and found that the first response time was 578 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ucc.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value18.5 s
0/100
25%
Value11.9 s
4/100
10%
Value4,610 ms
0/100
30%
Value0.169
70/100
15%
Value12.4 s
14/100
10%
578 ms
578 ms
1168 ms
370 ms
384 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Ucc.jp, 60% (92 requests) were made to Img.ucc.co.jp and 11% (17 requests) were made to Ucc.co.jp. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source I25.dga.jp.
Page size can be reduced by 649.2 kB (31%)
2.1 MB
1.5 MB
In fact, the total size of Ucc.jp main page is 2.1 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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 24.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. 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 24.4 kB or 76% of the original size.
Potential reduce by 52.7 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. Ucc images are well optimized though.
Potential reduce by 305.2 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 305.2 kB or 61% of the original size.
Potential reduce by 266.9 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. Ucc.jp needs all CSS files to be minified and compressed as it can save up to 266.9 kB or 84% of the original size.
Number of requests can be reduced by 50 (36%)
138
88
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ucc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ucc.jp
578 ms
www.ucc.jp
578 ms
www.ucc.co.jp
1168 ms
base.css
370 ms
structure.css
384 ms
contents.css
788 ms
ga_code.js
405 ms
footer.css
383 ms
mjl.js
680 ms
jquery.js
931 ms
run.js
583 ms
search_tool.js
2093 ms
player02.js
613 ms
conversion.js
17 ms
s_retargeting.js
595 ms
gtm.js
48 ms
ga.js
4 ms
matc.js
519 ms
gatrack.js
394 ms
analytics.js
3 ms
collect
3 ms
collect
71 ms
__utm.gif
70 ms
bg-body-01.png
245 ms
__utm.gif
47 ms
ico_arw_ucc-portal-footer.png
388 ms
logo.png
179 ms
btn-nav_header-01.png
185 ms
btn-nav_header-05.png
179 ms
btn-nav_header-02.png
177 ms
btn-nav_header-03.png
179 ms
bg-input-01.png
194 ms
btn-search-01.png
180 ms
btn-nav_global-01.png
190 ms
btn-nav_global-02.png
182 ms
btn-nav_global-03.png
195 ms
btn-nav_global-04.png
185 ms
btn-nav_global-05.png
186 ms
btn-nav_global-06.png
188 ms
bg-main_visual-01.png
198 ms
btn-main_visual-21.png
258 ms
btn-main_visual-18.png
243 ms
btn-main_visual-13.png
246 ms
btn-main_visual-19.png
215 ms
btn-main_visual-16.png
200 ms
btn-main_visual-22.png
254 ms
btn-main_visual-23.png
237 ms
btn-main_visual-24.png
251 ms
index-hdg-01.png
240 ms
btn-campaign-03.png
245 ms
index-photo-123.png
242 ms
index-photo-125.png
268 ms
index-photo-127.jpg
1083 ms
index-banner-07.png
263 ms
index-hdg-02.png
251 ms
index-btn-01.png
253 ms
btn-rss-01.png
254 ms
bg-icon-arrow-01.png
277 ms
bg-box_top_01-01.png
263 ms
index-hdg-03.png
256 ms
index-banner-01.png
259 ms
lognos.js
322 ms
banner-top.xml
391 ms
index-banner-02.png
94 ms
index-banner-03.png
109 ms
index-banner-04.png
110 ms
btn-category-01.png
133 ms
index-hdg-04.png
109 ms
index-banner-21.png
135 ms
index-banner-06.png
107 ms
index-banner-17.jpg
152 ms
index-hdg-07.png
105 ms
btn-zoom-01.png
103 ms
index-hdg-06.png
134 ms
bg-line-01.png
133 ms
index-photo-40.png
135 ms
index-photo-118.png
126 ms
index-photo-47.png
136 ms
index-photo-51.png
110 ms
index-photo-30.png
116 ms
bg-footer-03.png
103 ms
bg-footer-01.png
89 ms
bg-line-08.png
92 ms
bg-footer-02.png
93 ms
copyright.png
108 ms
icon-pdf-01.png
113 ms
icon-external-01.png
98 ms
utm.png
83 ms
slider-main-124.png
14 ms
slider-main-141.png
14 ms
slider-main-145.png
1545 ms
slider-main-143.png
6 ms
btn-main_view-01.png
22 ms
movie_ID.json
365 ms
40 ms
52 ms
43 ms
52 ms
16 ms
17 ms
34 ms
31 ms
28 ms
blade_track_jp.js
355 ms
51 ms
59 ms
29 ms
33 ms
33 ms
21 ms
20 ms
16 ms
cookie_enabled_get.html
357 ms
bl_track.cgi
369 ms
btn-nav_header-01_o.png
19 ms
btn_play_d.gif
404 ms
player_api
24 ms
btn_pause_d.gif
401 ms
btn-nav_header-05_o.png
34 ms
btn-nav_header-02_o.png
9 ms
btn-nav_header-03_o.png
7 ms
btn-search-01_o.png
23 ms
btn-nav_global-01_o.png
8 ms
btn-nav_global-02_o.png
24 ms
btn-nav_global-03_o.png
7 ms
btn-nav_global-04_o.png
24 ms
btn-nav_global-05_o.png
7 ms
btn-nav_global-06_o.png
17 ms
btn-main_visual-21_o.png
9 ms
btn-main_visual-18_o.png
14 ms
btn-main_visual-13_o.png
108 ms
btn-main_visual-19_o.png
59 ms
btn-main_visual-16_o.png
75 ms
btn-main_visual-22_o.png
60 ms
btn-main_visual-23_o.png
57 ms
btn-main_visual-24_o.png
72 ms
btn-campaign-03_o.png
77 ms
index-btn-01_o.png
61 ms
index-banner-01_o.png
90 ms
index-banner-02_o.png
66 ms
index-banner-03_o.png
91 ms
index-banner-04_o.png
88 ms
btn-category-01_o.png
101 ms
btn-zoom-01_o.png
78 ms
www-widgetapi.js
20 ms
63 ms
www-embed-player-vflQrT_sR.css
46 ms
www-embed-player.js
70 ms
base.js
98 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
8 ms
ad_status.js
55 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
55 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
59 ms
ucc.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.
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
<object> elements do not have alternate text
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.
ucc.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
Missing source maps for large first-party JavaScript
ucc.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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ucc.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Ucc.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.
ucc.jp
Open Graph description is not detected on the main page of Ucc. 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: