7.4 sec in total
1.5 sec
5.7 sec
225 ms
Click here to check amazing Digital Nmh content for Taiwan. Otherwise, check out these important facts you probably never knew about digital.nmh.gov.tw
49 Nan Hai Road, Taipei City 100, Taiwan, 2361-0270
Visit digital.nmh.gov.twWe analyzed Digital.nmh.gov.tw page load time and found that the first response time was 1.5 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
digital.nmh.gov.tw performance score
1485 ms
462 ms
714 ms
29 ms
880 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Digital.nmh.gov.tw, 47% (43 requests) were made to Nmh.gov.tw and 18% (17 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Nmh.gov.tw.
Page size can be reduced by 1.1 MB (53%)
2.1 MB
994.1 kB
In fact, the total size of Digital.nmh.gov.tw main page is 2.1 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. 60% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 4.1 kB, which is 14% 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 17.8 kB or 58% of the original size.
Potential reduce by 223.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, Digital Nmh needs image optimization as it can save up to 223.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 711.5 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 711.5 kB or 71% of the original size.
Potential reduce by 150.4 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. Digital.nmh.gov.tw needs all CSS files to be minified and compressed as it can save up to 150.4 kB or 89% of the original size.
Number of requests can be reduced by 32 (38%)
85
53
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Digital Nmh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
digital.nmh.gov.tw
1485 ms
www.nmh.gov.tw
462 ms
index.htm
714 ms
jquery.min.js
29 ms
web.css
880 ms
gsearch.css
451 ms
index.htm
654 ms
jquery-ui.min.js
53 ms
jquery-ui.css
51 ms
jquery.easing.1.3.htm
473 ms
jquery.print.htm
464 ms
content.htm
658 ms
fontsize.htm
659 ms
sub.htm
690 ms
html2canvas.htm
1178 ms
pagination.css
893 ms
jquery.pagination.htm
898 ms
WebResource.axd
664 ms
ScriptResource.axd
921 ms
ScriptResource.axd
679 ms
jquery-ui.js
7 ms
yh_reset.css
212 ms
sub.css
262 ms
unlock.png
243 ms
logo.png
651 ms
menu02.png
238 ms
menu03.png
241 ms
menu04.png
238 ms
menu05.png
379 ms
menu01.png
459 ms
a48cb719-bb1f-4f60-bd31-4d9761368c96_1280_573.jpg
1518 ms
rss.jpg
470 ms
fb.jpg
473 ms
youtube.jpg
594 ms
iii.jpg
665 ms
righticon1.png
691 ms
righticon2.png
702 ms
righticon3.png
811 ms
top.png
679 ms
purple.png
690 ms
black80.png
726 ms
search.png
739 ms
enter.jpg
850 ms
purple2.png
908 ms
embed
1234 ms
left2.png
876 ms
right2.png
912 ms
analytics.js
34 ms
circle.png
918 ms
black2.png
1013 ms
collect
13 ms
js
83 ms
init_embed.js
67 ms
common.js
63 ms
map.js
63 ms
google4.png
95 ms
overlay.js
15 ms
util.js
88 ms
onion.js
86 ms
search_impl.js
85 ms
stats.js
40 ms
openhand_8_8.cur
70 ms
ViewportInfoService.GetViewportInfo
66 ms
ViewportInfoService.GetViewportInfo
59 ms
kh
135 ms
kh
193 ms
transparent.png
63 ms
controls.js
74 ms
vt
119 ms
vt
342 ms
vt
189 ms
vt
183 ms
vt
194 ms
vt
190 ms
vt
194 ms
vt
268 ms
vt
272 ms
vt
265 ms
vt
308 ms
vt
291 ms
vt
343 ms
vt
340 ms
vt
392 ms
vt
379 ms
css
98 ms
entity11.png
57 ms
mapcnt6.png
54 ms
tmapctrl.png
48 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
55 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
72 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
85 ms
digital.nmh.gov.tw SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digital.nmh.gov.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 Digital.nmh.gov.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.
digital.nmh.gov.tw
Open Graph description is not detected on the main page of Digital Nmh. 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: