Tools & Wizards About Us
citrulline.jp.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

citrulline.jp.net

没有找到站点

Page Load Speed

8.9 sec in total

First Response

2.5 sec

Resources Loaded

5.4 sec

Page Rendered

1 sec

citrulline.jp.net screenshot

About Website

Click here to check amazing Citrulline content for Japan. Otherwise, check out these important facts you probably never knew about citrulline.jp.net

健康維持を目指す方や、筋肉量アップを目指している方におすすめのシトルリンサプリメントを紹介。今まで試してきた中でも、最も効果を実感できたシトルリンサプリメントとは？おすすめの3製品を発表します！

Visit citrulline.jp.net

Key Findings

We analyzed Citrulline.jp.net page load time and found that the first response time was 2.5 sec and then it took 6.4 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

citrulline.jp.net performance score

0

Network Requests Diagram

citrulline.jp.net

2499 ms

common.css

353 ms

layout.css

371 ms

design.css

571 ms

mobile.css

356 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 49% of them (30 requests) were addressed to the original Citrulline.jp.net, 11% (7 requests) were made to Apis.google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Citrulline.jp.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 266.4 kB (25%)

Content Size

1.1 MB

After Optimization

815.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Citrulline.jp.net main page is 1.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. 50% of websites need less resources to load. Images take 719.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 54.4 kB

  • Original 72.0 kB
  • After minification 67.5 kB
  • After compression 17.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. 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 54.4 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 16.0 kB

  • Original 719.4 kB
  • After minification 703.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. Citrulline images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 127.7 kB

  • Original 209.4 kB
  • After minification 199.1 kB
  • After compression 81.7 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 127.7 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 68.2 kB

  • Original 81.0 kB
  • After minification 57.8 kB
  • After compression 12.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. Citrulline.jp.net needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (58%)

Requests Now

59

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

citrulline.jp.net

citrulline.jp.net

2499 ms

common.css

common.css

353 ms

layout.css

layout.css

371 ms

design.css

design.css

571 ms

mobile.css

mobile.css

356 ms

mobile_layout.css

mobile_layout.css

362 ms

advanced.css

advanced.css

858 ms

jquery.js

jquery.js

1210 ms

utility.js

utility.js

700 ms

socialButton.js

socialButton.js

380 ms

devicepx-jetpack.js

devicepx-jetpack.js

61 ms

ga.js

ga.js

146 ms

print.css

print.css

186 ms

gtm.js

gtm.js

146 ms

bg-headtwo.jpg

bg-headtwo.jpg

539 ms

basubasu.png

basubasu.png

360 ms

aminohuraito.png

aminohuraito.png

866 ms

bxaa.jpg

bxaa.jpg

597 ms

amiyaji.png

amiyaji.png

381 ms

sitoriku.jpg

sitoriku.jpg

724 ms

yaseisuika.png

yaseisuika.png

1462 ms

undousuru.png

undousuru.png

1255 ms

toreni.png

toreni.png

1240 ms

suikasan.png

suikasan.png

1324 ms

kutiko.png

kutiko.png

1070 ms

nomusapu.png

nomusapu.png

1575 ms

sapunomu.png

sapunomu.png

1735 ms

kinsapu.png

kinsapu.png

1905 ms

sapurime.jpg

sapurime.jpg

1595 ms

icon-arrow_r.gif

icon-arrow_r.gif

1649 ms

icon-menu02.png

icon-menu02.png

1800 ms

bg-header.gif

bg-header.gif

1924 ms

bg-pagetop.png

bg-pagetop.png

1964 ms

__utm.gif

__utm.gif

13 ms

f88f8357-2741-4b43-82a4-446b756c723d.js

f88f8357-2741-4b43-82a4-446b756c723d.js

51 ms

WRf4.js

WRf4.js

10 ms

widgets.js

widgets.js

8 ms

button-only.gif

button-only.gif

344 ms

bookmark_button.js

bookmark_button.js

368 ms

plusone.js

plusone.js

128 ms

all.js

all.js

280 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

36 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

33 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

19 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

43 ms

fastbutton

fastbutton

128 ms

postmessageRelay

postmessageRelay

40 ms

jot

jot

170 ms

api.js

api.js

100 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

123 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

122 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

72 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

68 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

141 ms

87 ms

xd_arbiter.php

xd_arbiter.php

229 ms

xd_arbiter.php

xd_arbiter.php

421 ms

211 ms

reset.css

reset.css

9 ms

entry-button.css

entry-button.css

8 ms

button-counter.gif

button-counter.gif

3 ms

SEO Factors

citrulline.jp.net SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citrulline.jp.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed Japanese language. Our system also found out that Citrulline.jp.net 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

citrulline.jp.net

Open Graph description is not detected on the main page of Citrulline. 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: