9.8 sec in total
264 ms
9.2 sec
397 ms
Click here to check amazing Good Mydesy content for Taiwan. Otherwise, check out these important facts you probably never knew about good.mydesy.com
自己好之外,其他一切也都要好!
Visit good.mydesy.comWe analyzed Good.mydesy.com page load time and found that the first response time was 264 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
good.mydesy.com performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
264 ms
28 ms
452 ms
62 ms
83 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 18% of them (29 requests) were addressed to the original Good.mydesy.com, 12% (19 requests) were made to Um.simpli.fi and 6% (10 requests) were made to Tags.bluekai.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Extensiondl.maxthon.cn.
Page size can be reduced by 596.9 kB (45%)
1.3 MB
733.1 kB
In fact, the total size of Good.mydesy.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 611.0 kB which makes up the majority of the site volume.
Potential reduce by 67.3 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 14.6 kB, which is 17% 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 67.3 kB or 80% of the original size.
Potential reduce by 12.4 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. Good Mydesy images are well optimized though.
Potential reduce by 348.9 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 348.9 kB or 57% of the original size.
Potential reduce by 168.3 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. Good.mydesy.com needs all CSS files to be minified and compressed as it can save up to 168.3 kB or 85% of the original size.
Number of requests can be reduced by 81 (63%)
129
48
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Good Mydesy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
good.mydesy.com
264 ms
webfont.js
28 ms
style.css
452 ms
jetpack.css
62 ms
custom.css
83 ms
jquery.js
92 ms
jquery-migrate.min.js
2673 ms
q2w3-fixed-widget.min.js
869 ms
show_ads.js
14 ms
adsbygoogle.js
19 ms
api.js
41 ms
style.css
129 ms
custom.js
1175 ms
photon.js
562 ms
devicepx-jetpack.js
66 ms
gprofiles.js
67 ms
wpgroho.js
697 ms
comment-reply.min.js
704 ms
e-201609.js
15 ms
css
24 ms
reset.css
327 ms
prettyPhoto.css
315 ms
wp-emoji-release.min.js
83 ms
2hig-tnMw8lXZsjwuh-9ow.ttf
30 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
40 ms
UyYrYy3ltEffJV9QueSi4UpeNX8RPf6i6WQfJWyCWEs.ttf
69 ms
EkZSE.png
46 ms
matthew.jpg
1062 ms
AngelaLeeTED.jpg
118 ms
SirKenRobinson_1.jpg
138 ms
pinterest@2x.png
72 ms
twitter.png
45 ms
icon_32.png
6193 ms
RwQqA.png
49 ms
TPFba.png
48 ms
L1RRb.png
48 ms
Z6LnZ.png
45 ms
O3IZH.png
46 ms
yFj3pCH.png
63 ms
UxfikD5.png
77 ms
e_light.png
60 ms
fb_light.png
61 ms
g_light.png
633 ms
p_light.png
101 ms
tw_light.png
59 ms
linebg-fade.png
111 ms
75black.png
119 ms
loading.gif
138 ms
small-loading.gif
186 ms
stars-over.png
175 ms
navdiv.png
502 ms
meg-jay-at-ted2013.jpg
1087 ms
4311832482_b2fbf35340_b.jpg
1939 ms
01120.jpg
162 ms
c2.png
497 ms
7513624906_cc7736d603_z.jpg
1770 ms
keepmoving.jpg
137 ms
lizzie_cover.jpg
2329 ms
shaveit.jpg
2963 ms
amycuddy_1.jpg
130 ms
6040581595_8fb740c06b_b.jpg
2015 ms
youngman.jpg
95 ms
bamboo01.jpg
133 ms
return03.jpg
1924 ms
n01022.jpg
1954 ms
jquery-1.7.1.min.js
197 ms
pinterest@2x.png
76 ms
plus.png
482 ms
ca-pub-8996944007164252.js
55 ms
zrt_lookup.html
49 ms
show_ads_impl.js
128 ms
530 ms
small.js
155 ms
ads
271 ms
quotes.png
220 ms
osd.js
22 ms
recaptcha__en.js
218 ms
21 ms
ads
353 ms
ga.js
118 ms
hovercard.css
45 ms
services.css
77 ms
sprites.png
419 ms
dpx.js
27 ms
g.gif
27 ms
ads
381 ms
tpid=1EE70445ADD9D5562203B03502C8F03F
72 ms
__utm.gif
51 ms
p
49 ms
dpx
3 ms
match_redirect
17 ms
5210597567917189449
36 ms
abg.js
39 ms
m_js_controller.js
51 ms
googlelogo_color_112x36dp.png
21 ms
29931
20 ms
s
30 ms
x_button_blue2.png
31 ms
match_redirect
29 ms
74 ms
tpid=DA29559EAED9D5561071CBA802B05A87
38 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
26 ms
15689440579604086310
24 ms
lr
50 ms
tc.js
88 ms
favicon
60 ms
nessie_icon_tiamat_white.png
41 ms
lr.gif
32 ms
p
69 ms
match_redirect
37 ms
sync
7 ms
match_redirect
3 ms
DA29559EAED9D5561071CBA802B05A87
37 ms
match_redirect
4 ms
ProfilesEngineServlet
12 ms
v2
53 ms
ProfilesEngineServlet
88 ms
dpx
4 ms
27519
35 ms
pixel
41 ms
getuid
27 ms
generic
14 ms
i.match
184 ms
xrefid.xgi
9 ms
generic
7 ms
2964
19 ms
5386
48 ms
tap.php
12 ms
1407
146 ms
2831
23 ms
2981
56 ms
4448
15 ms
getuid
13 ms
event
6 ms
4470
17 ms
i.match
104 ms
exelate
3 ms
match_redirect
3 ms
4229
16 ms
engine
94 ms
33 ms
27 ms
18 ms
spotx_match
3 ms
fb_match
3 ms
u.php
26 ms
an
3 ms
lj_match
3 ms
cw_match
4 ms
rtset
24 ms
rb_match
3 ms
tap.php
231 ms
ox_match
4 ms
sd
8 ms
pm_match
6 ms
Pug
49 ms
pixel
85 ms
merge
38 ms
aa_px
3 ms
g_match
4 ms
match_redirect
4 ms
pixel
3851 ms
activeview
15 ms
good.mydesy.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
good.mydesy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
good.mydesy.com SEO score
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Good.mydesy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Good.mydesy.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.
good.mydesy.com
Open Graph data is detected on the main page of Good Mydesy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: