Tools & Wizards About Us
oculavis.de screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

oculavis.de

oculavis – smart service and connected worker solutions

Page Load Speed

3.8 sec in total

First Response

308 ms

Resources Loaded

2.9 sec

Page Rendered

683 ms

oculavis.de screenshot

About Website

Welcome to oculavis.de homepage info - get ready to check Oculavis best content right away, or after learning these important things about oculavis.de

Reach technicians and end users of machinery and equipment worldwide faster with smart service and connected worker solutions from oculavis.

Visit oculavis.de

Key Findings

We analyzed Oculavis.de page load time and found that the first response time was 308 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

oculavis.de performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

oculavis.de

308 ms

394 ms

style.min.css

300 ms

theme.min.css

301 ms

header-footer.min.css

304 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that all of those requests were addressed to Oculavis.de and no external sources were called. The less responsive or slowest element that took the longest time to load (829 ms) belongs to the original domain Oculavis.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.5 kB (43%)

Content Size

1.2 MB

After Optimization

705.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oculavis.de 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. 55% of websites need less resources to load. HTML takes 630.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 515.1 kB

  • Original 630.4 kB
  • After minification 611.5 kB
  • After compression 115.3 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 515.1 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 7.0 kB

  • Original 386.8 kB
  • After minification 379.8 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. Oculavis images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 487 B

  • Original 123.1 kB
  • After minification 123.1 kB
  • After compression 122.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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 9.0 kB

  • Original 96.3 kB
  • After minification 95.3 kB
  • After compression 87.3 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. Oculavis.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (64%)

Requests Now

89

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oculavis.de

oculavis.de

308 ms

394 ms

style.min.css

style.min.css

300 ms

theme.min.css

theme.min.css

301 ms

header-footer.min.css

header-footer.min.css

304 ms

custom-frontend.min.css

custom-frontend.min.css

306 ms

post-5.css

post-5.css

311 ms

widget-heading.min.css

widget-heading.min.css

381 ms

widget-divider.min.css

widget-divider.min.css

398 ms

widget-text-editor.min.css

widget-text-editor.min.css

400 ms

e-animation-sink.min.css

e-animation-sink.min.css

405 ms

fadeIn.min.css

fadeIn.min.css

406 ms

custom-pro-widget-mega-menu.min.css

custom-pro-widget-mega-menu.min.css

414 ms

e-animation-shrink.min.css

e-animation-shrink.min.css

478 ms

widget-social-icons.min.css

widget-social-icons.min.css

497 ms

apple-webkit.min.css

apple-webkit.min.css

499 ms

widget-nested-accordion.min.css

widget-nested-accordion.min.css

506 ms

swiper.min.css

swiper.min.css

509 ms

e-swiper.min.css

e-swiper.min.css

517 ms

custom-pro-frontend.min.css

custom-pro-frontend.min.css

575 ms

language-switcher.min.css

language-switcher.min.css

596 ms

global.css

global.css

599 ms

fadeInLeft.min.css

fadeInLeft.min.css

607 ms

widget-image.min.css

widget-image.min.css

609 ms

custom-widget-nested-tabs.min.css

custom-widget-nested-tabs.min.css

622 ms

widget-nested-carousel.min.css

widget-nested-carousel.min.css

672 ms

widget-counter.min.css

widget-counter.min.css

695 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

698 ms

widget-carousel.min.css

widget-carousel.min.css

709 ms

fadeInUp.min.css

fadeInUp.min.css

710 ms

widget-menu-anchor.min.css

widget-menu-anchor.min.css

724 ms

widget-forms.min.css

widget-forms.min.css

769 ms

flatpickr.min.css

flatpickr.min.css

794 ms

post-27726.css

post-27726.css

801 ms

post-27416.css

post-27416.css

814 ms

post-29183.css

post-29183.css

812 ms

post-27414.css

post-27414.css

829 ms

borlabs-cookie_1_en.css

borlabs-cookie_1_en.css

591 ms

font.css

font.css

604 ms

styles.css

styles.css

610 ms

page-transitions.min.js

page-transitions.min.js

619 ms

jquery.min.js

jquery.min.js

719 ms

jquery-migrate.min.js

jquery-migrate.min.js

632 ms

borlabs-cookie-prioritize.min.js

borlabs-cookie-prioritize.min.js

594 ms

wpstg-blank-loader.min.js

wpstg-blank-loader.min.js

605 ms

header.js

header.js

611 ms

hello-frontend.min.js

hello-frontend.min.js

620 ms

instant-page.min.js

instant-page.min.js

679 ms

jquery.sticky.min.js

jquery.sticky.min.js

670 ms

jquery-numerator.min.js

