3.1 sec in total
292 ms
2.6 sec
271 ms
Click here to check amazing Voss content. Otherwise, check out these important facts you probably never knew about voss.ag
Unsere Handelsvertretung ist der Achspunkt und Ansprechpartner für Stahl-, Metall- und Fassadenbauer, Schlossereien und auch für weitere Geschäftsfelder wie z. B. Facility Management. Bei Voss erwarte...
Visit voss.agWe analyzed Voss.ag page load time and found that the first response time was 292 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
voss.ag performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.9 s
3/100
25%
Value9.7 s
11/100
10%
Value90 ms
99/100
30%
Value0.489
17/100
15%
Value13.6 s
11/100
10%
292 ms
404 ms
427 ms
427 ms
428 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 96% of them (51 requests) were addressed to the original Voss.ag, 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (926 ms) belongs to the original domain Voss.ag.
Page size can be reduced by 39.6 kB (1%)
3.0 MB
2.9 MB
In fact, the total size of Voss.ag main page is 3.0 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. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 23.4 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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.4 kB or 81% of the original size.
Potential reduce by 16.2 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. Voss images are well optimized though.
Number of requests can be reduced by 29 (59%)
49
20
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
home
292 ms
5a857ac8364e8b02489439320e24e7aa.css
404 ms
Basic.css
427 ms
lightbox.min.css
427 ms
bootstrap-slider.min.css
428 ms
select2.css
429 ms
slick.css
428 ms
slick-theme.css
500 ms
jquery.fancybox.css
522 ms
docs.css
525 ms
bootstrap.css
625 ms
owl.carousel.css
523 ms
font-awesome.css
526 ms
animate.css
597 ms
jquery-ui.css
619 ms
style.css
621 ms
jquery-1.12.4.min.js
722 ms
jquery-ui.min.js
827 ms
js
62 ms
bootstrap.min.js
695 ms
owl.carousel.min.js
716 ms
custom.js
717 ms
wow.min.js
730 ms
Form.min.js
926 ms
lightbox.min.js
814 ms
bootstrap-slider.min.js
815 ms
select2.js
823 ms
slick.js
820 ms
jquery.fancybox.pack.js
924 ms
jquery.matchHeight.js
924 ms
custom.js
925 ms
a8d5c3ee6ee5767f10a72685ee5343a5.js
925 ms
gtm.js
77 ms
header-bg.jpg
583 ms
logo.png
149 ms
banner-bg_28.jpg
826 ms
lamellen-voss-werksvertetungen-1_10.jpg
633 ms
beschlaege-voss-werksvertetungen-1_08.jpg
448 ms
trafotueren-voss-bayern.jpg
450 ms
blechverarbeitung-rhoenblech-voss-bayern.jpg
422 ms
gitterroste-voss-bayern.jpg
711 ms
gitterroste-shop-online-K60-Normstufen.jpg
546 ms
gitterroste-shop-online-K60-individuelle-groessen.jpg
548 ms
contact.png
644 ms
footer-logo1.png
645 ms
footer-logo2.png
679 ms
diamond.png
584 ms
prev.png
595 ms
next.png
597 ms
loading.gif
630 ms
close.png
662 ms
Ubuntu-Regular.woff
664 ms
Ubuntu-Bold.woff
676 ms
voss.ag accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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.
voss.ag 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
voss.ag SEO score
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voss.ag can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Voss.ag 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.
voss.ag
Open Graph description is not detected on the main page of Voss. 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: