6.2 sec in total
375 ms
5.4 sec
401 ms
Click here to check amazing Fanily content for Taiwan. Otherwise, check out these important facts you probably never knew about fanily.com.tw
如果你:愛娛樂八卦、愛藝術、愛棒球、愛古裝歷史、愛插畫動漫、愛買東西。來 Fanily 粉絲玩樂 就對了!
Visit fanily.com.twWe analyzed Fanily.com.tw page load time and found that the first response time was 375 ms 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.
fanily.com.tw performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value3.7 s
58/100
25%
Value2.6 s
97/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value2.4 s
98/100
10%
375 ms
2080 ms
186 ms
371 ms
556 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fanily.com.tw, 20% (12 requests) were made to S3-ap-northeast-1.amazonaws.com and 8% (5 requests) were made to I.ytimg.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Fanily.tw.
Page size can be reduced by 552.3 kB (32%)
1.8 MB
1.2 MB
In fact, the total size of Fanily.com.tw main page is 1.8 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. Images take 979.1 kB which makes up the majority of the site volume.
Potential reduce by 51.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. 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 51.2 kB or 73% of the original size.
Potential reduce by 413 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. Fanily images are well optimized though.
Potential reduce by 293.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 293.1 kB or 63% of the original size.
Potential reduce by 207.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. Fanily.com.tw needs all CSS files to be minified and compressed as it can save up to 207.6 kB or 87% of the original size.
Number of requests can be reduced by 23 (41%)
56
33
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.fanily.tw
375 ms
www.fanily.tw
2080 ms
normalize.css
186 ms
glyphicons.css
371 ms
glyphicons-social.css
556 ms
ungrid.min.css
559 ms
jquery.colorbox.css
564 ms
slick.css
561 ms
slick-theme.css
562 ms
style.css
586 ms
jquery.min.js
69 ms
jquery.colorbox-min.js
737 ms
jquery.lazyload.min.js
742 ms
ZeroClipboard.min.js
745 ms
jquery.textarea_autosize.min.js
749 ms
slick.min.js
748 ms
load.sumome.com
567 ms
adsbytenmax.js
113 ms
analytics.js
101 ms
atrk.js
99 ms
da7f0ac204c52e7dabfdb2939ec588f3007afcf5-92cd4e2272ec6e7c8b1b36d0f664cf25f6b26f4ca07a34d9ce48d26b9f288839.jpg
1336 ms
logo.png
230 ms
fanily-shop.jpg
397 ms
a1fd2858f8fde3d627a10c5e14c541597beefa4c-095d1b3667d5df9864788ffeedb34e6f042881eb5995d67c7b41055c77d928cd.jpg
974 ms
a883717ff4f12908cde415df66a5742f862836fa-1ed624ae80bbd825d452e5988ac7895d55af6fe8c086a1aac1e354771dbacb37.jpg
1236 ms
a759d78de4e8fd754c3e2524d6a77c17c9e6c809-97ec9517ddf03e6baa73f1f7eec8cf6e6ac25c2f14d05ccdf2f39b55c292d963.jpg
874 ms
46c6dacae054bc7b8296d71fe5e5d0d1919abb2c-da08bdab7013e1a4e5208289a62823b7a4ace0cc303ccfb9e6044000f3437836.jpg
1470 ms
4e94b1394a8d827978477ee7ab4332328d3c4c2b-3d64c815c9954033935e8a64e073d1c442cd49dc777d518c910ea940e287a1ff.png
1530 ms
cf87c27e4df59488b4f57fe406ce1671c3d862ca-c884e6ef195efb00044b218eae3e68fdcc911f74471710b0fe0d6970c4edc4c8.png
1650 ms
187ca4a913a31122ae2df53fb1307e5240458ab9-9fbb79a319754db5cc11004a0832d015f2d6a5e3630be188a9ed5af52177f037.png
1436 ms
sdk.js
88 ms
ajax-loader.gif
209 ms
glyphicons-regular.woff
572 ms
iframe_api
172 ms
getVideoList
811 ms
atrk.gif
112 ms
collect
60 ms
b734323b-0532-40a6-8d4e-782e1c96bd3a
1116 ms
rmax-ad
1719 ms
rmax-ad
1733 ms
555 ms
collect
104 ms
101 ms
0e0794c2cad3dfec44801a909729b93599ac1272-9dccac2fadf068cc910ebffed60985d2cfa3e094630ed8772ec53e589628d449.jpg
1225 ms
2c02c8412df7667196063e816bc0e141ce74167c-0aab1acedb05fe9bd526c78839a00f473a4cb91bfb63350786c79fb940c34edb.jpg
1335 ms
efc3dbe5a296d0367df4c0edb5eb03709c4e8a3b-db7fd918cd3c511aac73baafb5febfd46fb4f1edc67eefdc06ee5c81baa92ca5.jpg
1409 ms
6867fd0a023f199f045655de0f308782a52581c1-0b08c2fa873cd49f29bc6bef305901129c6a47f94ce1fe8507fab2568dda8752.png
1435 ms
xd_arbiter.php
80 ms
www-widgetapi.js
54 ms
service.js
42 ms
service.js
59 ms
sme-popup.css
6 ms
css
64 ms
maxresdefault.jpg
158 ms
hqdefault.jpg
178 ms
hqdefault.jpg
216 ms
hqdefault.jpg
217 ms
hqdefault.jpg
212 ms
load
237 ms
status
332 ms
fanily.com.tw accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
fanily.com.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
fanily.com.tw 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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanily.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fanily.com.tw main page’s claimed encoding is . 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.
fanily.com.tw
Open Graph data is detected on the main page of Fanily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: