17.2 sec in total
2.5 sec
14.2 sec
506 ms
Visit fc.family.co.jp now to see the best up-to-date Fc Family content for Japan and also check out these interesting facts you probably never knew about fc.family.co.jp
【公式】ファミリーマートは全力で加盟希望者のフランチャイズ経営の夢を応援いたします。オーナーの仕事の紹介や、契約内容・開店までの流れ、各種独立の制度、オーナー募集店舗や説明会の開催情報をご紹介しています。
Visit fc.family.co.jpWe analyzed Fc.family.co.jp page load time and found that the first response time was 2.5 sec and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fc.family.co.jp performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value28.5 s
0/100
25%
Value14.3 s
1/100
10%
Value1,000 ms
27/100
30%
Value1
2/100
15%
Value24.0 s
1/100
10%
2504 ms
310 ms
332 ms
507 ms
534 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 64% of them (126 requests) were addressed to the original Fc.family.co.jp, 13% (26 requests) were made to Family.co.jp and 3% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Fc.family.co.jp.
Page size can be reduced by 756.3 kB (43%)
1.7 MB
985.5 kB
In fact, the total size of Fc.family.co.jp main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 736.0 kB which makes up the majority of the site volume.
Potential reduce by 45.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 9.9 kB, which is 17% 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 45.9 kB or 79% of the original size.
Potential reduce by 55.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. Fc Family images are well optimized though.
Potential reduce by 437.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 437.7 kB or 59% of the original size.
Potential reduce by 217.7 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. Fc.family.co.jp needs all CSS files to be minified and compressed as it can save up to 217.7 kB or 88% of the original size.
Number of requests can be reduced by 63 (34%)
184
121
The browser has sent 184 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fc 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 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
fc.family.co.jp
2504 ms
import.css
310 ms
import_home2.css
332 ms
share.js
507 ms
cookie.js
534 ms
minmax.js
557 ms
jquery-1.7.1.js
1648 ms
common.js
694 ms
image_ch.js
869 ms
jquery-rollover.js
855 ms
jsapi
18 ms
areaDetection.js
1058 ms
jquery.js
875 ms
i_search_assist.js
896 ms
search_tool.js
998 ms
jquery.js
1534 ms
general.css
911 ms
layout.css
1093 ms
layout_2012.css
923 ms
general_2012.css
581 ms
module.css
1067 ms
individual.css
1290 ms
individual_company.css
869 ms
main.css
1467 ms
base.css
1089 ms
area.css
1347 ms
navi.css
1549 ms
elements.css
1800 ms
form.css
2020 ms
local2.css
2015 ms
s_retargeting.js
609 ms
conversion.js
18 ms
jquery.js
2529 ms
i_search_assist.js
924 ms
search_tool.js
807 ms
jquery.min.js
31 ms
js
47 ms
analytics.js
28 ms
body_bg_01.gif
174 ms
txt_sitename_01.gif
175 ms
header_logo_01.gif
170 ms
header_bt_search_01.gif
173 ms
img_footer_qr_01.gif
172 ms
img_footer_qr_02.gif
174 ms
txt_keyvisual_01.png
662 ms
tit_sitename_01.png
342 ms
txt_header_01.png
688 ms
txt_header_02.png
689 ms
txt_gnav_01.gif
353 ms
txt_gnav_05.gif
514 ms
txt_gnav_02.gif
651 ms
txt_gnav_04.gif
666 ms
left_ti_01.jpg
989 ms
left_ti_02.jpg
1132 ms
left_ti_02_002.gif
991 ms
left_ti_02_001.gif
1010 ms
left_ti_03.jpg
1201 ms
left_ti_04.jpg
1201 ms
bn_01.gif
1515 ms
bn_02.gif
1517 ms
bn_03.gif
1600 ms
bn_12.gif
1690 ms
bn_04.gif
1727 ms
bn_08.jpg
1754 ms
tit_interpretmap_01.gif
2237 ms
bt_interpretmap_01.gif
2055 ms
bt_interpretmap_02.gif
2102 ms
bt_interpretmap_03.gif
2218 ms
bt_interpretmap_04.gif
2228 ms
bt_interpretmap_05.gif
2269 ms
bt_interpretmap_06.gif
2605 ms
bt_interpretmap_07.gif
2593 ms
bt_interpretmap_08.gif
2704 ms
bt_interpretmap_09.gif
2763 ms
txt_tel_01.gif
2755 ms
bn_form_01.gif
2768 ms
bnr_area_03.png
3069 ms
bnr_area_02.jpg
3959 ms
tit_contractan_01.gif
3481 ms
ScriptServlet
43 ms
collect
19 ms
248 ms
collect
52 ms
bn_contractan_01.gif
3096 ms
43 ms
bn_contractan_02.gif
2937 ms
ga.js
13 ms
tit_support_01.gif
3114 ms
__utm.gif
12 ms
collect
11 ms
bn_support_01.gif
3044 ms
tit_owner_01.gif
3303 ms
bn_owner_01.gif
3256 ms
tit_ownerwork_01.gif
3537 ms
img_ownerwork_01.jpg
3691 ms
img_ownerwork_02.jpg
3594 ms
bnr_topics_5.gif
3557 ms
bnr_topics_2.gif
3609 ms
bnr_topics_3.gif
3632 ms
bnr_topics_1.gif
3719 ms
jsonp.js
351 ms
yahoo-min.js
367 ms
dom-min.js
372 ms
searchAssistTemplate.js
383 ms
iSearchAssistJSON.js
384 ms
headline_title_02.gif
3399 ms
headline_call.gif
3862 ms
text_call.gif
3532 ms
headline_mobile.gif
3734 ms
body_fm_bg_04.jpg
180 ms
gtm.js
66 ms
header_frame.gif
175 ms
header_bt_sprite.gif
342 ms
header_frame_dot.gif
174 ms
header_frame_bar.gif
178 ms
header_frame_company.gif
320 ms
header_bt_company_sprite.gif
507 ms
header_frame_company_bar.gif
336 ms
ic_pagetop.gif
298 ms
line_footer_bg.gif
310 ms
footer_fm.gif
594 ms
footer_list_ttl_bg_bottom.gif
467 ms
footer_list_ttl_bg_top.gif
465 ms
footer_list_ttl_arw.gif
465 ms
footer_list_arw.gif
482 ms
footer_copy.gif
634 ms
__utm.gif
53 ms
fbevents.js
95 ms
65 ms
tag.js
46 ms
text_mobile.gif
3506 ms
87 ms
collect
41 ms
collect
18 ms
collect
16 ms
tag
8 ms
44 ms
97 ms
bottom_ti.gif
3279 ms
31 ms
32 ms
bg_bodyarea_01.png
3469 ms
bg_keyvisual_01.jpg
4954 ms
body_02.gif
3337 ms
body_bottom_02.gif
3317 ms
body_head_02.gif
3246 ms
allow_middle.gif
3314 ms
navi_left_hr.gif
3342 ms
allow_new_middle.gif
3488 ms
bg_interpretmap_01.jpg
3738 ms
bg_contractan_01.jpg
3712 ms
bg_support_01.jpg
3755 ms
bg_ownerwork_01.jpg
3846 ms
bg_ownerwork_02.gif
3324 ms
txt_ownerwork_01.gif
3630 ms
tit_ownerwork_02.gif
3790 ms
txt_ownerwork_02.gif
3417 ms
tit_ownerwork_03.gif
3666 ms
pt_circle.gif
3334 ms
headline_bg_02.gif
3460 ms
pt_h2_line.gif
3455 ms
ic-schedule.gif
3138 ms
topics_hr.gif
3211 ms
ic-manage.gif
3249 ms
bottom.gif
3084 ms
bottom_bottom.gif
3014 ms
bottom_head.gif
2944 ms
dt_bg.gif
2836 ms
txt_header_01_on.png
3237 ms
txt_header_02_on.png
3277 ms
txt_gnav_01_on.gif
2982 ms
txt_gnav_05_on.gif
2778 ms
txt_gnav_02_on.gif
2688 ms
common.js
20 ms
util.js
39 ms
stats.js
34 ms
AuthenticationService.Authenticate
264 ms
txt_gnav_04_on.gif
2675 ms
bt_interpretmap_01_on.gif
3043 ms
bt_interpretmap_02_on.gif
3022 ms
bt_interpretmap_03_on.gif
2932 ms
bt_interpretmap_04_on.gif
3059 ms
bt_interpretmap_05_on.gif
2921 ms
bt_interpretmap_06_on.gif
2939 ms
bt_interpretmap_07_on.gif
3140 ms
bt_interpretmap_08_on.gif
2946 ms
bt_interpretmap_09_on.gif
3073 ms
bn_contractan_01_on.gif
3062 ms
bn_contractan_02_on.gif
2755 ms
bn_support_01_on.gif
2539 ms
bn_owner_01_on.gif
2899 ms
bnr_topics_5_on.gif
2930 ms
bnr_topics_2_on.gif
2928 ms
bnr_topics_3_on.gif
2943 ms
bnr_topics_1_on.gif
2894 ms
ya.js
328 ms
fc.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fc.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fc.family.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fc.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 Fc.family.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.
fc.family.co.jp
Open Graph description is not detected on the main page of Fc 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: