Tools & Wizards About Us
vague-project.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vague-project.co.jp

糖鎖サプリメントの通販ショップ - プレシード2

Page Load Speed

4.1 sec in total

First Response

731 ms

Resources Loaded

3.2 sec

Page Rendered

197 ms

vague-project.co.jp screenshot

About Website

Welcome to vague-project.co.jp homepage info - get ready to check Vague Project best content right away, or after learning these important things about vague-project.co.jp

糖鎖(とうさ)栄養素を含む健康食品/サプリメント通販ならアクアネクスト・オンライン。

Visit vague-project.co.jp

Key Findings

We analyzed Vague-project.co.jp page load time and found that the first response time was 731 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

vague-project.co.jp performance score

0

Network Requests Diagram

vague-project.co.jp

731 ms

order.css

370 ms

imageMenu.css

343 ms

prototype.js

1051 ms

effects.js

876 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that all of those requests were addressed to Vague-project.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Vague-project.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.4 kB (28%)

Content Size

460.5 kB

After Optimization

332.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vague-project.co.jp main page is 460.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Images take 300.7 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 8.2 kB

  • Original 12.7 kB
  • After minification 12.5 kB
  • After compression 4.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 8.2 kB or 64% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 300.7 kB
  • After minification 300.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. Vague Project images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 117.2 kB

  • Original 143.1 kB
  • After minification 104.8 kB
  • After compression 25.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 117.2 kB or 82% of the original size.

CSS Optimization

-76%

Potential reduce by 3.0 kB

  • Original 3.9 kB
  • After minification 2.8 kB
  • After compression 917 B

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. Vague-project.co.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

29

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vague-project.co.jp

vague-project.co.jp

731 ms

order.css

order.css

370 ms

imageMenu.css

imageMenu.css

343 ms

prototype.js

prototype.js

1051 ms

effects.js

effects.js

876 ms

accordion.js

accordion.js

532 ms

top.js

top.js

365 ms

h1_title.gif

h1_title.gif

179 ms

bg-top.gif

bg-top.gif

185 ms

btn_home.jpg

btn_home.jpg

191 ms

btn_law.gif

btn_law.gif

185 ms

btn_policy.gif

btn_policy.gif

177 ms

btn_inquiry.gif

btn_inquiry.gif

176 ms

btn_company.gif

btn_company.gif

344 ms

btn_cart.jpg

btn_cart.jpg

350 ms

mpleseed2.jpg

mpleseed2.jpg

349 ms

pleseed2.jpg

pleseed2.jpg

1055 ms

m10days.jpg

m10days.jpg

362 ms

10days.jpg

10days.jpg

983 ms

mlutein.jpg

mlutein.jpg

511 ms

lutein.jpg

lutein.jpg

1196 ms

mmobile.jpg

mmobile.jpg

523 ms

mobile.jpg

mobile.jpg

1091 ms

jozuka.jpg

jozuka.jpg

1049 ms

jozuka02.jpg

jozuka02.jpg

864 ms

jozuka01.jpg

jozuka01.jpg

1385 ms

btn_pleseed2.jpg

btn_pleseed2.jpg

1522 ms

btn_10days.jpg

btn_10days.jpg

1570 ms

btn_lutein.jpg

btn_lutein.jpg

1227 ms

bg-bottom.gif

bg-bottom.gif

1258 ms

acclog.cgi

acclog.cgi

618 ms

SEO Factors

vague-project.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vague-project.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vague-project.co.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

vague-project.co.jp

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