jquery-numerator.min.js

629 ms

imagesloaded.min.js

imagesloaded.min.js

614 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

640 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

634 ms

webpack.runtime.min.js

webpack.runtime.min.js

647 ms

frontend-modules.min.js

frontend-modules.min.js

654 ms

hooks.min.js

hooks.min.js

628 ms

i18n.min.js

i18n.min.js

613 ms

frontend.min.js

frontend.min.js

628 ms

core.min.js

core.min.js

622 ms

frontend.min.js

frontend.min.js

643 ms

elements-handlers.min.js

elements-handlers.min.js

647 ms

Homepage-scaled.webp

Homepage-scaled.webp

537 ms

dalle_1.webp

dalle_1.webp

347 ms

dalle_2.webp

dalle_2.webp

469 ms

dalle_3.webp

dalle_3.webp

270 ms

dalle_4.webp

dalle_4.webp

398 ms

icon_QR.svg

icon_QR.svg

305 ms

dalle_1_photo.webp

dalle_1_photo.webp

472 ms

icon_group.svg

icon_group.svg

403 ms

icon_workflows.svg

icon_workflows.svg

446 ms

icon_cases.svg

icon_cases.svg

502 ms

icon_priority_high.svg

icon_priority_high.svg

500 ms

icon_progress.svg

icon_progress.svg

546 ms

user_photo_icon.webp

user_photo_icon.webp

570 ms

icon_ticketing_2.webp

icon_ticketing_2.webp

574 ms

icon_ticketing_1.webp

icon_ticketing_1.webp

600 ms

icon_tel_hangup_D43438.svg

icon_tel_hangup_D43438.svg

604 ms

sideelem6.webp

sideelem6.webp

636 ms

Cases-qkpw06in1pr90tv1t30nfxklcdybanmketvyn4zecm.jpg

Cases-qkpw06in1pr90tv1t30nfxklcdybanmketvyn4zecm.jpg

653 ms

Servicekontaktpunkt-qjk8b9ax72zpmns972p7eukgqqhb49cgyh1nyuwajq.jpg

Servicekontaktpunkt-qjk8b9ax72zpmns972p7eukgqqhb49cgyh1nyuwajq.jpg

673 ms

Training-qkpvzak4lcji235gzp7c35mx5abu0y3oyfpgbqas86.jpg

Training-qkpvzak4lcji235gzp7c35mx5abu0y3oyfpgbqas86.jpg

677 ms

Workflows-qjk8be0459658plffmqc9bdrpnu56qv4n4b3d8pbom.jpg

Workflows-qjk8be0459658plffmqc9bdrpnu56qv4n4b3d8pbom.jpg

699 ms

Integration-qjk8b7f8tex4zfuzi1vy9v1jjyqkov50a7qp0az2w6.jpg

Integration-qjk8b7f8tex4zfuzi1vy9v1jjyqkov50a7qp0az2w6.jpg

693 ms

Cases-qkpw06in1pr083eluddw69yos17wnbocw8boyyryk8.jpg

Cases-qkpw06in1pr083eluddw69yos17wnbocw8boyyryk8.jpg

719 ms

Servicekontaktpunkt-qjk8b9ax72zgtxbt8d2g56yk6dqwgxe9fvheaoourc.jpg

Servicekontaktpunkt-qjk8b9ax72zgtxbt8d2g56yk6dqwgxe9fvheaoourc.jpg

712 ms

Training-qkpvzak4lcj99cp10zkkti10kxlfdm5hfu56nk3cfs.jpg

Training-qkpvzak4lcj99cp10zkkti10kxlfdm5hfu56nk3cfs.jpg

733 ms

Workflows-qjk8be04595wfz4zgx3kznrv5b3qjewx4iqtp2hvw8.jpg

Workflows-qjk8be04595wfz4zgx3kznrv5b3qjewx4iqtp2hvw8.jpg

708 ms

Integration-qjk8b7f8teww6pejjc9707fmzm061j6srm6fc4rn3s.jpg

Integration-qjk8b7f8teww6pejjc9707fmzm061j6srm6fc4rn3s.jpg

725 ms

oculavis-Tube-300x160.jpg

oculavis-Tube-300x160.jpg

726 ms

coporate-blog-300x160.jpg

coporate-blog-300x160.jpg

744 ms

oculavis-TechTalk-Podcast-300x160.jpg

oculavis-TechTalk-Podcast-300x160.jpg

750 ms

Accessibility Review

oculavis.de accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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.

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

oculavis.de best practices score

92

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

Page has valid source maps

SEO Factors

oculavis.de SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Oculavis.de 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 Oculavis.de 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

oculavis.de

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