10.6 sec in total
681 ms
9.3 sec
660 ms
Visit ein2.funmily.com now to see the best up-to-date Ein 2 Funmily content for Taiwan and also check out these interesting facts you probably never knew about ein2.funmily.com
Funmily 歡樂派 官方網站,全新遊戲會員平台只需一個 Funmily 會員帳號,即可暢遊 Funmily 旗下各個地區的網上遊戲及使用各種會員服務,無需額外申請遊戲帳號,簡單方便。此外,Funmily 提供多種線上購點服務,會員可於網站直接購點及儲值。
Visit ein2.funmily.comWe analyzed Ein2.funmily.com page load time and found that the first response time was 681 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ein2.funmily.com performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value16.0 s
0/100
25%
Value10.2 s
8/100
10%
Value350 ms
73/100
30%
Value0.315
37/100
15%
Value12.0 s
16/100
10%
681 ms
1246 ms
887 ms
907 ms
452 ms
Our browser made a total of 153 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ein2.funmily.com, 59% (91 requests) were made to Image.funmily.com and 16% (25 requests) were made to Static.funmily.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Image.funmily.com.
Page size can be reduced by 508.1 kB (9%)
5.6 MB
5.1 MB
In fact, the total size of Ein2.funmily.com main page is 5.6 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 107.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. 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 107.9 kB or 86% of the original size.
Potential reduce by 135.8 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. Ein 2 Funmily images are well optimized though.
Potential reduce by 155.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 155.7 kB or 64% of the original size.
Potential reduce by 108.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. Ein2.funmily.com needs all CSS files to be minified and compressed as it can save up to 108.7 kB or 84% of the original size.
Number of requests can be reduced by 47 (32%)
147
100
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ein 2 Funmily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ein2.funmily.com
681 ms
www.funmily.com
1246 ms
reset.min.css
887 ms
uniform.default.css
907 ms
font-awesome.min.css
452 ms
master.css
1138 ms
sea.js
939 ms
master.js
940 ms
plugin-shim.js
304 ms
1.9.1.min.js
431 ms
analytics.js
33 ms
bg.jpg
1453 ms
Validcode
726 ms
favicon.ico
302 ms
logo.png
1448 ms
20160202100349665.png
1489 ms
20160217095117934.png
1494 ms
20160118111915457.png
1529 ms
201505181228264498.png
1533 ms
201510150947573145.png
1530 ms
20151210101035344.png
1691 ms
20150924095536356.png
1735 ms
201412011820045418.png
1737 ms
20150910103546448.png
1780 ms
20140703124056169.png
1783 ms
20151102181643205.png
1787 ms
20150518124332614.png
1933 ms
20160318155355257.png
1030 ms
20151106143412806.png
1980 ms
20160112104903950.png
1982 ms
201510011743406644.png
2031 ms
20151224113552762.png
2035 ms
20150722154822713.png
2043 ms
20160311113223697.png
2173 ms
20150324143220246.png
1029 ms
201504081450564109.jpg
2720 ms
20140814145908567.png
2226 ms
20151012124342533.png
2283 ms
20160104111523608.png
2286 ms
20160223151133668.jpg
3840 ms
20160127141251620.jpg
4113 ms
20151113155617859.jpg
3996 ms
20150904094622561.jpg
4308 ms
20160224121158803.jpg
4317 ms
20160316100211221.jpg
4203 ms
20160223142557570.jpg
4096 ms
20151125101829147.jpg
4235 ms
20160120141851462.jpg
4611 ms
20160217095134942.jpg
4355 ms
fbevents.js
95 ms
gtm.js
92 ms
like.php
277 ms
bg-input.png
290 ms
like.php
241 ms
collect
65 ms
b60.png
958 ms
fontawesome-webfont.woff
679 ms
8i5wLKr4CIi.js
325 ms
73 ms
LVx-xkvaJ0b.png
362 ms
TY3MhkXpWJ-.js
571 ms
atrk.js
71 ms
collect
36 ms
collect
17 ms
collect
21 ms
collect
17 ms
collect
18 ms
collect
18 ms
collect
101 ms
34 ms
45 ms
75 ms
83 ms
97 ms
95 ms
96 ms
collect
83 ms
atrk.gif
78 ms
test.png
55 ms
index.js
235 ms
2.1.2.js
216 ms
placeholder.ie.js
222 ms
tabs.fade.clip.slide.1.10.4.js
461 ms
ga-audiences
41 ms
ga-audiences
32 ms
ga-audiences
36 ms
libary.js
352 ms
slides.min.jquery.js
213 ms
greybox.css
219 ms
3.2.js
203 ms
3.2.css
404 ms
page.js
444 ms
float-banner.js
444 ms
greybox.js
233 ms
enter.js
232 ms
20160128184744165.jpg
3427 ms
201511121549532766.jpg
3430 ms
show.js
215 ms
aside.js
220 ms
201505181230576615.jpg
3125 ms
2015061218053655.jpg
3132 ms
20160311113240557.jpg
3120 ms
20160125162628725.jpg
3217 ms
201510091057242824.jpg
3211 ms
201412011820043004.jpg
3295 ms
201410281504314327.jpg
3301 ms
20160113095416644.jpg
3161 ms
20151210101057102.jpg
3143 ms
logo.png
1041 ms
logo.png
734 ms
logo.png
736 ms
logo.png
1249 ms
logo.png
978 ms
logo.png
1004 ms
logo.png
1267 ms
logo.png
975 ms
logo.png
1262 ms
logo.png
1357 ms
logo.png
1563 ms
logo.png
1267 ms
logo.png
1247 ms
logo.png
1204 ms
logo.png
1042 ms
logo.png
1616 ms
logo.png
1260 ms
logo.png
1210 ms
20150318145828250.png
2288 ms
20140821142357664.jpg
1997 ms
2014020510092119.jpg
2065 ms
20140625105003727.jpg
2049 ms
20140625105922322.jpg
783 ms
20140625105354790.jpg
1792 ms
logo.png
675 ms
logo.png
993 ms
20141223170433953.jpg
1635 ms
20140512122213830.jpg
1693 ms
20140625105242309.jpg
1771 ms
funmily.png
1600 ms
bg.png
1491 ms
funmily.png
1406 ms
bg.png
1458 ms
title.png
1472 ms
submit.png
1552 ms
submit-title.png
1500 ms
social-l.png
1492 ms
title.png
1529 ms
title.png
1561 ms
bg.png
1514 ms
title.png
1583 ms
btn.png
1524 ms
2.png
1525 ms
3.png
1546 ms
sprite.png
462 ms
ein2.funmily.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ein2.funmily.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
ein2.funmily.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ein2.funmily.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Ein2.funmily.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.
ein2.funmily.com
Open Graph data is detected on the main page of Ein 2 Funmily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: