5 sec in total
359 ms
4.3 sec
347 ms
Click here to check amazing Omni Vital content. Otherwise, check out these important facts you probably never knew about omnivital.de
Startseite Bionika Vital Onlineshop Übersicht Kategorien
Visit omnivital.deWe analyzed Omnivital.de page load time and found that the first response time was 359 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
omnivital.de performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value5.9 s
14/100
25%
Value10.7 s
7/100
10%
Value180 ms
91/100
30%
Value0.086
93/100
15%
Value26.7 s
0/100
10%
359 ms
1422 ms
17 ms
29 ms
27 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Omnivital.de, 83% (58 requests) were made to Bionika-vital.de and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Bionika-vital.de.
Page size can be reduced by 495.1 kB (41%)
1.2 MB
717.2 kB
In fact, the total size of Omnivital.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. Images take 613.0 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.9 kB or 80% of the original size.
Potential reduce by 23.4 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. Omni Vital images are well optimized though.
Potential reduce by 259.1 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 259.1 kB or 75% of the original size.
Potential reduce by 175.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. Omnivital.de needs all CSS files to be minified and compressed as it can save up to 175.7 kB or 85% of the original size.
Number of requests can be reduced by 40 (62%)
65
25
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omni Vital. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
omnivital.de
359 ms
www.bionika-vital.de
1422 ms
jquery.min.js
17 ms
jquery-ui.min.js
29 ms
jquery-migrate-1.2.1.min.js
27 ms
megamenu.min.css
214 ms
custom.css
216 ms
base.css
215 ms
page.css
329 ms
boxes.css
219 ms
specific.css
216 ms
theme.css
424 ms
jquery.timers-1.2.js
419 ms
jquery.cookie.js
420 ms
jquery.pstrength.1.1.js
428 ms
jquery.simplemodal-1.3.5.js
432 ms
jquery.semantictabs.js
539 ms
jquery.autocomplete.js
626 ms
jquery.jcarousel.js
629 ms
jquery.cal.js
632 ms
cloud-zoom.1.0.2.js
640 ms
jquery.mousewheel-3.0.4.pack.js
643 ms
jquery.fancybox-1.3.3.js
751 ms
jquery.tooltip.js
835 ms
jquery.tipTip.js
836 ms
jquery.dependClass.js
841 ms
hoverIntent.js
846 ms
jquery.dropdown.js
854 ms
jquery.waitforimages.js
957 ms
global.js
1043 ms
jtl.basket.js
1050 ms
jquery.nivo.slider.pack.js
1057 ms
xajax_core.js
1064 ms
megamenu.min.js
1068 ms
dailydeal.css
1168 ms
conversion.js
36 ms
css
65 ms
ger.png
219 ms
bionicabg.jpg
940 ms
header.jpg
430 ms
basket.png
225 ms
search_button.png
224 ms
go-home.png
224 ms
Bionika-Entsafter-DA-1000-schwarz.jpg
346 ms
ampel2.png
441 ms
entsafter-saftpressen-standmixer-doerrgeraete-getreidemuehlen-getreideflocker.jpg
547 ms
wasserfilter_2.jpg
453 ms
Haushalt-Wohnen.jpg
665 ms
Beauty-Wellness-Fitness.jpg
754 ms
Lebensmittel-Nahrungsergaenzung.jpg
662 ms
Literatur.jpg
782 ms
Bionika-Entsafter-DA-1000-rot.jpg
762 ms
Bionika-Entsafter-DA-1000-chrom-schwarz.jpg
890 ms
System-II-Sprossenglaeser-750-ml.jpg
882 ms
Wasserfilter-Aqua-Select-mit-Glaskanne.jpg
1020 ms
paypal.png
973 ms
vorkasse.png
997 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
72 ms
back.png
1043 ms
top.png
1045 ms
ger.png
1105 ms
fre.png
1130 ms
jtl.png
1159 ms
ga.js
62 ms
110 ms
__utm.gif
18 ms
61 ms
collect
78 ms
std_kSuchspecialOverlay_1_4.png
467 ms
print.css
111 ms
omnivital.de 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
omnivital.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
omnivital.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
![]()
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omnivital.de 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 German. Our system also found out that Omnivital.de main page’s claimed encoding is iso-8859-1. 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.
omnivital.de
Open Graph description is not detected on the main page of Omni Vital. 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: