7.3 sec in total
1.5 sec
5.5 sec
259 ms
Visit faq.family.co.jp now to see the best up-to-date Faq Family content for Japan and also check out these interesting facts you probably never knew about faq.family.co.jp
お問い合わせトップ | FamilyMart
Visit faq.family.co.jpWe analyzed Faq.family.co.jp page load time and found that the first response time was 1.5 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
faq.family.co.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value10.2 s
0/100
25%
Value9.5 s
11/100
10%
Value130 ms
96/100
30%
Value0.046
99/100
15%
Value9.0 s
34/100
10%
1540 ms
515 ms
481 ms
510 ms
708 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 16% of them (12 requests) were addressed to the original Faq.family.co.jp, 61% (47 requests) were made to Family.co.jp and 6% (5 requests) were made to Cache.dga.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Faq.family.co.jp.
Page size can be reduced by 332.9 kB (69%)
481.8 kB
148.9 kB
In fact, the total size of Faq.family.co.jp main page is 481.8 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 262.6 kB which makes up the majority of the site volume.
Potential reduce by 28.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.9 kB, which is 11% 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.2 kB or 77% of the original size.
Potential reduce by 1.6 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. Obviously, Faq Family needs image optimization as it can save up to 1.6 kB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 145.5 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 145.5 kB or 55% of the original size.
Potential reduce by 157.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. Faq.family.co.jp needs all CSS files to be minified and compressed as it can save up to 157.6 kB or 88% of the original size.
Number of requests can be reduced by 38 (52%)
73
35
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faq 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 16 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
faq.family.co.jp
1540 ms
import.css
515 ms
cookie.js
481 ms
share.js
510 ms
iasks.css
708 ms
jquery.js
1340 ms
jquery.bnrCorner.js
902 ms
i_search_assist.js
1305 ms
search_tool.js
1327 ms
jquery.js
1381 ms
general.css
329 ms
layout.css
818 ms
module.css
850 ms
individual.css
896 ms
left_navi.css
370 ms
general_2012.css
492 ms
layout_2012.css
922 ms
print.css
348 ms
i_search_assist.js
1070 ms
search_tool.js
1089 ms
jsonp.js
750 ms
yahoo-min.js
763 ms
dom-min.js
771 ms
searchAssistTemplate.js
773 ms
iSearchAssistJSON.js
791 ms
body_fm_bg_05.jpg
342 ms
header_logo_01.gif
166 ms
header_bt_search_01.gif
198 ms
leftmenu_g_navi_oth.gif
181 ms
header_bt_search.gif
166 ms
inquiry_tien_02.gif
172 ms
inquiry_tellno_01.gif
186 ms
inquiry_tien_01.gif
330 ms
inquiry_tien_03.gif
328 ms
ft_tellno_01.gif
342 ms
ft_tellno_02.gif
359 ms
ft_tellno_03.gif
369 ms
img_footer_qr_01.gif
391 ms
img_footer_qr_02.gif
491 ms
main_bg_09.gif
343 ms
mark_new.gif
352 ms
ft_title02.gif
365 ms
i-ask_logo_s.gif
371 ms
gtm.js
74 ms
body_fm_bg_05.jpg
476 ms
header_frame.gif
497 ms
header_bt_sprite.gif
523 ms
header_frame_dot.gif
538 ms
header_frame_bar.gif
563 ms
leftmenu_g_bg_01.gif
583 ms
leftmenu_g_bg_02.gif
584 ms
leftmenu_g_bg_04.gif
610 ms
leftmenu_g_bg_03.gif
654 ms
com_g_arrow_01.gif
667 ms
com_line_01.gif
711 ms
main_bg_11.gif
746 ms
main_bg_12.gif
748 ms
com_ic_16.gif
779 ms
region_ic_04.gif
826 ms
com_g_arrow_02.gif
848 ms
com_line_04.gif
905 ms
ic_pagetop.gif
908 ms
line_footer_bg.gif
911 ms
footer_fm.gif
948 ms
footer_list_ttl_bg_bottom.gif
1004 ms
footer_list_ttl_bg_top.gif
1032 ms
footer_list_ttl_arw.gif
1099 ms
ga.js
28 ms
analytics.js
27 ms
fbevents.js
83 ms
__utm.gif
15 ms
collect
53 ms
collect
10 ms
collect
62 ms
footer_list_arw.gif
984 ms
footer_copy.gif
987 ms
103 ms
faq.family.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
faq.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
faq.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
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 doesn't use legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faq.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 Faq.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.
faq.family.co.jp
Open Graph description is not detected on the main page of Faq 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: