3 sec in total
45 ms
2.4 sec
603 ms
Welcome to community.htc.com homepage info - get ready to check Community Htc best content for Taiwan right away, or after learning these important things about community.htc.com
這裡有最快最新的官方消息、專屬的好康活動,誠摯邀請你在此與我們盡情的互動!
Visit community.htc.comWe analyzed Community.htc.com page load time and found that the first response time was 45 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
community.htc.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value34.5 s
0/100
25%
Value13.3 s
2/100
10%
Value410 ms
66/100
30%
Value0.459
19/100
15%
Value40.5 s
0/100
10%
45 ms
331 ms
20 ms
38 ms
37 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 76% of them (102 requests) were addressed to the original Community.htc.com, 10% (13 requests) were made to S3.amazonaws.com and 4% (5 requests) were made to Htcsense.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 1.3 MB (22%)
5.8 MB
4.5 MB
In fact, the total size of Community.htc.com main page is 5.8 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. 85% 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 81.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 31.4 kB, which is 33% 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 81.8 kB or 85% of the original size.
Potential reduce by 171.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. Community Htc images are well optimized though.
Potential reduce by 609.4 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 609.4 kB or 69% of the original size.
Potential reduce by 421.2 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. Community.htc.com needs all CSS files to be minified and compressed as it can save up to 421.2 kB or 87% of the original size.
Number of requests can be reduced by 62 (53%)
116
54
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Htc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
tw
45 ms
hero.php
331 ms
modernizr-2.6.3.min.js
20 ms
jquery-1.11.2.min.js
38 ms
device.js
37 ms
jquery.validate.min.js
49 ms
hoverIntent-r7.min.js
51 ms
jquery.placeholder.min.js
59 ms
htc.chrome.all.min.js
57 ms
htc.chrome.ltr.css
54 ms
style_1_common.css
56 ms
bootstrap.css
55 ms
style.css
56 ms
icon-fonts.css
97 ms
clingify.css
98 ms
janrain-share.css
98 ms
jquery-1.10.2.min.js
113 ms
htc_common.js
98 ms
html5shiv.min.js
96 ms
respond.min.js
104 ms
satelliteLib-5d25d1b0bb1d0ba05c6df46eaf8077142a7a4d4d.js
109 ms
responsive.css
98 ms
responsive.php
237 ms
title.css
108 ms
owl.carousel.css
107 ms
owl.transitions.css
105 ms
jquery.bxslider.js
109 ms
owl.carousel.min.js
110 ms
functions.min.js
117 ms
initialise-functions.js
116 ms
jquery.flexslider-min.js
113 ms
modernizr.js
113 ms
jquery.cslider.js
114 ms
index.js
117 ms
jquery.clingify.min.js
116 ms
jquery-migrate-1.2.1.min.js
117 ms
bootstrap.min.js
123 ms
bootstrap-dialog.js
124 ms
htcaccount.js
531 ms
janrain-social.min.js
105 ms
bootstrap-hover-dropdown.min.js
122 ms
back-to-top.js
103 ms
app.js
101 ms
jquery.json.js
88 ms
htcsso.js
87 ms
htcssoaction.js
90 ms
htc_community.js
80 ms
jquery.textareaAutoResize.js
80 ms
janrain_share.js
83 ms
jquery.serialize-object.min.js
82 ms
css
88 ms
mbox-contents-92772e6e78b8ab7a53db7e0a77986c6d160fd114.js
23 ms
satellite-54c15d5a6166620015030900.js
35 ms
s-code-contents-9141f308cbb207913a2dfc8ff0c09b2547a80da0.js
33 ms
target.js
137 ms
standard
9 ms
background.png
30 ms
htc-one-e9-global-2v-listing.png
30 ms
htc-one-m9plus-global-2v-listing.png
31 ms
htc-one-m9-global-2v-listing.png
32 ms
htc-one-e9plus-tw-2v-listing.png
33 ms
163922frhtra4o1nwa4rro.jpg
145 ms
171838u7f6annief11hzcy.jpg
145 ms
095646t2xy6s6g0i50xbxg.jpg
145 ms
140242ot6beotsh3sfh6qz.jpg
89 ms
190557d02c8yyp23eer48x.jpg
143 ms
arrowLeft.png
142 ms
arrowRight.png
147 ms
55f21c0245f81916d12a1fbb390637bf.png
219 ms
b50767f259470975450f808b8ca1f491.jpg
149 ms
e6b46088d30619c9a81827a6c5f33ffc.jpg
148 ms
2ff925a676633c74361e1e0fae568d18.png
152 ms
4901cf228e0d51bac11d4233fe5c1d48.jpg
145 ms
98fc368c52937515b3631f49f66926dd.jpg
150 ms
analytics.js
139 ms
202710l9aaxgibz2z99iir.jpg
412 ms
103751fb0oz3gz1zv9zoo0.jpg
378 ms
main-17e7da0580554f9fcc06.js
80 ms
101645bexnzgbi11xo7dp1.jpg
377 ms
noavatar_small.gif
393 ms
122843xfrb6fgf6l10etrz.jpg
369 ms
172138a8t4zqbq9qo9it1m.jpg
398 ms
162938i5552emkmkgerrzg.jpg
429 ms
connect-fb.png
397 ms
connect-youtube.png
388 ms
htc_community_icon.png
425 ms
htc-logo.png
446 ms
permanent-link-bg.png
442 ms
magnify.png
421 ms
collect
53 ms
hero.php
590 ms
noavatar_small.gif
361 ms
noavatar_small.gif
359 ms
16_avatar_small.jpg
555 ms
globe.png
360 ms
collect
236 ms
noavatar_small.gif
316 ms
satellite-52e978f83f85cf66f0000036.js
22 ms
satellite-52ab88a33f5c710e140000ce.js
85 ms
satellite-52ab88a33f5c710e140000cf.js
915 ms
satellite-52ab88493acfa2d429000141.js
84 ms
satellite-52a7a9d602fa559d37000063.js
103 ms
satellite-52a79721a8554afa16000157.js
105 ms
satellite-54c186873664620015f10a00.js
120 ms
satellite-54b80dfc6335330014200100.js
208 ms
satellite-54b8138233396100174a0000.js
119 ms
22_avatar_small.jpg
416 ms
noavatar_small.gif
296 ms
iframe_api
201 ms
163942ozgel2e7gbki1vk3.jpg
253 ms
remotemethod.html
145 ms
janrain-social.css
32 ms
15_avatar_small.jpg
415 ms
noavatar_small.gif
241 ms
s68874568073078
112 ms
noavatar_small.gif
231 ms
48_avatar_small.jpg
397 ms
noavatar_small.gif
258 ms
79_avatar_small.jpg
443 ms
noavatar_small.gif
338 ms
41 ms
90_avatar_small.jpg
286 ms
29_avatar_small.jpg
337 ms
40_avatar_small.jpg
342 ms
noavatar_small.gif
286 ms
noavatar_small.gif
288 ms
www-widgetapi.js
27 ms
font-common-12b41c8f34dcbb74edbc00fc045dd044.css
48 ms
en_US-24e8a3529cdd4645b0f7299bb856d640.js
85 ms
up.png
284 ms
noavatar_small.gif
275 ms
63 ms
39_avatar_small.jpg
357 ms
collect
24 ms
community.htc.com accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
community.htc.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
community.htc.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.htc.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Chinese. Our system also found out that Community.htc.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.
community.htc.com
Open Graph data is detected on the main page of Community Htc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: