Tools & Wizards About Us
htcsense.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

htcsense.com

Welcome to HTC

Page Load Speed

2.6 sec in total

First Response

19 ms

Resources Loaded

2.2 sec

Page Rendered

386 ms

htcsense.com screenshot

About Website

Welcome to htcsense.com homepage info - get ready to check HTC Sense best content for United States right away, or after learning these important things about htcsense.com

One HTC account for your phone and VR world. Sign in HTC account to manage personal info, security option and privacy preference.

Visit htcsense.com

Key Findings

We analyzed Htcsense.com page load time and found that the first response time was 19 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

htcsense.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value2,830 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

19 ms

styles.css

20 ms

jquery-3.6.3.min.js

18 ms

jquery-migrate-3.4.0.min.js

53 ms

css2

58 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Htcsense.com, 17% (8 requests) were made to Youtube.com and 11% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (331 ms) relates to the external source Htc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.5 kB (17%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Htcsense.com main page is 2.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. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 50.0 kB

  • Original 59.1 kB
  • After minification 43.0 kB
  • After compression 9.1 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 16.1 kB, which is 27% 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 50.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.8 MB
  • After minification 1.8 MB

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 Sense images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 435.5 kB

  • Original 841.1 kB
  • After minification 840.9 kB
  • After compression 405.6 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 435.5 kB or 52% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 119.1 kB
  • After minification 119.1 kB
  • After compression 119.1 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. Htcsense.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (39%)

Requests Now

38

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HTC Sense. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

19 ms

styles.css

styles.css

20 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

18 ms

jquery-migrate-3.4.0.min.js

jquery-migrate-3.4.0.min.js

53 ms

css2

css2

58 ms

player_api

player_api

63 ms

purl.js

purl.js

55 ms

vendor_1.js

vendor_1.js

56 ms

vendor_2.js

vendor_2.js

56 ms

vendor_3.js

vendor_3.js

63 ms

app.js

app.js

61 ms

195 ms

gtm.js

gtm.js

312 ms

htc-logo.svg

htc-logo.svg

262 ms

5g.svg

5g.svg

329 ms

exodus.svg

exodus.svg

266 ms

vive.svg

vive.svg

297 ms

vive-logo-short.svg

vive-logo-short.svg

253 ms

vive-xr-elite-1920.jpg

vive-xr-elite-1920.jpg

298 ms

vive-sub-banner.jpg

vive-sub-banner.jpg

262 ms

vip-sub-banner.png

vip-sub-banner.png

295 ms

vive-business-sub-banner.jpg

vive-business-sub-banner.jpg

274 ms

desktop.jpg

desktop.jpg

331 ms

www-widgetapi.js

www-widgetapi.js

213 ms

138 ms

120 ms

htc-logo-w.svg

htc-logo-w.svg

308 ms

vive-logo-short-white.svg

vive-logo-short-white.svg

110 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

24 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

40 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf

41 ms

fontello.woff

fontello.woff

79 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

257 ms

icomoon.ttf

icomoon.ttf

77 ms

htc-accessory-desktop.jpg

htc-accessory-desktop.jpg

34 ms

product-listing-v2-desktop.jpg

product-listing-v2-desktop.jpg

95 ms

SGeNk9FiJMI

SGeNk9FiJMI

65 ms

PHdhNnkdJws

PHdhNnkdJws

96 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

35 ms

base.js

base.js

79 ms

ad_status.js

ad_status.js

303 ms

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js

229 ms

embed.js

embed.js

120 ms

id

id

49 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

52 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

54 ms

Accessibility Review

htcsense.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

htcsense.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

htcsense.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Htcsense.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 Htcsense.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.

Social Sharing Optimization

htcsense.com

Open Graph data is detected on the main page of HTC Sense. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: