Tools & Wizards About Us
family.every-one.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

family.every-one.co.jp

ココストア・エブリワンのホームページ閉鎖のおしらせ｜FamilyMart

Page Load Speed

6.5 sec in total

First Response

1.7 sec

Resources Loaded

4.5 sec

Page Rendered

272 ms

family.every-one.co.jp screenshot

About Website

Welcome to family.every-one.co.jp homepage info - get ready to check Family Every One best content for Japan right away, or after learning these important things about family.every-one.co.jp

ココストア・エブリワンのホームページは、2016年8月31日を持ちまして、閉鎖いたしました。

Visit family.every-one.co.jp

Key Findings

We analyzed Family.every-one.co.jp page load time and found that the first response time was 1.7 sec and then it took 4.8 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

family.every-one.co.jp performance score

0

Network Requests Diagram

family.every-one.co.jp

1745 ms

design.css

393 ms

stylesheet.css

820 ms

font.css

220 ms

analytics.js

40 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Family.every-one.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Family.co.jp. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Family.every-one.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 83.2 kB (25%)

Content Size

328.3 kB

After Optimization

245.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Family.every-one.co.jp main page is 328.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. 15% of websites need less resources to load. Images take 214.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.4 kB

  • Original 35.3 kB
  • After minification 30.6 kB
  • After compression 6.9 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.7 kB, which is 13% 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 28.4 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 747 B

  • Original 214.2 kB
  • After minification 213.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. Family Every One images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 22.0 kB

  • Original 25.8 kB
  • After minification 16.9 kB
  • After compression 3.8 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. Family.every-one.co.jp needs all CSS files to be minified and compressed as it can save up to 22.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (36%)

Requests Now

50

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

family.every-one.co.jp

family.every-one.co.jp

1745 ms

design.css

design.css

393 ms

stylesheet.css

stylesheet.css

820 ms

font.css

font.css

220 ms

analytics.js

analytics.js

40 ms

footer_copy.gif

footer_copy.gif

670 ms

bg.gif

bg.gif

219 ms

logo.gif

logo.gif

393 ms

header_storesearch.gif

header_storesearch.gif

209 ms

header_search.gif

header_search.gif

385 ms

header_searchbtn.gif

header_searchbtn.gif

391 ms

logo_famima.gif

logo_famima.gif

608 ms

navi01_o.gif

navi01_o.gif

415 ms

navi02.gif

navi02.gif

432 ms

navi03.gif

navi03.gif

577 ms

navi04.gif

navi04.gif

588 ms

spacer.gif

spacer.gif

588 ms

title_fair.gif

title_fair.gif

619 ms

rss.gif

rss.gif

647 ms

ya_pi.gif

ya_pi.gif

770 ms

tukiwari.gif

tukiwari.gif

783 ms

otokuwari.gif

otokuwari.gif

783 ms

getfile.asp

getfile.asp

812 ms

getfile.asp

getfile.asp

825 ms

getfile.asp

getfile.asp

866 ms

newwin.gif

newwin.gif

961 ms

getfile.asp

getfile.asp

980 ms

title_news.gif

title_news.gif

974 ms

ya_or.gif

ya_or.gif

1013 ms

title_konsyu.gif

title_konsyu.gif

1027 ms

getfile.asp

getfile.asp

1083 ms

ya_bu.gif

ya_bu.gif

1152 ms

title_bottom.gif

title_bottom.gif

1167 ms

title_osusume.gif

title_osusume.gif

1173 ms

getfile.asp

getfile.asp

1219 ms

getfile.asp

getfile.asp

1233 ms

getfile.asp

getfile.asp

1300 ms

getfile.asp

getfile.asp

1349 ms

btn_yakitatepan.jpg

btn_yakitatepan.jpg

1361 ms

btn_dekitatebento.jpg

btn_dekitatebento.jpg

1366 ms

ebook.jpg

ebook.jpg

1625 ms

btn_mado.gif

btn_mado.gif

1423 ms

collect

collect

11 ms

btn_qa.gif

btn_qa.gif

1315 ms

blanklink.gif

blanklink.gif

1332 ms

everyone_default.jpg

everyone_default.jpg

1958 ms

title_back.gif

title_back.gif

1181 ms

ten_be.gif

ten_be.gif

1258 ms

footer_line01.gif

footer_line01.gif

1323 ms

footer_icon.gif

footer_icon.gif

1313 ms

arrow_green.gif

arrow_green.gif

1189 ms

SEO Factors

family.every-one.co.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 Family.every-one.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 Family.every-one.co.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

family.every-one.co.jp

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