15.4 sec in total
364 ms
14.4 sec
615 ms
Click here to check amazing Fami Geki content for Japan. Otherwise, check out these important facts you probably never knew about fami-geki.com
ドラマ、アニメ、バラエティ…人気番組が大集合!ファミリー劇場は「あなたの見たい」を満足させる24時間ゴールデンタイムチャンネルです。
Visit fami-geki.comWe analyzed Fami-geki.com page load time and found that the first response time was 364 ms and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fami-geki.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value56.7 s
0/100
25%
Value42.0 s
0/100
10%
Value7,430 ms
0/100
30%
Value0.383
27/100
15%
Value52.7 s
0/100
10%
364 ms
349 ms
1492 ms
77 ms
889 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 61% of them (98 requests) were addressed to the original Fami-geki.com, 4% (6 requests) were made to Googletagmanager.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Fami-geki.com.
Page size can be reduced by 386.3 kB (5%)
8.3 MB
7.9 MB
In fact, the total size of Fami-geki.com main page is 8.3 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. 70% of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.
Potential reduce by 97.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 30.6 kB, which is 27% 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 97.9 kB or 85% of the original size.
Potential reduce by 30.1 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. Fami Geki images are well optimized though.
Potential reduce by 186.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 186.5 kB or 52% of the original size.
Potential reduce by 71.9 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. Fami-geki.com needs all CSS files to be minified and compressed as it can save up to 71.9 kB or 77% of the original size.
Number of requests can be reduced by 88 (57%)
154
66
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fami Geki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fami-geki.com
364 ms
www.fami-geki.com
349 ms
www.fami-geki.com
1492 ms
gtm.js
77 ms
style.css
889 ms
slick.css
568 ms
slick-theme.css
568 ms
owl.carousel.css
568 ms
all.css
44 ms
jquery.min.js
24 ms
slick.min.js
739 ms
owl.carousel.min.js
1009 ms
common.js
1071 ms
index.js
1083 ms
jquery.matchHeight.js
1084 ms
js
48 ms
js
108 ms
destination
106 ms
uwt.js
29 ms
analytics.js
98 ms
destination
99 ms
linkid.js
129 ms
conversion.js
133 ms
s_retargeting.js
712 ms
adsct
172 ms
adsct
101 ms
collect
18 ms
collect
41 ms
adsct
93 ms
adsct
94 ms
adsct
189 ms
adsct
121 ms
collect
50 ms
collect
25 ms
header_logo.png
449 ms
nav_icon_about.png
622 ms
nav_icon_tw.png
621 ms
nav_icon_yt.png
627 ms
nav_icon_fb.png
626 ms
head_search_icon.png
627 ms
sp_head_icon_time.png
967 ms
sp_head_icon_how.png
1122 ms
sp_head_icon_present.png
1123 ms
sp_head_icon_mail.png
1123 ms
slider_7223_pc.jpg
2179 ms
sp_menu_tw.png
1160 ms
sp_menu_fb.png
1470 ms
sp_menu_yt.png
1621 ms
head_sp_guide_icon.png
1624 ms
howto.jpg
1639 ms
slider_7222_pc.jpg
2885 ms
slider_7221_pc.jpg
3084 ms
slider_7220_pc.jpg
3174 ms
slider_7219_pc.jpg
3048 ms
slider_7218_pc.jpg
3242 ms
slider_7217_pc.jpg
5036 ms
slider_7216_pc.jpg
4500 ms
l.jpg
4082 ms
l.jpg
4121 ms
l.jpg
4343 ms
l.jpg
3747 ms
l.jpg
4817 ms
l.jpg
5115 ms
l.jpg
4812 ms
l.jpg
5013 ms
l.jpg
5168 ms
l.jpg
5489 ms
l.jpg
5332 ms
l.jpg
5707 ms
l.jpg
5704 ms
sdk.js
89 ms
widgets.js
221 ms
fbevents.js
5 ms
itm.js
198 ms
conversion.js
683 ms
ytag.js
708 ms
c5h23piji1
174 ms
sdk.js
104 ms
164 ms
segmentation.js
145 ms
cmt.js
33 ms
clarity.js
29 ms
adsct
32 ms
adsct
26 ms
30 ms
segment
400 ms
cnt
841 ms
slick.svg
5343 ms
l.jpg
5240 ms
l.jpg
5606 ms
l.jpg
5729 ms
l.jpg
5750 ms
l.jpg
6087 ms
gtm.js
32 ms
tdim-1.2.0.min.js
115 ms
beacon.html
118 ms
lt.js
17 ms
err.gif
827 ms
conversion_async.js
1334 ms
cnt
652 ms
log.js
35 ms
tracker
258 ms
collect
170 ms
l.jpg
5869 ms
special_bnr_8_pc.png
5427 ms
special_bnr_45_pc.png
5817 ms
about_character.png
5754 ms
plus_logo.png
5737 ms
about_icon.png
5584 ms
tel_icon.png
5596 ms
sns_x.png
5712 ms
sns_fb.png
5774 ms
608 ms
sns_yt.png
5236 ms
top_no_icon1.png
4569 ms
l.jpg
4694 ms
top_no_icon2.png
4651 ms
l.jpg
4854 ms
top_no_icon3.png
4670 ms
l.jpg
4702 ms
btm_bnr_12.jpg
3888 ms
banner_skp4.png
4116 ms
btm_bnr_07.jpg
3934 ms
btm_bnr_17.jpg
3932 ms
btm_bnr_21.png
3660 ms
btm_bnr_02.jpg
3731 ms
btm_bnr_11.jpg
3725 ms
btm_bnr_09.jpg
3760 ms
btm_bnr_22.png
3838 ms
btm_bnr_23.png
3779 ms
b_pagetop_pc.gif
3679 ms
footer_ssl.gif
3562 ms
footer_ssl_sp.gif
3533 ms
menu_time_icon.png
3591 ms
menu_time_grass.png
3662 ms
btm_arw.png
3629 ms
menu_arrow.png
3290 ms
search_icon.png
3218 ms
menu_time_present.png
3386 ms
menu_time_mail.png
3269 ms
menu_time_know.png
3261 ms
blank_img.png
3156 ms
fami_ttl_icon.png
3159 ms
ic_footer_link_arrow_w.png
3195 ms
ic_footer_link_arrow.png
3363 ms
ic_nowonair.jpg
3302 ms
b_onair_prev.gif
3281 ms
b_onair_next.gif
3175 ms
beacon.html
14 ms
pixel
57 ms
tap.php
49 ms
Pug
42 ms
set
219 ms
pixel
57 ms
sync
694 ms
report
800 ms
bounce
10 ms
sd
27 ms
c.gif
8 ms
sync
225 ms
fami-geki.com 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-hidden="true"] elements contain focusable descendents
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
fami-geki.com 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
fami-geki.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 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 Fami-geki.com 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 Fami-geki.com 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.
fami-geki.com
Open Graph data is detected on the main page of Fami Geki. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: