Tools & Wizards About Us
ansinkan.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ansinkan.jp

非常食専門店生活安心館

Page Load Speed

5.7 sec in total

First Response

572 ms

Resources Loaded

4.9 sec

Page Rendered

201 ms

ansinkan.jp screenshot

About Website

Welcome to ansinkan.jp homepage info - get ready to check Ansinkan best content right away, or after learning these important things about ansinkan.jp

有限会社　生活安心館では、団体用防災食、非常食の販売及びアドバイザーを行っております。

Visit ansinkan.jp

Key Findings

We analyzed Ansinkan.jp page load time and found that the first response time was 572 ms and then it took 5.1 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

ansinkan.jp performance score

0

Network Requests Diagram

ansinkan.jp

572 ms

www.ansinkan.jp

808 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css

1069 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

1239 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

536 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 63% of them (22 requests) were addressed to the original Ansinkan.jp, 37% (13 requests) were made to Web.xaas.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ansinkan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 342.1 kB (27%)

Content Size

1.2 MB

After Optimization

905.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ansinkan.jp main page is 1.2 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 811.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.9 kB

  • Original 22.1 kB
  • After minification 19.1 kB
  • After compression 5.2 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 3.0 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 16.9 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 7.2 kB

  • Original 811.1 kB
  • After minification 804.0 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. Ansinkan images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 184.7 kB

  • Original 249.9 kB
  • After minification 249.0 kB
  • After compression 65.2 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 184.7 kB or 74% of the original size.

CSS Optimization

-81%

Potential reduce by 133.3 kB

  • Original 164.7 kB
  • After minification 155.2 kB
  • After compression 31.4 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. Ansinkan.jp needs all CSS files to be minified and compressed as it can save up to 133.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (39%)

Requests Now

33

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ansinkan.jp

ansinkan.jp

572 ms

www.ansinkan.jp

www.ansinkan.jp

808 ms

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css

A.jqselectable.css+prettyphoto.css+popup.css+base.css+print.css+layout.css,,q20150708+jqtransform.css,Mcc._Rn03G5v2q.css.pagespeed.cf.1FlClNpo4U.css

1069 ms

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

jquery_v2.1.4.js.pagespeed.jm.UWusawvZ2R.js

1239 ms

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

ajax_v2016.js.pagespeed.jm.IhMMOvTC75.js

536 ms

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

jcarousellite_v1.1.js.pagespeed.jm.wtlzVdCKLg.js

531 ms

mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js

mousewheel_v3.1.13.js.pagespeed.jm.wBwlG6vk-c.js

555 ms

jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js

jscrollpane.js.pagespeed.jm.2wYEC_BNG3.js

742 ms

treeview.js.pagespeed.jm.Ccxdh7coVu.js

treeview.js.pagespeed.jm.Ccxdh7coVu.js

709 ms

common_v2016.js.pagespeed.jm.6iGU-6_f5J.js

common_v2016.js.pagespeed.jm.6iGU-6_f5J.js

943 ms

prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js

prettyphoto_v3.1.6.js,q20150527.pagespeed.jm.w2fGLjjfmp.js

941 ms

theme.css

theme.css

577 ms

addStyle.css

addStyle.css

405 ms

information.js.pagespeed.jm.95f-nsecLq.js

information.js.pagespeed.jm.95f-nsecLq.js

736 ms

hdr_bg.jpg

hdr_bg.jpg

577 ms

xspace.gif.pagespeed.ic.lRMfmktUso.png

xspace.gif.pagespeed.ic.lRMfmktUso.png

181 ms

logo.jpg

logo.jpg

776 ms

main_img.jpg

main_img.jpg

2463 ms

icn_home.gif

icn_home.gif

361 ms

sdr_img001.gif

sdr_img001.gif

582 ms

sdr_img002.gif

sdr_img002.gif

405 ms

bnr_img001.jpg

bnr_img001.jpg

1411 ms

bnr_img002.jpg

bnr_img002.jpg

1680 ms

bnr_img003.jpg

bnr_img003.jpg

1136 ms

bnr_img004.jpg

bnr_img004.jpg

1149 ms

bnr_img005.jpg

bnr_img005.jpg

1568 ms

index

index

1515 ms

loading_icon.gif

loading_icon.gif

384 ms

space.gif

space.gif

196 ms

bg_footer.gif

bg_footer.gif

1343 ms

index

index

1908 ms

icn_h_information.gif

icn_h_information.gif

203 ms

bg_border01.gif

bg_border01.gif

199 ms

icn_h_calendar.gif

icn_h_calendar.gif

202 ms

icn_arrow05.gif

icn_arrow05.gif

200 ms

SEO Factors

ansinkan.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

ansinkan.jp

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