Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

guardian-stone.jp

パワーストーン・天然石の通販|Guardian.Stone ガーディアンストーン

Page Load Speed

8.2 sec in total

First Response

882 ms

Resources Loaded

7 sec

Page Rendered

374 ms

guardian-stone.jp screenshot

About Website

Visit guardian-stone.jp now to see the best up-to-date Guardian Stone content and also check out these interesting facts you probably never knew about guardian-stone.jp

パワーストーン・天然石の通販なら「Guardian.Stone ガーディアンストーン」へ。あなたの願いをこめたオーダーメイドアクセサリーもお作りします。大田区池上の実店舗でも購入いただけます。

Visit guardian-stone.jp

Key Findings

We analyzed Guardian-stone.jp page load time and found that the first response time was 882 ms and then it took 7.3 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

guardian-stone.jp performance score

0

Network Requests Diagram

guardian-stone.jp

882 ms

www.guardian-stone.jp

1096 ms

import.css

316 ms

mt.js

484 ms

cube.site.js

338 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 93% of them (81 requests) were addressed to the original Guardian-stone.jp, 2% (2 requests) were made to Apis.google.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Guardian-stone.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.9 kB (7%)

Content Size

2.7 MB

After Optimization

2.5 MB

In fact, the total size of Guardian-stone.jp main page is 2.7 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 15.5 kB

  • Original 20.7 kB
  • After minification 19.8 kB
  • After compression 5.2 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 15.5 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

  • Original 2.5 MB
  • After minification 2.4 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. Guardian Stone images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 132.9 kB

  • Original 175.8 kB
  • After minification 139.0 kB
  • After compression 42.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 132.9 kB or 76% of the original size.

CSS Optimization

-79%

Potential reduce by 25.2 kB

  • Original 31.8 kB
  • After minification 23.5 kB
  • After compression 6.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. Guardian-stone.jp needs all CSS files to be minified and compressed as it can save up to 25.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (36%)

Requests Now

85

After Optimization

54

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

SEO Factors

guardian-stone.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 Guardian-stone.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 Guardian-stone.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

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