Tools & Wizards About Us
spigen.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

spigen.co.jp

買える場所/売ってる場所を知れるメディア｜カウシル |

Page Load Speed

8.9 sec in total

First Response

444 ms

Resources Loaded

8.2 sec

Page Rendered

248 ms

spigen.co.jp screenshot

About Website

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

iPhoneケース、スマホカバーブランドSpigen公式ストアです。会員登録で”すぐに使える”400ポイント進呈中！

Visit spigen.co.jp

Key Findings

We analyzed Spigen.co.jp page load time and found that the first response time was 444 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

spigen.co.jp performance score

0

Network Requests Diagram

spigen.co.jp

444 ms

www.spigen.co.jp

459 ms

common.css

184 ms

pcmax.css

348 ms

tablet.css

359 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 80% of them (40 requests) were addressed to the original Spigen.co.jp, 10% (5 requests) were made to Google-analytics.com and 6% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Spigen.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 924.4 kB (24%)

Content Size

3.9 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 24.5 kB

  • Original 29.6 kB
  • After minification 23.5 kB
  • After compression 5.1 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. This page needs HTML code to be minified as it can gain 6.1 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.5 kB or 83% of the original size.

Image Optimization

-15%

Potential reduce by 500.0 kB

  • Original 3.3 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. Obviously, Spigen needs image optimization as it can save up to 500.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-81%

Potential reduce by 343.9 kB

  • Original 422.3 kB
  • After minification 232.3 kB
  • After compression 78.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 343.9 kB or 81% of the original size.

CSS Optimization

-81%

Potential reduce by 56.1 kB

  • Original 69.3 kB
  • After minification 47.1 kB
  • After compression 13.2 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. Spigen.co.jp needs all CSS files to be minified and compressed as it can save up to 56.1 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spigen.co.jp

spigen.co.jp

444 ms

www.spigen.co.jp

www.spigen.co.jp

459 ms

common.css

common.css

184 ms

pcmax.css

pcmax.css

348 ms

tablet.css

tablet.css

359 ms

sp.css

sp.css

361 ms

flexslider.css

flexslider.css

364 ms

owl.carousel.css

owl.carousel.css

367 ms

owl.theme.css

owl.theme.css

374 ms

mobile-menu.css

mobile-menu.css

518 ms

jqmin.1.10.1.js

jqmin.1.10.1.js

1084 ms

jquery.flexslider.js

jquery.flexslider.js

544 ms

owl.carousel.js

owl.carousel.js

547 ms

jquery.mobile-menu.js

jquery.mobile-menu.js

549 ms

analytics.js

analytics.js

88 ms

fbevents.js

fbevents.js

88 ms

logo.png

logo.png

183 ms

magnifying.png

magnifying.png

188 ms

menubanner-stylering_01.jpg

menubanner-stylering_01.jpg

1034 ms

slideshow_1.jpg

slideshow_1.jpg

1219 ms

slideshow_2.jpg

slideshow_2.jpg

1956 ms

slideshow_3.jpg

slideshow_3.jpg

1951 ms

slideshow_4.jpg

slideshow_4.jpg

4159 ms

slideshow_5.jpg

slideshow_5.jpg

2869 ms

slideshow_7.jpg

slideshow_7.jpg

5717 ms

iphone6s.jpg

iphone6s.jpg

1390 ms

iphone6splus.jpg

iphone6splus.jpg

1562 ms

galaxys7.png

galaxys7.png

1736 ms

galaxys7edge.png

galaxys7edge.png

1906 ms

xperia_z5.jpg

xperia_z5.jpg

2079 ms

nexus6p.jpg

nexus6p.jpg

2300 ms

accessories.png

accessories.png

2311 ms

banner-middle01.jpg

banner-middle01.jpg

2250 ms

banner-middle02.jpg

banner-middle02.jpg

2592 ms

footer_icon_facebook.png

footer_icon_facebook.png

3000 ms

footer_icon_twitter.png

footer_icon_twitter.png

3206 ms

footer_icon_insta.png

footer_icon_insta.png

2935 ms

footer_icon_youtube.png

footer_icon_youtube.png

3717 ms

authentic.png

authentic.png

3276 ms

90_days.png

90_days.png

3175 ms

ecommerce.js

ecommerce.js

19 ms

collect

collect

62 ms

95 ms

collect

collect

9 ms

115 ms

134 ms

collect

collect

23 ms

collect

collect

24 ms

slidebar.png

slidebar.png

347 ms

flexslider-icon.woff

flexslider-icon.woff

368 ms

SEO Factors

spigen.co.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spigen.co.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Spigen.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

spigen.co.jp

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