Tools & Wizards About Us
testshop.imobile.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

testshop.imobile.co.jp

オンラインショッピングモール GOGO!ショッピング

Page Load Speed

7.2 sec in total

First Response

2.2 sec

Resources Loaded

4.3 sec

Page Rendered

651 ms

testshop.imobile.co.jp screenshot

About Website

Click here to check amazing Testshop Imobile content for Japan. Otherwise, check out these important facts you probably never knew about testshop.imobile.co.jp

PC

Visit testshop.imobile.co.jp

Key Findings

We analyzed Testshop.imobile.co.jp page load time and found that the first response time was 2.2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

testshop.imobile.co.jp performance score

0

Network Requests Diagram

testshop.imobile.co.jp

2246 ms

common.css

301 ms

common.css

346 ms

layout.css

349 ms

style.css

348 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Testshop.imobile.co.jp, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to P8-test.imobile.co.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Testshop.imobile.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.3 kB (29%)

Content Size

833.2 kB

After Optimization

594.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Testshop.imobile.co.jp main page is 833.2 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. 20% of websites need less resources to load. Images take 544.9 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 58.6 kB

  • Original 63.3 kB
  • After minification 51.4 kB
  • After compression 4.7 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 11.9 kB, which is 19% 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 58.6 kB or 93% of the original size.

Image Optimization

-3%

Potential reduce by 17.9 kB

  • Original 544.9 kB
  • After minification 527.1 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. Testshop Imobile images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 97.2 kB

  • Original 147.1 kB
  • After minification 139.1 kB
  • After compression 49.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 97.2 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 64.7 kB

  • Original 77.9 kB
  • After minification 50.4 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. Testshop.imobile.co.jp needs all CSS files to be minified and compressed as it can save up to 64.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

54

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

testshop.imobile.co.jp

testshop.imobile.co.jp

2246 ms

common.css

common.css

301 ms

common.css

common.css

346 ms

layout.css

layout.css

349 ms

style.css

style.css

348 ms

shop.css

shop.css

820 ms

cart.css

cart.css

451 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

741 ms

css.js

css.js

450 ms

navi.js

navi.js

495 ms

win_op.js

win_op.js

496 ms

site.js

site.js

497 ms

rollover.js

rollover.js

599 ms

fixHeight.js

fixHeight.js

600 ms

customize.css

customize.css

649 ms

import.css

import.css

349 ms

main.css

main.css

152 ms

index.css

index.css

156 ms

products.css

products.css

156 ms

under.css

under.css

153 ms

under02.css

under02.css

158 ms

mypage.css

mypage.css

247 ms

window.css

window.css

302 ms

analytics.js

analytics.js

65 ms

bg_contents.gif

bg_contents.gif

1195 ms

header_bg.jpg

header_bg.jpg

452 ms

header_logo.png

header_logo.png

302 ms

gogotown_banner.jpg

gogotown_banner.jpg

303 ms

button_search.gif

button_search.gif

157 ms

gotitle_cat.jpg

gotitle_cat.jpg

156 ms

category_01_off.jpg

category_01_off.jpg

306 ms

category_02_off.jpg

category_02_off.jpg

306 ms

category_06_off.jpg

category_06_off.jpg

452 ms

category_03_off.jpg

category_03_off.jpg

457 ms

category_04_off.jpg

category_04_off.jpg

458 ms

category_05_off.jpg

category_05_off.jpg

460 ms

category_07_off.jpg

category_07_off.jpg

601 ms

category_08_off.jpg

category_08_off.jpg

602 ms

category_09_off.jpg

category_09_off.jpg

607 ms

main_image_sample.jpg

main_image_sample.jpg

1098 ms

03011557_56d53d4919f1e.jpg

03011557_56d53d4919f1e.jpg

611 ms

btn_item_page.png

btn_item_page.png

751 ms

03011556_56d53d105c76a.jpg

03011556_56d53d105c76a.jpg

755 ms

03011555_56d53cdfc242b.jpg

03011555_56d53cdfc242b.jpg

762 ms

03011554_56d53ca755f9f.jpg

03011554_56d53ca755f9f.jpg

765 ms

12111739_566a8bb97ee66.jpg

12111739_566a8bb97ee66.jpg

903 ms

12081737_566696e443d10.jpg

12081737_566696e443d10.jpg

901 ms

12021927_565ec796defc2.jpg

12021927_565ec796defc2.jpg

912 ms

10151148_543de08a622d7.jpg

10151148_543de08a622d7.jpg

921 ms

03201929_550bf672ed424.jpg

03201929_550bf672ed424.jpg

1052 ms

02021450_54cf100f940f4.jpg

02021450_54cf100f940f4.jpg

1054 ms

pagetop.png

pagetop.png

1062 ms

bg_header.png

bg_header.png

1312 ms

bg_footer.jpg

bg_footer.jpg

1153 ms

collect

collect

11 ms

collect

collect

25 ms

SEO Factors

testshop.imobile.co.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 Testshop.imobile.co.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 Testshop.imobile.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

testshop.imobile.co.jp

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