Tools & Wizards About Us
jzool.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jzool.jp

[簡単！手軽に！海外販売] 月920円からのJzool.comイージーマーケット

Page Load Speed

3.4 sec in total

First Response

497 ms

Resources Loaded

2.6 sec

Page Rendered

394 ms

jzool.jp screenshot

About Website

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

日本から直接、商品を海外販売する事に特化した出店型の海外向けECです。今なら月々920円から海外販売を始められます。初期費用無料で海外80カ国以上にネットで販売。

Visit jzool.jp

Key Findings

We analyzed Jzool.jp page load time and found that the first response time was 497 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Jzool.jp rating and web reputation

Performance Metrics

jzool.jp performance score

0

Network Requests Diagram

jzool.jp

497 ms

jquery-ui.css

10 ms

sprite.css

12 ms

buttons.css

13 ms

main.css

16 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 36% of them (24 requests) were addressed to the original Jzool.jp, 27% (18 requests) were made to Jzool-jp-public.s3.amazonaws.com and 12% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Jzool-jp-public.s3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 512.1 kB (70%)

Content Size

734.3 kB

After Optimization

222.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jzool.jp main page is 734.3 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. 60% of websites need less resources to load. Javascripts take 397.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 31.0 kB

  • Original 43.7 kB
  • After minification 42.3 kB
  • After compression 12.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. 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 31.0 kB or 71% of the original size.

Image Optimization

-63%

Potential reduce by 123.3 kB

  • Original 195.7 kB
  • After minification 72.4 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, Jzool needs image optimization as it can save up to 123.3 kB or 63% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 278.9 kB

  • Original 397.5 kB
  • After minification 383.0 kB
  • After compression 118.5 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 278.9 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 78.8 kB

  • Original 97.4 kB
  • After minification 74.5 kB
  • After compression 18.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. Jzool.jp needs all CSS files to be minified and compressed as it can save up to 78.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (50%)

Requests Now

64

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jzool.jp

jzool.jp

497 ms

jquery-ui.css

jquery-ui.css

10 ms

sprite.css

sprite.css

12 ms

buttons.css

buttons.css

13 ms

main.css

main.css

16 ms

forms.css

forms.css

12 ms

top_nav_company.css

top_nav_company.css

17 ms

page.css

page.css

17 ms

nivo-slider.css

nivo-slider.css

17 ms

pop.css

pop.css

17 ms

easy.css

easy.css

18 ms

easy_20141226.js

easy_20141226.js

27 ms

jquery.fancybox.css

jquery.fancybox.css

20 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

21 ms

.js

.js

185 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

21 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

20 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

21 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

22 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

22 ms

gmaps4rails.css

gmaps4rails.css

21 ms

jquery.socialbutton-1.8.1.js

jquery.socialbutton-1.8.1.js

21 ms

popbar_bottom.gif

popbar_bottom.gif

812 ms

all.js

all.js

289 ms

widgets.js

widgets.js

17 ms

plusone.js

plusone.js

104 ms

bg.png

bg.png

629 ms

jzool_logo_e.png

jzool_logo_e.png

1086 ms

jzool-easy-box1.png

jzool-easy-box1.png

1038 ms

low_price.png

low_price.png

669 ms

printing.png

printing.png

688 ms

noenglish.png

noenglish.png

795 ms

trans.png

trans.png

846 ms

shipped.png

shipped.png

863 ms

googlemap.gif

googlemap.gif

948 ms

bulb.png

bulb.png

904 ms

1.png

1.png

964 ms

2.png

2.png

1031 ms

3.png

3.png

1034 ms

4.png

4.png

1094 ms

yen.png

yen.png

1149 ms

videos.png

videos.png

1204 ms

vidsplash.jpg

vidsplash.jpg

354 ms

ajax-loader.gif

ajax-loader.gif

38 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

38 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

26 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

21 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

10 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

8 ms

fastbutton

fastbutton

134 ms

postmessageRelay

postmessageRelay

109 ms

64 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

30 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

19 ms

jot

jot

96 ms

xd_arbiter.php

xd_arbiter.php

229 ms

xd_arbiter.php

xd_arbiter.php

433 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

24 ms

rpc:shindig_random.js

rpc:shindig_random.js

38 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

16 ms

nr-885.min.js

nr-885.min.js

45 ms

ping

ping

37 ms

7f8e74b743

7f8e74b743

45 ms

like.php

like.php

63 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

480 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

545 ms

SEO Factors

jzool.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 Jzool.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 Jzool.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

jzool.jp

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