2.5 sec in total
176 ms
2 sec
308 ms
Welcome to oculus.com homepage info - get ready to check Oculus best content for United States right away, or after learning these important things about oculus.com
Oculus wants to make it possible to experience anything, anywhere, through the power of virtual reality. The Oculus Rift will be released in Q1 2016.
Visit oculus.comWe analyzed Oculus.com page load time and found that the first response time was 176 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
oculus.com performance score
name
value
score
weighting
Value8.6 s
0/100
10%
Value13.3 s
0/100
25%
Value8.6 s
17/100
10%
Value0 ms
100/100
30%
Value0.184
66/100
15%
Value8.6 s
37/100
10%
176 ms
298 ms
151 ms
204 ms
226 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Oculus.com, 56% (20 requests) were made to Static.oculus.com and 8% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (298 ms) belongs to the original domain Oculus.com.
Page size can be reduced by 568.1 kB (46%)
1.2 MB
668.8 kB
In fact, the total size of Oculus.com main page is 1.2 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. 35% of websites need less resources to load. Images take 483.0 kB which makes up the majority of the site volume.
Potential reduce by 19.6 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 19.6 kB or 78% of the original size.
Potential reduce by 15.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. Oculus images are well optimized though.
Potential reduce by 273.2 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 273.2 kB or 64% of the original size.
Potential reduce by 259.7 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. Oculus.com needs all CSS files to be minified and compressed as it can save up to 259.7 kB or 87% of the original size.
Number of requests can be reduced by 8 (33%)
24
16
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oculus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
oculus.com
176 ms
www.oculus.com
298 ms
151 ms
204 ms
jquery-1.11.2.min.js
226 ms
www-head.min.js
27 ms
fbevents.js
220 ms
ga.js
66 ms
a.js;m=11002203359465;cache=0.9384965500794351
112 ms
4731330629.js
162 ms
__utm.gif
37 ms
collect
106 ms
tr
104 ms
a.html;m=11002203359465;noscript=1
26 ms
baxter.min.css
84 ms
oval.min.css
209 ms
www.min.css
224 ms
oval.min.js
265 ms
174 ms
96_sprite.png
45 ms
gear-vr-home.jpg
71 ms
eve-valkyrie.jpg
90 ms
luckys-tale.jpg
148 ms
dragon-front.jpg
86 ms
24_sprite.png
87 ms
spinner-128x128-black.png
134 ms
sdk.js
126 ms
www.min.js
220 ms
oculussans-semibold-webfont.woff
86 ms
oculussans-black-webfont.woff
104 ms
oculussans-regular-webfont.woff
95 ms
oculussans-regularitalic-webfont.woff
114 ms
oculussans-semibolditalic-webfont.woff
121 ms
oculussans-blackitalic-webfont.woff
155 ms
107 ms
xd_arbiter.php
259 ms
oculus.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oculus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
oculus.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
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
N/A
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oculus.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 English. Our system also found out that Oculus.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
oculus.com
Open Graph description is not detected on the main page of Oculus. 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: