Tools & Wizards About Us
cp-tokucha.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cp-tokucha.jp

LINEで始めよう！特茶キャンペーン - 体脂肪を減らすのを助ける - 伊右衛門 特茶　サントリー

Page Load Speed

7 sec in total

First Response

402 ms

Resources Loaded

6.4 sec

Page Rendered

279 ms

cp-tokucha.jp screenshot

About Website

Welcome to cp-tokucha.jp homepage info - get ready to check Cp Tokucha best content for Japan right away, or after learning these important things about cp-tokucha.jp

商品に貼られているシールに記載のQRコードを読み込んでLINEで応募しよう！体脂肪を減らすのを助ける特茶。ひとりじゃなかなか続かない体脂肪対策に、みんなで取り組もう！家族や友だち、仕事の仲間。身近な人と一緒に、楽しく体脂肪を減らすのを助ける企画。

Visit cp-tokucha.jp

Key Findings

We analyzed Cp-tokucha.jp page load time and found that the first response time was 402 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

cp-tokucha.jp performance score

0

Network Requests Diagram

www.cp-tokucha.jp

402 ms

914 ms

pc_to_mobile.js

615 ms

suntory_gn_utf8.css

1094 ms

basic.css

979 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cp-tokucha.jp, 47% (58 requests) were made to Suntory.co.jp and 4% (5 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Suntory.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.5 kB (23%)

Content Size

2.3 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cp-tokucha.jp main page is 2.3 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 35.6 kB

  • Original 46.7 kB
  • After minification 43.0 kB
  • After compression 11.1 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 35.6 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 116.4 kB

  • Original 1.7 MB
  • After minification 1.6 MB

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. Cp Tokucha images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 335.0 kB

  • Original 485.6 kB
  • After minification 414.5 kB
  • After compression 150.6 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 335.0 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 42.5 kB

  • Original 50.1 kB
  • After minification 41.8 kB
  • After compression 7.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. Cp-tokucha.jp needs all CSS files to be minified and compressed as it can save up to 42.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 68 (59%)

Requests Now

115

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cp Tokucha. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.cp-tokucha.jp

www.cp-tokucha.jp

402 ms

914 ms

pc_to_mobile.js

pc_to_mobile.js

615 ms

suntory_gn_utf8.css

suntory_gn_utf8.css

1094 ms

basic.css

basic.css

979 ms

style.css

style.css

755 ms

style.css

style.css

378 ms

common.js

common.js

1150 ms

lib.js

lib.js

1419 ms

common.js

common.js

1036 ms

jquery.webticker.min.js

jquery.webticker.min.js

1522 ms

oneten.js

oneten.js

1322 ms

top.js

top.js

1493 ms

jquery.socialbutton.js

jquery.socialbutton.js

1375 ms

jquery.socialbutton_suntory.js

jquery.socialbutton_suntory.js

1944 ms

basic.js

basic.js

1683 ms

img_logo-tokucha.png

img_logo-tokucha.png

1173 ms

gnav_product.png

gnav_product.png

1196 ms

gnav_tokucha.png

gnav_tokucha.png

1236 ms

gnav_servey.png

gnav_servey.png

1626 ms

gnav_taisou.png

gnav_taisou.png

1462 ms

gnav_cm.png

gnav_cm.png

1579 ms

main2.jpg

main2.jpg

1655 ms

main7.jpg

main7.jpg

1699 ms

main5.jpg

main5.jpg

1856 ms

btn_cm.png

btn_cm.png

1881 ms

btn_cm_over.png

btn_cm_over.png

2050 ms

btn_tokucha.png

btn_tokucha.png

2138 ms

btn_tokucha_over.png

btn_tokucha_over.png

2064 ms

btn_servey.png

btn_servey.png

2032 ms

btn_servey_over.png

btn_servey_over.png

2519 ms

btn_product.png

btn_product.png

2241 ms

btn_product_over.png

btn_product_over.png

2558 ms

content_bottom_title.gif

content_bottom_title.gif

2429 ms

btn_middle_data01.png

btn_middle_data01.png

2429 ms

btn_taisou.png

btn_taisou.png

2594 ms

btn_recipe.png

btn_recipe.png

2599 ms

btn_middle_data04.png

btn_middle_data04.png

2782 ms

btn_middle_data03.png

btn_middle_data03.png

2882 ms

btn_middle_data02.png

btn_middle_data02.png

3177 ms

socialmedia.jpg

socialmedia.jpg

3113 ms

town_20140601.jpg

town_20140601.jpg

2751 ms

campaign_20140601.jpg

campaign_20140601.jpg

2687 ms

hd_bg.png

hd_bg.png

2844 ms

tag.js

tag.js

8 ms

gtm.js

gtm.js

70 ms

hd.png

hd.png

2656 ms

tag

tag

11 ms

conversion_async.js

conversion_async.js

28 ms

analytics.js

analytics.js

11 ms

segmentation.js

segmentation.js

22 ms

verify-age-common.js

verify-age-common.js

1597 ms

s_retargeting.js

s_retargeting.js

537 ms

dc.js

dc.js

50 ms

collect

collect

6 ms

collect

collect

9 ms

collect

collect

155 ms

collect

collect

158 ms

83 ms

cnt

cnt

390 ms

117 ms

sub_sbf.png

sub_sbf.png

2762 ms

audience

audience

320 ms

__utm.gif

__utm.gif

17 ms

__utm.gif

__utm.gif

57 ms

smt2e.min.js

smt2e.min.js

150 ms

87 ms

bg0.gif

bg0.gif

2729 ms

72 ms

71 ms

64 ms

bg_gnav.png

bg_gnav.png

2681 ms

bg_logo.gif

bg_logo.gif

2710 ms

bg_logo-tokucha.png

bg_logo-tokucha.png

2637 ms

gnav_iyemon.png

gnav_iyemon.png

2817 ms

ic_loader.gif

ic_loader.gif

2590 ms

section_line.png

section_line.png

2581 ms

ft_bg.png

ft_bg.png

2541 ms

mone.9eacfca051f_195.js

mone.9eacfca051f_195.js

100 ms

ya.js

ya.js

332 ms

beacon.html

beacon.html

53 ms

share.js

share.js

332 ms

widgets.js

widgets.js

24 ms

ft.png

ft.png

2500 ms

pixel

pixel

42 ms

cs

cs

313 ms

Pug

Pug

43 ms

set

set

311 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

30 ms

like.php

like.php

71 ms

sd

sd

22 ms

tap.php

tap.php

17 ms

sync

sync

362 ms

0000007818-img-dc

0000007818-img-dc

632 ms

b

b

1195 ms

cnt

cnt

188 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

12 ms

sync

sync

173 ms

pagenater0.png

pagenater0.png

2399 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

486 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

551 ms

arrow_left.png

arrow_left.png

2512 ms

jot

jot

81 ms

arrow_right.png

arrow_right.png

2438 ms

facebook_share.gif

facebook_share.gif

2424 ms

pb.js

pb.js

465 ms

324 ms

mapuser

mapuser

150 ms

sync

sync

263 ms

share_button.html

share_button.html

300 ms

iui3

iui3

122 ms

sync

sync

280 ms

combo

combo

151 ms

pixel

pixel

14 ms

pb.html

pb.html

9 ms

pixel

pixel

14 ms

308 ms

bt_check_1.png

bt_check_1.png

10 ms

615 ms

311 ms

smt-aux.min.js

smt-aux.min.js

70 ms

149 ms

smt-record.min.js

smt-record.min.js

74 ms

audience

audience

191 ms

SEO Factors

cp-tokucha.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cp-tokucha.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 Cp-tokucha.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.

Social Sharing Optimization

cp-tokucha.jp

Open Graph data is detected on the main page of Cp Tokucha. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: