Tools & Wizards About Us
materiars.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

materiars.jp

MATERI-ARS – 外の天気を部屋の中へ持ってこよう～自然エネルギーやグリーンなどで遊ぶ店舗デザインのマテリアルス

Page Load Speed

7.8 sec in total

First Response

1.5 sec

Resources Loaded

5.7 sec

Page Rendered

564 ms

materiars.jp screenshot

About Website

Visit materiars.jp now to see the best up-to-date MATERI ARS content and also check out these interesting facts you probably never knew about materiars.jp

外の天気を部屋の中へ持ってこよう～自然エネルギーやグリーンなどで遊ぶ店舗デザインのマテリアルス

Visit materiars.jp

Key Findings

We analyzed Materiars.jp page load time and found that the first response time was 1.5 sec and then it took 6.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

materiars.jp performance score

0

Network Requests Diagram

materiars.jp

1497 ms

newstyle.css

168 ms

contents.css

337 ms

jquery-1.9.1.min.js

520 ms

jquery.nivo.slider.pack.js

348 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 81% of them (21 requests) were addressed to the original Materiars.jp, 8% (2 requests) were made to Stats.g.doubleclick.net and 4% (1 request) were made to S.yjtag.jp. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Materiars.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.6 kB (6%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Materiars.jp main page is 3.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. 20% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 8.6 kB

  • Original 12.9 kB
  • After minification 12.0 kB
  • After compression 4.3 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.6 kB or 67% of the original size.

Image Optimization

-3%

Potential reduce by 74.9 kB

  • Original 2.9 MB
  • After minification 2.8 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. MATERI ARS images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 93.1 kB

  • Original 160.5 kB
  • After minification 160.4 kB
  • After compression 67.4 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 93.1 kB or 58% of the original size.

CSS Optimization

-78%

Potential reduce by 7.0 kB

  • Original 8.9 kB
  • After minification 6.5 kB
  • After compression 1.9 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. Materiars.jp needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (20%)

Requests Now

25

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

materiars.jp

materiars.jp

1497 ms

newstyle.css

newstyle.css

168 ms

contents.css

contents.css

337 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

520 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

348 ms

nivo-slider.css

nivo-slider.css

361 ms

dc.js

dc.js

73 ms

logo.gif

logo.gif

240 ms

top7.jpg

top7.jpg

1947 ms

top8.jpg

top8.jpg

1888 ms

top9.jpg

top9.jpg

1462 ms

top10.jpg

top10.jpg

1382 ms

2.jpg

2.jpg

2097 ms

1.jpg

1.jpg

2202 ms

2.jpg

2.jpg

2960 ms

1.jpg

1.jpg

2986 ms

RealClothes(exterior).jpg

RealClothes(exterior).jpg

2276 ms

1.jpg

1.jpg

3286 ms

4.jpg

4.jpg

2782 ms

moobei.jpg

moobei.jpg

2869 ms

cuboblog.jpg

cuboblog.jpg

2609 ms

Facebook_logo.jpg

Facebook_logo.jpg

2918 ms

tag.js

tag.js

18 ms

__utm.gif

__utm.gif

19 ms

tag

tag

229 ms

ya.js

ya.js

330 ms

SEO Factors

materiars.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Materiars.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 Materiars.jp main page’s claimed encoding is shift_jis. 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

materiars.jp

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