6.5 sec in total
652 ms
5.3 sec
608 ms
Visit microduo.tw now to see the best up-to-date Microduo content for Taiwan and also check out these interesting facts you probably never knew about microduo.tw
手機及電腦軟硬體討論為主,兼具人文與娛樂,量多質精的3C綜合資源論壇。
Visit microduo.twWe analyzed Microduo.tw page load time and found that the first response time was 652 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
microduo.tw performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value7.1 s
5/100
25%
Value12.6 s
3/100
10%
Value2,710 ms
3/100
30%
Value0.126
82/100
15%
Value15.3 s
7/100
10%
652 ms
1123 ms
629 ms
422 ms
417 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 36% of them (37 requests) were addressed to the original Microduo.tw, 7% (7 requests) were made to Static.doublemax.net and 7% (7 requests) were made to Ad.sitemaji.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Adplace.adsame.com.
Page size can be reduced by 337.6 kB (42%)
801.6 kB
464.0 kB
In fact, the total size of Microduo.tw main page is 801.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 345.8 kB which makes up the majority of the site volume.
Potential reduce by 108.5 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 108.5 kB or 82% of the original size.
Potential reduce by 53.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. Obviously, Microduo needs image optimization as it can save up to 53.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 108.0 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 108.0 kB or 46% of the original size.
Potential reduce by 68.0 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. Microduo.tw needs all CSS files to be minified and compressed as it can save up to 68.0 kB or 77% of the original size.
Number of requests can be reduced by 51 (53%)
97
46
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Microduo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
microduo.tw
652 ms
www.microduo.tw
1123 ms
style_163_common.css
629 ms
style_163_forum_index.css
422 ms
style.css
417 ms
common.js
1347 ms
style_163_widthauto.css
419 ms
forum.js
609 ms
style.css
624 ms
pace.min.js
637 ms
logging.js
637 ms
md5.js
816 ms
adsbygoogle.js
6 ms
tr.js
198 ms
s
2280 ms
d2s_unify.js
456 ms
microduo.js
454 ms
XBvjARUQau.png
1341 ms
bd_bg.png
209 ms
logo2015.png
633 ms
fblogin.gif
423 ms
glogin.gif
210 ms
collapsed_no.gif
217 ms
forum_new11.png
210 ms
online_admin.gif
415 ms
online_supermod.gif
417 ms
online_mod.gif
417 ms
online_member.gif
422 ms
switch_width.png
617 ms
px.png
608 ms
pn.png
608 ms
nv.png
609 ms
qmenu.png
609 ms
nv_a.png
805 ms
search.png
807 ms
pt_item.png
805 ms
ca-pub-0130920398030382.js
65 ms
zrt_lookup.html
62 ms
show_ads_impl.js
66 ms
thead.png
794 ms
dot.gif
795 ms
chart.png
793 ms
titlebg.png
989 ms
a.htm
317 ms
ads
288 ms
osd.js
17 ms
ads
275 ms
cmt.htm
8 ms
ta.js
339 ms
cm.htm
309 ms
15472523428211190397
79 ms
abg.js
86 ms
m_js_controller.js
100 ms
googlelogo_color_112x36dp.png
57 ms
s
44 ms
x_button_blue2.png
44 ms
favicon
87 ms
nessie_icon_tiamat_white.png
44 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
4 ms
trans_domain.jsp
271 ms
9d6c916ef31cd2d1df3eff7e416d2913.jpg
19 ms
cf.png
6 ms
cmpixel.htm
152 ms
a.htm
156 ms
count_red.png
211 ms
ol_bg.png
214 ms
ads
256 ms
d2s5.css
15 ms
d2s_init.js
452 ms
d2s_adlabel.png
5 ms
a.htm
236 ms
ads
305 ms
syndication.js
42 ms
TaNsX3NcqimadIVgHm22CQ.js
19 ms
scrolltop.png
225 ms
feedback-tab.png
13 ms
ckip.php
409 ms
tab-horizontal-dark-3efc2033e3bb06b1eefaa3431d3d47d8.png
4 ms
trans_domain.jsp
153 ms
b3cce57eabbd8dbab2ce07cf957e51a2.jpg
10 ms
favicon
67 ms
cmpixel.htm
160 ms
trans_domain.jsp
153 ms
getCookie.js
418 ms
getCode.php
419 ms
favicon
43 ms
118 ms
193 ms
205 ms
microduo.css
451 ms
resizeads.js
7 ms
activeview
15 ms
rta.js
19 ms
getCode.php
205 ms
a.htm
153 ms
trans_domain.jsp
151 ms
d7e72c4ab9962c43806097dc459dfd37.jpg
10 ms
base.css
4 ms
p
44 ms
p
62 ms
p
81 ms
cmpixel.htm
151 ms
microduo.tw 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
microduo.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
microduo.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Tap targets are not sized appropriately
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Microduo.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Microduo.tw 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.
microduo.tw
Open Graph description is not detected on the main page of Microduo. 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: