17.5 sec in total
551 ms
16.7 sec
251 ms
Visit fmyeah.com now to see the best up-to-date Fmyeah content for Taiwan and also check out these interesting facts you probably never knew about fmyeah.com
廣播電台|線上影音|網上商店|Directory|網站目錄|分類目錄|網站導航|網址導航
Visit fmyeah.comWe analyzed Fmyeah.com page load time and found that the first response time was 551 ms and then it took 16.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fmyeah.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.6 s
18/100
25%
Value9.1 s
14/100
10%
Value1,060 ms
25/100
30%
Value0.007
100/100
15%
Value11.8 s
17/100
10%
551 ms
563 ms
1040 ms
779 ms
1032 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 15% of them (23 requests) were addressed to the original Fmyeah.com, 13% (20 requests) were made to Apis.google.com and 11% (17 requests) were made to Bijint.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Douban.com.
Page size can be reduced by 716.7 kB (31%)
2.3 MB
1.6 MB
In fact, the total size of Fmyeah.com main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 58.8 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 58.8 kB or 71% of the original size.
Potential reduce by 64.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. Fmyeah images are well optimized though.
Potential reduce by 489.8 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 489.8 kB or 64% of the original size.
Potential reduce by 103.5 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. Fmyeah.com needs all CSS files to be minified and compressed as it can save up to 103.5 kB or 87% of the original size.
Number of requests can be reduced by 80 (57%)
140
60
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fmyeah. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fmyeah.com
551 ms
www.fmyeah.com
563 ms
radio.css
1040 ms
jwplayer.js
779 ms
highslide.css
1032 ms
highslide-full.js
1435 ms
jquery.min.js
179 ms
time.js
1287 ms
show_ads.js
112 ms
tracking.js
402 ms
addthis_widget.js
479 ms
ga.js
472 ms
bg.jpg
1268 ms
top_bg.png
1270 ms
time.png
1269 ms
facebook-comment.png
983 ms
homelink.gif
1257 ms
search.gif
1266 ms
bgs1.png
1617 ms
bg1.png
1616 ms
ajg.gif
1617 ms
leftmenua.png
1617 ms
leftmenub.png
1617 ms
ca-pub-4355432878324120.js
490 ms
zrt_lookup.html
481 ms
show_ads_impl.js
498 ms
gg.html
592 ms
radiolive.jpg
2220 ms
fmyeah.png
1894 ms
h.js
1269 ms
__utm.gif
27 ms
ads
333 ms
osd.js
23 ms
www.bijint.com
190 ms
ads
300 ms
ads
279 ms
style.css
813 ms
jquery.min.js
62 ms
a7965.js
448 ms
imgLiquid-min.js
399 ms
jquery.mmenu.min.all.js
810 ms
common.js
446 ms
toppage.min.js
446 ms
plusone.js
114 ms
3683471223941894495
53 ms
abg.js
60 ms
m_js_controller.js
88 ms
googlelogo_color_112x36dp.png
118 ms
css
166 ms
css
200 ms
s
45 ms
x_button_blue2.png
47 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
5 ms
favicon
202 ms
nessie_icon_tiamat_white.png
75 ms
favicon
189 ms
PuwvqkdbcqU-fCZ9Ed-b7RsxEYwM7FgeyaSgU71cLG0.woff
465 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
604 ms
hm.gif
568 ms
all.js
660 ms
300lo.json
179 ms
all.js&version=v2.0
1001 ms
widgets.js
303 ms
plusone.js
302 ms
cb=gapi.loaded_0
151 ms
cb=gapi.loaded_1
267 ms
fastbutton
452 ms
page
456 ms
sh.953eb77977227bfd253ee158.html
125 ms
analytics.js
206 ms
img_blank.png
272 ms
ttl_cc.png
271 ms
img_cc.png
1247 ms
sttl_cc.png
267 ms
flow.png
492 ms
sdk.js
748 ms
banner_common.html
481 ms
pc-sd13bd4954f.png
891 ms
background.png
1413 ms
cb=gapi.loaded_0
121 ms
cb=gapi.loaded_1
122 ms
collect
85 ms
postmessageRelay
413 ms
button.71000885400e222c3c0eec823f8f93f0.js
592 ms
rs=AGLTcCPAqmsHN-Miy-Ef6YL7YJb1UaUfpQ
173 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
212 ms
rs=AGLTcCN9CQjjK8cVeyhCZMMQOHZOwNOlKg
397 ms
grlryt2bdKIyfMSOhzd1eA.woff
271 ms
activeview
111 ms
activeview
210 ms
ajs.php
212 ms
463 ms
558 ms
xd_arbiter.php
380 ms
xd_arbiter.php
734 ms
photo.jpg
495 ms
d-QWLnp4didxos_6urzFtg.woff
271 ms
vxNK-E6B13CyehuDCmvQvw.woff
286 ms
cb=gapi.loaded_0
246 ms
cb=gapi.loaded_1
245 ms
fastbutton
15 ms
fastbutton
279 ms
1913.json
329 ms
1077434459-postmessagerelay.js
360 ms
rpc:shindig_random.js
320 ms
rs=AGLTcCN9CQjjK8cVeyhCZMMQOHZOwNOlKg
83 ms
259 ms
postmessageRelay
189 ms
rs=AGLTcCN9CQjjK8cVeyhCZMMQOHZOwNOlKg
136 ms
cb=gapi.loaded_1
119 ms
original.jpg
669 ms
original.jpg
708 ms
original.jpg
970 ms
original.jpg
1007 ms
1913.jpg
1342 ms
cb=gapi.loaded_0
27 ms
tweet_button.fd774b599f565016d763dd860cb31c79.zh-tw.html
25 ms
jot
101 ms
activeview
16 ms
like.php
162 ms
3XaI8mzWBSs.js
524 ms
LVx-xkvaJ0b.png
588 ms
like.php
86 ms
3XaI8mzWBSs.js
224 ms
account
1072 ms
account
2451 ms
hao
376 ms
hao
375 ms
jquery.min.js
443 ms
swfobject.js
441 ms
blank_mask.png
415 ms
rounded-white.png
545 ms
zoomout.cur
570 ms
loader.white.gif
585 ms
xd_arbiter.php
193 ms
like.php
104 ms
like_box.php
182 ms
zhxgx__rVIm.css
80 ms
EWO3D1XXkFA.css
205 ms
SRSW8M763HA.js
634 ms
ldIMPsSoKmy.js
1680 ms
y97Ig99UVTs.js
397 ms
KHAtULXOQuz.js
397 ms
hm.gif
874 ms
12804793_1007328935980466_3626113598169874642_n.jpg
412 ms
307419_240801265966574_1429431652_n.jpg
700 ms
11898529_1637852866494359_6051648852076728763_n.jpg
874 ms
11659237_516179835199742_4101492169589529221_n.jpg
914 ms
559965_453454398067953_691294324_n.jpg
922 ms
11145159_10207789691519614_3884919595123307500_n.jpg
913 ms
10354686_10150004552801856_220367501106153455_n.jpg
913 ms
wL6VQj7Ab77.png
107 ms
1JLnMyDN79z.png
107 ms
VXcANLwwL5J.js
149 ms
i8XO-4kv8i7.js
147 ms
ui
382 ms
like.php
211 ms
fmyeah.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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fmyeah.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fmyeah.com 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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmyeah.com 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 Fmyeah.com main page’s claimed encoding is big5. 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.
fmyeah.com
Open Graph description is not detected on the main page of Fmyeah. 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: