3.9 sec in total
835 ms
2.3 sec
799 ms
Click here to check amazing Holo Lens content for China. Otherwise, check out these important facts you probably never knew about hololens.com
Introducing HoloLens 2, an untethered mixed reality headset that's designed to help you solve real business problems today using intelligent apps and solutions.
Visit hololens.comWe analyzed Hololens.com page load time and found that the first response time was 835 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
hololens.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value11.7 s
0/100
25%
Value5.0 s
62/100
10%
Value1,060 ms
25/100
30%
Value0.346
32/100
15%
Value16.0 s
6/100
10%
835 ms
21 ms
41 ms
38 ms
61 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hololens.com, 44% (52 requests) were made to Microsoft.com and 8% (9 requests) were made to C.s-microsoft.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn-dynmedia-1.microsoft.com.
Page size can be reduced by 314.2 kB (35%)
897.2 kB
583.0 kB
In fact, the total size of Hololens.com main page is 897.2 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. 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. Javascripts take 472.0 kB which makes up the majority of the site volume.
Potential reduce by 189.9 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 189.9 kB or 87% of the original size.
Potential reduce by 61.5 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, Holo Lens needs image optimization as it can save up to 61.5 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 62.8 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 62.8 kB or 13% of the original size.
Potential reduce by 14 B
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. Hololens.com has all CSS files already compressed.
Number of requests can be reduced by 49 (46%)
106
57
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holo Lens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
835 ms
main-light.min.ACSHASH561c834597fb9bc5aac4021e21e006be.css
21 ms
main-light.min.ACSHASH4a3498116ccd44ff7f0f811f7ba4ef60.css
41 ms
clientlib-onecloud-util.min.ACSHASHeaf79b9fdbdd0d1a36875835364c1d1b.js
38 ms
clientlib-base.min.ACSHASH69fcbf8d5beaac9b4a74170aad04b54a.css
61 ms
clientlib-events.min.ACSHASH7677f65c1626ab1bde509437776d4291.js
38 ms
clientlib-uhf.min.ACSHASHf9f2395c582fa601707b7a5dfae9f05f.css
38 ms
clientlib-polyfills.min.ACSHASHf381d5147c85ee687ea8fbef32c83d37.js
39 ms
clientlib-jquery.min.ACSHASH35986a813756f39ab6b922979ffedb03.js
84 ms
clientlib-jquery-cookie.min.ACSHASH20aafdf6904d3dc5db0e0e33abbfc1a4.js
83 ms
v1.min.ACSHASH4cffc2c9b55f8bde649e0d2535a1eebd.js
82 ms
v1.min.ACSHASHbe3f2a9f6a41fc40556efe260fc861a5.js
83 ms
msochead.css
83 ms
msochead.js
83 ms
v4.js
39 ms
v1.min.ACSHASHd7106db242c2b41f88a1b02418bec7e2.js
117 ms
site.min.ACSHASHa8a3710424dc6e0dff393c6964441bdb.css
106 ms
ca-ae3ce4
110 ms
site.min.ACSHASH1dabd5cc3f7b68c178b59ea74dc62947.js
139 ms
site.min.ACSHASH96ddea96f43b844ad97950d109c49366.css
104 ms
site.min.ACSHASH866c3a4ac33e41fa69b45e73bba381b8.css
104 ms
clientlib-product-pricing.min.ACSHASH4ab0eedab0ba9025faa176c16f80b8b4.js
115 ms
clientlib-product-pricing.min.ACSHASH2add065651afb45e8c80967dd7b86a41.css
138 ms
site.min.ACSHASH2779a1f7171beec22e383ef464e8a205.js
138 ms
clientlibs.min.ACSHASH4402231c6c651d105bb28a0781aa644e.css
163 ms
site.min.ACSHASH348b07e6e2c5729e9e932ba2765bdf43.js
163 ms
site.min.ACSHASHf51f0d5bcfe05f53a3624fa78b778f92.js
161 ms
ump.mjs
343 ms
site.min.ACSHASH131d95cf2ec0e511b73b264fa0c84059.css
162 ms
site.min.ACSHASHf3ce0716faf38b81e39f92e91d6f05dc.js
162 ms
wcp-consent.js
99 ms
2b-8e0ae6
241 ms
publisher.min.ACSHASHa24ceb8fa2848efd5974571d2ea918a1.js
339 ms
main-light.min.ACSHASH1315b52070fe169b25b7b0a6e3667170.js
341 ms
main-light.min.ACSHASHf2a1b7d80bcd06e3837cfd75470b4f9b.js
341 ms
clientlib-base.min.ACSHASH8a825c513af4b75b682515af94d92d62.js
339 ms
isv-redirect.min.ACSHASH832c4ecfe1459d803f5f773f723e6a68.js
338 ms
clientlib-site.min.ACSHASH87b8f0e23485bbb3b4ecade3d42aed38.js
341 ms
clientlib-contact-sales.min.ACSHASH4a1a21c1176e98acf994a206329519ba.css
512 ms
clientlib-chat.min.ACSHASHfa6f56b2d3037982772378233706c9af.css
361 ms
clientlib-click-group-telemetry.min.ACSHASHf25fec6821f63d701a6b6291a4011894.js
357 ms
clientlib-httpclient.min.ACSHASH5ee9e4e4e0a5fd39092e63d2d102b12b.js
356 ms
clientlib-cookieconsent.min.ACSHASH96f0c5b1219e39b8788028f5c17a5ad9.js
357 ms
clientlib-cookievalidator.min.ACSHASH3db5cf9fd3fab92b3889302c8de78d1b.js
479 ms
featurecontrol.min.ACSHASHc22ea5b46f3fcad90da0abcc0a3f73d4.js
443 ms
custom-oneds.min.ACSHASHa4621d4de3464466d03df6bcf2b32a57.js
463 ms
msocbody.js
436 ms
clientlib-contact-sales.min.ACSHASH4bb59388a4ff931ab2da144672d66cc9.js
463 ms
clientlib-chat.min.ACSHASHcec9b9ad957dfa692d66f6f8cd3d53e3.js
553 ms
clientlib-market-layer.min.ACSHASH551a5d1b5ebf715e3f78c311a57fa1d7.js
559 ms
clientlib-greenid.min.ACSHASH383b23d12df0d9265d7569a7102c2f96.js
559 ms
ie11-polyfills.js
538 ms
RE1Mu3b
215 ms
airbus-140x75_RWGH7T
258 ms
astellas-140x75_RWGxo1
385 ms
audi-140x75_RWHbvG
501 ms
bhp-140x75_RWGuXf
507 ms
CAE-white-140x75_RWGuXj
508 ms
Untitled-XboxWirelessController_RWGH7Y
504 ms
Untitled-Surface-Pen_RWGuXx
585 ms
catapult-140x75_RWGxob
583 ms
cleanenergy-140x75_RWGELm
579 ms
ecolab-140x75_RWGs4r
511 ms
faurecia-140x75_RWGuXB
624 ms
friesland-140x75_RWGpyg
579 ms
gaumard-140x75_RWGpyl
580 ms
genesis-140x75_RWGpyp
582 ms
goodyear-140x75_RWGuXO
583 ms
ivirma-140x75_RWGELs
581 ms
Untitled-Surface-Pro-Signature-Type-Cover_RWGxov
625 ms
jrcs-140x75_RWGELv
585 ms
kautex-140x75_RWGELx
585 ms
kruger-140x75_RWGpzo
584 ms
kuchen-140x75_RWGxpv
624 ms
lockneed-martin-140x75_RWGpzr
625 ms
loreal-140x75_RWGxpB
626 ms
lyondell-140x75_RWGxpE
626 ms
MDA-140x75_RWGxpH
631 ms
mediview-white-140x75_RWGxpQ
947 ms
medlab-white-140x75_RWGxpT
1040 ms
mercedez-benz-140x75_RWGsnW
642 ms
microsoft-140x75_RWGso5
660 ms
mitsubushi-140x75_RWGsnZ
1001 ms
Mount_Sinai_hospital_140x75_RWGso2
679 ms
musashi-140x75_RWGCfF
684 ms
ML-140x75_RWGHeC
769 ms
MicrosoftTeams-image_60_RWGHeF
704 ms
natuzzi-140x75_RWGxpy
741 ms
Alder-Hey-Childrens-NHS-white-140x75_RWGuXa
1077 ms
latest.woff
273 ms
latest.woff
366 ms
latest.woff
394 ms
latest.woff
395 ms
latest.woff
397 ms
latest.woff
396 ms
latest.woff
395 ms
latest.woff
396 ms
latest.woff
394 ms
mwfmdl2-v3.54.woff
299 ms
MWFFluentIcons.woff
295 ms
NHS-imperial-college-healthcare-white-140x75_RWGHeI
545 ms
nox-140x75_RWGCfI
844 ms
parco-140x75_RWGHeM
326 ms
quaker-140x75_RWGHeP
459 ms
renault-140x75_RWGCfL
459 ms
saint-gobain-140x75_RWGHeT
564 ms
salvatove-140x75_RWGHeW
397 ms
suntory-140x75_RWGHeZ
420 ms
tetrapak-140x75_RWGHf2
642 ms
tokyo-140x75_RWGHf5
497 ms
toyota-140x75_RWGCfR
593 ms
walsgreen-140x75_RWGHf8
613 ms
weidmuller-140x75_RWGCfV
512 ms
zf-140x75_RWGHfb
515 ms
twitter-gray
517 ms
facebook-gray
523 ms
youtube-gray
523 ms
linkedin-gray
494 ms
hololens.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
hololens.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hololens.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hololens.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 Hololens.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.
hololens.com
Open Graph data is detected on the main page of Holo Lens. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: