1.2 sec in total
77 ms
1.1 sec
57 ms
Welcome to occlusense.com homepage info - get ready to check Occlu Sense best content right away, or after learning these important things about occlusense.com
THE FUTURE OF OCCLUSION CONTROL. The OccluSense by Bausch combines the traditional and digital occlusion control.
Visit occlusense.comWe analyzed Occlusense.com page load time and found that the first response time was 77 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
occlusense.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value4.5 s
36/100
25%
Value12.1 s
3/100
10%
Value4,810 ms
0/100
30%
Value0.001
100/100
15%
Value18.3 s
3/100
10%
77 ms
31 ms
45 ms
42 ms
269 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Occlusense.com, 40% (19 requests) were made to Static.parastorage.com and 23% (11 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (643 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 746.7 kB (50%)
1.5 MB
754.2 kB
In fact, the total size of Occlusense.com main page is 1.5 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. 45% of websites need less resources to load. HTML takes 888.5 kB which makes up the majority of the site volume.
Potential reduce by 720.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 720.5 kB or 81% of the original size.
Potential reduce by 23.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. Occlu Sense images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 13 (46%)
28
15
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Occlu 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 14 to 1 for JavaScripts and as a result speed up the page load time.
www.occlusense.com
77 ms
originTrials.41d7301a.bundle.min.js
31 ms
minified.js
45 ms
focus-within-polyfill.js
42 ms
polyfill.min.js
269 ms
thunderbolt-commons.eb770ee8.bundle.min.js
82 ms
main.578f27a3.bundle.min.js
81 ms
lodash.min.js
77 ms
react.production.min.js
80 ms
react-dom.production.min.js
80 ms
siteTags.bundle.min.js
80 ms
wix-perf-measure.umd.min.js
82 ms
e86774cc376779beb7aa08e9.js
280 ms
snippet.js
90 ms
OccluSense_Logo_Final_weiss.png
201 ms
21c6bc_303a12cfae184ea4a66e78392efe87ac~mv2.jpg
351 ms
iPad%2BOS.png
493 ms
boc_white.png
471 ms
21c6bc_69245ec79edc4124b73fb1758ea5f2af~mv2.jpg
440 ms
21c6bc_71f81ff4d27e4ca2804f524553eb545b~mv2.jpg
455 ms
21c6bc_5b5ca48ee0ae4196a031cc526b56c5adf000.jpg
453 ms
21c6bc_5b4760b34a9e46969b82feb4a6f9c85e~mv2.jpg
548 ms
nsplsh_3eeb8afbfe4a43228b2ff8282da914cc~mv2.jpg
643 ms
Logo_Claim_2020_WEISS.png
631 ms
bundle.min.js
73 ms
cgaIrkaP9Empe8_PwXbajD8E0i7KZn-EPnyo3HZu7kw.woff
139 ms
dI-qzxlKVQA6TUC5RKSb3z8E0i7KZn-EPnyo3HZu7kw.woff
138 ms
bc176270-17fa-4c78-a343-9fe52824e501.woff
138 ms
07d62b21-8d7a-4c36-be86-d32ab1089972.woff
138 ms
a9e95a29-98a7-404a-90ee-1929ad09c696.woff
148 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
138 ms
file.woff
432 ms
158 ms
149 ms
153 ms
142 ms
145 ms
142 ms
178 ms
176 ms
174 ms
177 ms
176 ms
deprecation-en.v5.html
8 ms
bolt-performance
24 ms
deprecation-style.v5.css
9 ms
right-arrow.svg
10 ms
occlusense.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
occlusense.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
Page has valid source maps
occlusense.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Occlusense.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 Occlusense.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.
occlusense.com
Open Graph data is detected on the main page of Occlu Sense. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: