40 sec in total
291 ms
23.8 sec
15.8 sec
Welcome to htc.com homepage info - get ready to check HTC best content for Taiwan right away, or after learning these important things about htc.com
HTC United States
Visit htc.comWe analyzed Htc.com page load time and found that the first response time was 291 ms and then it took 39.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
htc.com performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value12.8 s
0/100
25%
Value7.1 s
31/100
10%
Value1,850 ms
9/100
30%
Value0.157
74/100
15%
Value19.5 s
2/100
10%
291 ms
393 ms
137 ms
124 ms
133 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 62% of them (52 requests) were addressed to the original Htc.com, 7% (6 requests) were made to Google-analytics.com and 5% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Paypalobjects.com.
Page size can be reduced by 3.7 MB (49%)
7.4 MB
3.8 MB
In fact, the total size of Htc.com main page is 7.4 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. 80% 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 82.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 82.5 kB or 82% of the original size.
Potential reduce by 66.6 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. HTC images are well optimized though.
Potential reduce by 1.7 MB
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 1.7 MB or 74% of the original size.
Potential reduce by 1.9 MB
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. Htc.com needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 91% of the original size.
Number of requests can be reduced by 49 (61%)
80
31
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
291 ms
main.css
393 ms
us-custom.css
137 ms
mmcore.js
124 ms
jquery-2.2.2.min.js
133 ms
subscription.min.js
2401 ms
modernizr-custom.js
2402 ms
device.min.js
139 ms
jquery.validate.min.js
139 ms
hoverIntent-r7.min.js
138 ms
jquery.placeholder.min.js
2399 ms
xregexp-all-min.js
2399 ms
velocity-1.2.2.js
2397 ms
velocity-ui-5.0.4.js
2366 ms
bxslider-4.2.5.min.js
2460 ms
watch-2.0.min.js
2365 ms
htc.chrome.all.min.js
2366 ms
all.min.js
2436 ms
us-custom.js
2345 ms
htc.chrome.css
2436 ms
css
2173 ms
39 ms
css
325 ms
htc-u11-red-2v-listing.png
473 ms
htc-u-ultra-blue-global-2v-listing-copy.png
971 ms
accessories-buy.png
511 ms
nav-u11.jpg
510 ms
nav-campus.jpg
592 ms
HTC-U-Ultra-unlocked-nav.png
591 ms
170830-smart-home-logo-hp.svg
507 ms
170830-smart-home-logo-hp-mobile.svg
589 ms
u11-ubox-homepage.jpg
663 ms
u11-ubox-homepage-mobile.jpg
638 ms
htc-u11-global-red-buy-back.png
638 ms
htc-u11-global-red-buy-front.png
636 ms
htc-u-ultra-global-blue-buy-back.png
903 ms
htc-u-ultra-global-blue-buy-front.png
901 ms
htc-bolt-back-buy.png
628 ms
htc-bolt-front-buy.png
902 ms
htc-10-global-carbon-gray-buy-back.png
901 ms
htc-10-global-gray-front-buy.png
901 ms
connect-fb.png
888 ms
connect-twitter.png
877 ms
connect-youtube.png
877 ms
connect-googleplus.png
877 ms
gtm.js
840 ms
htc-logo.png
1674 ms
permanent-link-bg.png
1679 ms
magnify.png
1609 ms
170830-smart-home-hero-hp.jpg
1680 ms
170817-htc-u11-paypal-tile.jpg
1678 ms
20170815-summer-sunset-hp-tile.jpg
1680 ms
20170717-box-3-htc-alexa.jpg
1678 ms
1px.png
387 ms
globe_nbg.png
721 ms
htc-footer-logo.png
514 ms
jquery.bxslider.min.js
1826 ms
merchant.js
2526 ms
analytics.js
1978 ms
conversion_async.js
1179 ms
uwt.js
1178 ms
fbevents.js
933 ms
1808 ms
adsct
803 ms
oct.js
798 ms
1691537031146884
385 ms
linkid.js
286 ms
ec.js
287 ms
2067 ms
2378 ms
collect
1332 ms
collect
1771 ms
js
1395 ms
adsct
1091 ms
1090 ms
adsct
216 ms
215 ms
ga-audiences
813 ms
collect
261 ms
collect
261 ms
ga-audiences
268 ms
htc.jsp
525 ms
adsct
524 ms
adsct
524 ms
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
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
General
Impact
Issue
Detected JavaScript libraries
htc.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Htc.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 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.
htc.com
Open Graph data is detected on the main page of HTC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: