Tools & Wizards About Us
dietta.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dietta.jp

ダイエット口コミサイト | 痩せたいあなたにDIETTA[ディエッタ]

Page Load Speed

9.7 sec in total

First Response

661 ms

Resources Loaded

8 sec

Page Rendered

1.1 sec

dietta.jp screenshot

About Website

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

ダイエットに関する口コミ情報が満載のDIETTA[ディエッタ]では、おすすめの食材やレシピ、運動方法などを掲載中。痩せたい人、効果的なダイエット方法を知りたい人は、成功談などの口コミをチェックして、自分にぴったりのスタイルを見つけよう！

Visit dietta.jp

Key Findings

We analyzed Dietta.jp page load time and found that the first response time was 661 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

dietta.jp performance score

0

Network Requests Diagram

dietta.jp

661 ms

dietta.jp

1922 ms

4896030099.js

315 ms

app-d148b897.css

854 ms

dietta-embedded-ef557b51.css

852 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 30% of them (17 requests) were addressed to the original Dietta.jp, 43% (24 requests) were made to G0ivo6rxfntu7h.cdn.jp.idcfcloud.com and 5% (3 requests) were made to Spad.i-mobile.co.jp. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source G0ivo6rxfntu7h.cdn.jp.idcfcloud.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 735.6 kB (48%)

Content Size

1.5 MB

After Optimization

788.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dietta.jp main page is 1.5 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. Javascripts take 629.2 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 61.7 kB

  • Original 71.2 kB
  • After minification 52.2 kB
  • After compression 9.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 19.0 kB, which is 27% 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 61.7 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 29.9 kB

  • Original 535.5 kB
  • After minification 505.6 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. Dietta images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 408.0 kB

  • Original 629.2 kB
  • After minification 598.4 kB
  • After compression 221.3 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 408.0 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 236.0 kB

  • Original 288.3 kB
  • After minification 271.4 kB
  • After compression 52.3 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. Dietta.jp needs all CSS files to be minified and compressed as it can save up to 236.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

51

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dietta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

dietta.jp

dietta.jp

661 ms

dietta.jp

dietta.jp

1922 ms

4896030099.js

4896030099.js

315 ms

app-d148b897.css

app-d148b897.css

854 ms

dietta-embedded-ef557b51.css

dietta-embedded-ef557b51.css

852 ms

animate-f37a1535.css

animate-f37a1535.css

836 ms

adstir.js

adstir.js

923 ms

jquery.min-f03e5a3b.js

jquery.min-f03e5a3b.js

1155 ms

fastclick-6e9d3b0d.js

fastclick-6e9d3b0d.js

919 ms

foundation.min-b24a3d49.js

foundation.min-b24a3d49.js

1156 ms

slideout.min-5b42fbf4.js

slideout.min-5b42fbf4.js

1647 ms

app-921ea960.js

app-921ea960.js

1860 ms

jquery.cookie-d5528dde.js

jquery.cookie-d5528dde.js

1677 ms

jcf-24ec2c5b.js

jcf-24ec2c5b.js

1703 ms

jcf.number-43ce9bef.js

jcf.number-43ce9bef.js

1762 ms

toppage-bb6933d0.js

toppage-bb6933d0.js

1777 ms

jquery.colorbox-0060f5c3.js

jquery.colorbox-0060f5c3.js

2576 ms

logo_dietta.png

logo_dietta.png

2401 ms

1e44ca8a7346323a5e7c5c28fdf5c212.jpg

1e44ca8a7346323a5e7c5c28fdf5c212.jpg

3072 ms

436aecf7dc88584f358a6fb85d02dec6.jpg

436aecf7dc88584f358a6fb85d02dec6.jpg

3072 ms

c475a7e4c1b7144093997fcf7621d9f1.jpg

c475a7e4c1b7144093997fcf7621d9f1.jpg

2828 ms

95f8aab3f7a67be34bae7051250c44c7.jpg

95f8aab3f7a67be34bae7051250c44c7.jpg

2410 ms

8201750959c948f5935ddbef5b36dd73.jpg

8201750959c948f5935ddbef5b36dd73.jpg

2438 ms

2d93679a379c68cd455a560cf632f80a.jpg

2d93679a379c68cd455a560cf632f80a.jpg

2625 ms

27b8429d860c0c5c2df0b545cc24a635.jpeg

27b8429d860c0c5c2df0b545cc24a635.jpeg

2637 ms

2d6d066214b770f904fa496a0433f154.jpg

2d6d066214b770f904fa496a0433f154.jpg

2648 ms

8075fe17db150bd5f4741fc7c365d3c7.jpg

8075fe17db150bd5f4741fc7c365d3c7.jpg

2815 ms

3c0bf258b71fee1a266f0cadbdb69d62.jpg

3c0bf258b71fee1a266f0cadbdb69d62.jpg

2838 ms

c9221904dd12f1c887a5bff85ee3fe80.jpg

c9221904dd12f1c887a5bff85ee3fe80.jpg

2842 ms

3ee99bb33c2f1db3b6246b7fd50b668d.jpeg

3ee99bb33c2f1db3b6246b7fd50b668d.jpeg

3054 ms

30aa3ce2ae679a2e5e20ec8ee0866365.jpg

30aa3ce2ae679a2e5e20ec8ee0866365.jpg

3068 ms

383af6c6f11ccf9e3d8677a1929f4696.jpg

383af6c6f11ccf9e3d8677a1929f4696.jpg

3072 ms

36788f75b7350b65c97fe01a01e69821.jpg

36788f75b7350b65c97fe01a01e69821.jpg

3073 ms

usericon_05.png

usericon_05.png

3265 ms

usericon_04.png

usericon_04.png

3281 ms

1d439e04482182f3dcfa78a69a6c17c6.jpg

1d439e04482182f3dcfa78a69a6c17c6.jpg

3281 ms

user.png

user.png

3276 ms

usericon_02.png

usericon_02.png

3515 ms

usericon_03.png

usericon_03.png

3497 ms

5d46fa1d15291fc08e00587f67bc1666.jpeg

5d46fa1d15291fc08e00587f67bc1666.jpeg

3474 ms

img_regist_promo.jpg

img_regist_promo.jpg

3719 ms

gtm.js

gtm.js

389 ms

9YNLL0bmRhcAAfTIrgAAAA=

9YNLL0bmRhcAAfTIrgAAAA=

92 ms

dietta.svg

dietta.svg

1692 ms

ad

ad

870 ms

analytics.js

analytics.js

163 ms

conversion_async.js

conversion_async.js

185 ms

collect

collect

38 ms

collect

collect

187 ms

175 ms

757 ms

adssp.js

adssp.js

503 ms

adcore.js

adcore.js

116 ms

adcore_sp.js

adcore_sp.js

248 ms

s_retargeting.js

s_retargeting.js

2448 ms

search_keyword.json

search_keyword.json

269 ms

SEO Factors

dietta.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 Dietta.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 Dietta.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

dietta.jp

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