Tools & Wizards About Us
fcart.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fcart.jp

【赤すぐ】～マタニティ・ベビー・子供用品の通販サイト 赤すぐ～

Page Load Speed

8.7 sec in total

First Response

1.3 sec

Resources Loaded

7.2 sec

Page Rendered

201 ms

fcart.jp screenshot

About Website

Welcome to fcart.jp homepage info - get ready to check Fcart best content for Japan right away, or after learning these important things about fcart.jp

赤すぐは、雑誌「赤すぐ」「妊すぐ」に掲載しているマタニティグッズやベビー用品の通販サイトです。妊婦さんやママのための機能的でオシャレなマタニティウェアや授乳服、赤ちゃんやキッズのための可愛いベビー服や子供服、さらにはマザーズバック、ベビーカー、赤すぐ限定商品まで、豊富に商品をご用意しています。

Visit fcart.jp

Key Findings

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

fcart.jp performance score

0

Network Requests Diagram

fcart.jp

1311 ms

common.css

458 ms

flat.style.css

452 ms

top_201305.css

493 ms

jquery.suggest.css

345 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Fcart.jp, 9% (5 requests) were made to Cdn.akasugu.fcart.jp and 2% (1 request) were made to Akasugu.fcart.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fcart.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 558.9 kB (37%)

Content Size

1.5 MB

After Optimization

968.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 26.7 kB

  • Original 35.4 kB
  • After minification 30.5 kB
  • After compression 8.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 4.9 kB, which is 14% 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 26.7 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 22.9 kB

  • Original 823.1 kB
  • After minification 800.2 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. Fcart images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 402.6 kB

  • Original 540.2 kB
  • After minification 448.9 kB
  • After compression 137.7 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 402.6 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 106.7 kB

  • Original 128.3 kB
  • After minification 114.0 kB
  • After compression 21.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. Fcart.jp needs all CSS files to be minified and compressed as it can save up to 106.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (38%)

Requests Now

56

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fcart.jp

fcart.jp

1311 ms

common.css

common.css

458 ms

flat.style.css

flat.style.css

452 ms

top_201305.css

top_201305.css

493 ms

jquery.suggest.css

jquery.suggest.css

345 ms

jquery.js

jquery.js

1093 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

190 ms

utils.js

utils.js

225 ms

suggest.js

suggest.js

247 ms

prototype.js

prototype.js

629 ms

common.js

common.js

300 ms

rollover.js

rollover.js

380 ms

linkset.js

linkset.js

415 ms

qr.js

qr.js

403 ms

window.js

window.js

478 ms

shadowbox.js

shadowbox.js

565 ms

link_external.js

link_external.js

552 ms

jquery.easing.js

jquery.easing.js

599 ms

lofslidernews.js

lofslidernews.js

642 ms

jquery.history.js

jquery.history.js

721 ms

jquery.cookie.js

jquery.cookie.js

756 ms

common.js

common.js

801 ms

s_code.js

s_code.js

785 ms

ysm00001.png

ysm00001.png

570 ms

yam00011.jpg

yam00011.jpg

857 ms

aka_ttl.jpg

aka_ttl.jpg

782 ms

uchiiwai_201312.jpg

uchiiwai_201312.jpg

566 ms

gift_201305.jpg

gift_201305.jpg

749 ms

akasugu_roulette_960_100.gif

akasugu_roulette_960_100.gif

505 ms

bn_eruca_180x90.png

bn_eruca_180x90.png

191 ms

bn_gochimaru_180x90.jpg

bn_gochimaru_180x90.jpg

419 ms

bnr_mail.png

bnr_mail.png

347 ms

bnr_fb.png

bnr_fb.png

534 ms

bnr_blog.png

bnr_blog.png

612 ms

thm_relate_02.jpg

thm_relate_02.jpg

671 ms

thm_relate_01.jpg

thm_relate_01.jpg

699 ms

bn_278x126_eruca.jpg

bn_278x126_eruca.jpg

829 ms

bn_278x126_oxrp_01.png

bn_278x126_oxrp_01.png

811 ms

bn_278x126_gochimaru.jpg

bn_278x126_gochimaru.jpg

838 ms

copyright.gif

copyright.gif

857 ms

y0000290.png

y0000290.png

528 ms

ysb00001.png

ysb00001.png

414 ms

200302.png

200302.png

542 ms

utiiwai_180x90.jpg

utiiwai_180x90.jpg

545 ms

headerAjaxJs.js

headerAjaxJs.js

943 ms

base.png

base.png

1079 ms

load-indicator.gif

load-indicator.gif

361 ms

top_common.png

top_common.png

377 ms

category_01.png

category_01.png

263 ms

style.png

style.png

203 ms

bg_footer_b.png

bg_footer_b.png

198 ms

bg_footer_t.png

bg_footer_t.png

175 ms

lin_dot.png

lin_dot.png

169 ms

page

page

1077 ms

5CnFDRy2IM2A

5CnFDRy2IM2A

301 ms

arrow_current.png

arrow_current.png

202 ms

s43376934670377

s43376934670377

82 ms

SEO Factors

fcart.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcart.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 Fcart.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

fcart.jp

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