19.2 sec in total
6.8 sec
12.2 sec
164 ms
Visit search.family.co.jp now to see the best up-to-date Search Family content for Japan and also check out these interesting facts you probably never knew about search.family.co.jp
あなたと、コンビに、ファミリーマート公式ウェブサイト。新商品紹介、キャンペーン情報など店舗サービスのご紹介。店舗検索、ファミマTカード、社会環境活動、企業情報掲載。
Visit search.family.co.jpWe analyzed Search.family.co.jp page load time and found that the first response time was 6.8 sec and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
search.family.co.jp performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value29.3 s
0/100
25%
Value9.5 s
12/100
10%
Value320 ms
77/100
30%
Value0.585
11/100
15%
Value23.3 s
1/100
10%
6848 ms
660 ms
846 ms
863 ms
1006 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 35% of them (25 requests) were addressed to the original Search.family.co.jp, 38% (27 requests) were made to Family.co.jp and 7% (5 requests) were made to I25.dga.jp. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Search.family.co.jp.
Page size can be reduced by 244.7 kB (64%)
381.1 kB
136.4 kB
In fact, the total size of Search.family.co.jp main page is 381.1 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. 25% of websites need less resources to load. Javascripts take 283.7 kB which makes up the majority of the site volume.
Potential reduce by 20.6 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 20.6 kB or 75% of the original size.
Potential reduce by 815 B
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. Search Family images are well optimized though.
Potential reduce by 180.1 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 180.1 kB or 63% of the original size.
Potential reduce by 43.1 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. Search.family.co.jp needs all CSS files to be minified and compressed as it can save up to 43.1 kB or 85% of the original size.
Number of requests can be reduced by 38 (56%)
68
30
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search Family. 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 10 to 1 for CSS and as a result speed up the page load time.
search.family.co.jp
6848 ms
import_external.css
660 ms
cookie.js
846 ms
share.js
863 ms
jquery.js
1006 ms
jquery.easing.1.3.js
546 ms
i_search_assist.js
362 ms
popup.js
736 ms
common.js
384 ms
i_search1.css
743 ms
i_search2.css
982 ms
i_search3.css
502 ms
search.css
741 ms
jquery.js
1468 ms
i_search_assist.js
1097 ms
search_tool.js
1147 ms
general_external.css
156 ms
layout_external.css
311 ms
general_2012_external.css
331 ms
layout_2012_external.css
699 ms
i_search_assist.js
1311 ms
search_tool.js
1447 ms
print_external.css
182 ms
jsonp.js
1090 ms
yahoo-min.js
1278 ms
dom-min.js
1318 ms
searchAssistTemplate.js
1146 ms
iSearchAssistJSON.js
2746 ms
header_logo_01.gif
182 ms
index.gif
335 ms
webshot.php
1067 ms
webshot.php
1246 ms
header_bt_search_01.gif
157 ms
btn_search.gif
175 ms
img_footer_qr_01.gif
172 ms
img_footer_qr_02.gif
177 ms
relation_back_top.gif
503 ms
relation_back_bottom.gif
862 ms
search_form_top.gif
355 ms
search_form_bottom.gif
357 ms
ranking_title.gif
364 ms
digiana_log.gif
498 ms
gtm.js
71 ms
body_fm_bg_05.jpg
167 ms
header_frame.gif
294 ms
header_bt_sprite.gif
485 ms
header_frame_dot.gif
329 ms
header_frame_bar.gif
319 ms
ic_pagetop.gif
327 ms
line_footer_bg.gif
315 ms
footer_fm.gif
432 ms
footer_list_ttl_bg_bottom.gif
484 ms
footer_list_ttl_bg_top.gif
480 ms
footer_list_ttl_arw.gif
493 ms
footer_list_arw.gif
507 ms
footer_copy.gif
586 ms
relation_back.gif
499 ms
leftmenu_g_bg_01.gif
679 ms
leftmenu_g_bg_02.gif
514 ms
leftmenu_g_bg_04.gif
633 ms
leftmenu_g_bg_03.gif
635 ms
com_line_01.gif
676 ms
ga.js
31 ms
fbevents.js
88 ms
analytics.js
11 ms
__utm.gif
15 ms
dummy_popup.gif
790 ms
popup_back.gif
878 ms
collect
56 ms
collect
10 ms
collect
76 ms
23 ms
search.family.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
search.family.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
search.family.co.jp SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Search.family.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 Search.family.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.
search.family.co.jp
Open Graph description is not detected on the main page of Search Family. 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: