Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

elgin.jp

エックスサーバー サーバー初期ページ

Page Load Speed

7.2 sec in total

First Response

788 ms

Resources Loaded

6 sec

Page Rendered

397 ms

elgin.jp screenshot

About Website

Visit elgin.jp now to see the best up-to-date Elgin content for Japan and also check out these interesting facts you probably never knew about elgin.jp

エルジン ELGIN 腕時計の専門店でございます。

Visit elgin.jp

Key Findings

We analyzed Elgin.jp page load time and found that the first response time was 788 ms 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

elgin.jp performance score

0

Network Requests Diagram

elgin.jp

788 ms

m_sys_common.css

317 ms

import.css

342 ms

script.js

357 ms

check_history.css

309 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Elgin.jp, 8% (8 requests) were made to Rakuten.ne.jp and 5% (5 requests) were made to Thumbnail.image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Elgin.jp.

Page Optimization Overview & Recommendations

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

Content Size

641.4 kB

After Optimization

483.8 kB

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

HTML Optimization

-82%

Potential reduce by 54.4 kB

  • Original 65.9 kB
  • After minification 59.0 kB
  • After compression 11.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 82% of the original size.

Image Optimization

-11%

Potential reduce by 56.4 kB

  • Original 515.3 kB
  • After minification 458.9 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. Obviously, Elgin needs image optimization as it can save up to 56.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-56%

Potential reduce by 5.0 kB

  • Original 9.0 kB
  • After minification 7.1 kB
  • After compression 4.0 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 5.0 kB or 56% of the original size.

CSS Optimization

-82%

Potential reduce by 41.8 kB

  • Original 51.3 kB
  • After minification 40.4 kB
  • After compression 9.4 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. Elgin.jp needs all CSS files to be minified and compressed as it can save up to 41.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (52%)

Requests Now

101

After Optimization

48

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

SEO Factors

elgin.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elgin.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 Elgin.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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