vorwerk.at Website Information

Daily Unique Visits: 0

Daily Page Views: 0

Income Per Day: $0

Estimated Value: $9

This website is located in Germany and is using following IP address 213.239.249.169. See the complete list of popular websites hosted in Germany.

vorwerk.at is registered under .AT top-level domain. Please check other sites in .AT zone.

Website vorwerk.at is using the following name servers:

dns3.telekom.at
dns1.telekom.at
dns2.telekom.at

and is probably hosted by Hetzner Online GmbH. See the full list of other websites hosted by Hetzner Online GmbH.

The highest website vorwerk.at position in Alexa rank database was 9182 and the lowest rank position was 998129. Current position of vorwerk.at in Alexa rank database is below 1 million.

Desktop speed score of vorwerk.at (67/100) is better than the results of 45.93% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of vorwerk.at (98/100) is better than the results of 55.61% of other sites and means that the page is mobile-friendly.

Mobile speed score of vorwerk.at (47/100) is better than the results of 28.68% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

vorwerk.at Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

vorwerk.at whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

% Copyright (c)2024 by NIC.AT (1)
%
% Restricted rights.
%
% Except for agreed Internet operational purposes, no part of this
% information may be reproduced, stored in a retrieval system, or
% transmitted, in any form or by any means, electronic, mechanical,
% recording, or otherwise, without prior permission of NIC.AT on behalf
% of itself and/or the copyright holders. Any use of this material to
% target advertising or similar activities is explicitly forbidden and
% can be prosecuted.
%
% It is furthermore strictly forbidden to use the Whois-Database in such
% a way that jeopardizes or could jeopardize the stability of the
% technical systems of NIC.AT under any circumstances. In particular,
% this includes any misuse of the Whois-Database and any use of the
% Whois-Database which disturbs its operation.
%
% Should the user violate these points, NIC.AT reserves the right to
% deactivate the Whois-Database entirely or partly for the user.
% Moreover, the user shall be held liable for any and all damage
% arising from a violation of these points.

% Quota exceeded

vorwerk.at server information

Servers Location

vorwerk.at desktop page speed rank

Last tested: 2019-06-24

Desktop Speed Medium

67/100

vorwerk.at Desktop Speed Test Quick Summary

priority - 14Reduce server response time

In our test, your server responded in 0.70 seconds.

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://corporate.vorwerk.de/typo3temp/compressor/…4d2.js.gzip?1560429618
https://corporate.vorwerk.de/typo3temp/compressor/…821.js.gzip?1560429622
https://corporate.vorwerk.de/typo3temp/compressor/…7d4.js.gzip?1560429616

Optimize CSS Delivery of the following:

https://corporate.vorwerk.de/typo3temp/compressor/…6b4c422.css?1560429612
https://corporate.vorwerk.de/typo3temp/compressor/…cbc3446.css?1560429613
https://corporate.vorwerk.de//typo3conf/Resources/…t/src/css/intlTelInput

priority - 10Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 98KiB (32% reduction).

Compressing https://corporate.vorwerk.de/fileadmin/_processed_…_stores_fa704c748b.jpg could save 37.7KiB (33% reduction).
Compressing https://corporate.vorwerk.de/fileadmin/_processed_…-VKnext_58f9bc0d4c.jpg could save 23.4KiB (32% reduction).
Compressing https://corporate.vorwerk.de/fileadmin/_processed_…rwaerts_de2c0dbecb.jpg could save 19.9KiB (34% reduction).
Compressing https://corporate.vorwerk.de/fileadmin/_processed_…cookkey_9d1769ccc4.jpg could save 17KiB (30% reduction).

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://kobold.vorwerk.de/gen_uuid.php (expiration not specified)
https://www.google-analytics.com/gtm/js?id=GTM-522…d=631853031.1561413843 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-794889033 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-5QMQ73G (15 minutes)
https://connect.facebook.net/signals/config/279877…9408?v=2.8.51&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 (20 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 37.1KiB (14% reduction).

Minifying https://corporate.vorwerk.de/typo3temp/compressor/…7d4.js.gzip?1560429616 could save 36.4KiB (14% reduction) after compression.
Minifying https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 could save 646B (85% reduction) after compression.
Minifying https://corporate.vorwerk.de/typo3temp/compressor/…4d2.js.gzip?1560429618 could save 104B (26% reduction) after compression.

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://vorwerk.at/
https://corporate.vorwerk.de/gate/at
https://corporate.vorwerk.de/gate/at/

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 9% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 452B (13% reduction).

Minifying https://corporate.vorwerk.de/gate/at/ could save 452B (13% reduction) after compression.

vorwerk.at Desktop Resource Breakdown

Total Resources	53
Number of Hosts	16
Static Resources	19
JavaScript Resources	19
CSS Resources	2

vorwerk.at mobile page speed rank

Last tested: 2018-12-31

Mobile Speed Bad

47/100

vorwerk.at Mobile Speed Test Quick Summary

priority - 56Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://corporate.vorwerk.de/typo3temp/compressor/…012.js.gzip?1542667770
https://corporate.vorwerk.de/typo3temp/compressor/…9ec.js.gzip?1542809126

Optimize CSS Delivery of the following:

https://corporate.vorwerk.de/typo3temp/compressor/…d4.css.gzip?1542667769
https://corporate.vorwerk.de/typo3temp/compressor/…80.css.gzip?1542809113
https://corporate.vorwerk.de/typo3temp/compressor/…29.css.gzip?1542809113

priority - 28Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 277.4KiB (41% reduction).

Compressing https://corporate.vorwerk.de/fileadmin/user_upload…_Frankfurt_3_72dpi.jpg could save 229KiB (75% reduction).
Compressing https://corporate.vorwerk.de/fileadmin/data/master…mg_4_3_UK_flooring.jpg could save 35.6KiB (14% reduction).
Compressing https://corporate.vorwerk.de/fileadmin/data/master…rmomix_TM5-cookkey.jpg could save 12.8KiB (12% reduction).

priority - 10Reduce server response time

In our test, your server responded in 0.49 seconds.

priority - 10Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://vorwerk.at/
https://corporate.vorwerk.de/gate/at
https://corporate.vorwerk.de/gate/at/

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 13% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 6Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://kobold.vorwerk.de/gen_uuid.php (expiration not specified)
https://www.google-analytics.com/gtm/js?id=GTM-522…d=496122529.1546270965 (15 minutes)
https://www.googletagmanager.com/gtag/js?id=AW-794889033 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-5QMQ73G (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/279877…9408?v=2.8.35&r=stable (20 minutes)
https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 36.9KiB (14% reduction).

Minifying https://corporate.vorwerk.de/typo3temp/compressor/…9ec.js.gzip?1542809126 could save 36.8KiB (14% reduction) after compression.
Minifying https://corporate.vorwerk.de/typo3temp/compressor/…012.js.gzip?1542667770 could save 104B (26% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 471B (11% reduction).

Minifying https://corporate.vorwerk.de/gate/at/ could save 471B (11% reduction) after compression.

vorwerk.at Mobile Resource Breakdown

Total Resources	57
Number of Hosts	15
Static Resources	24
JavaScript Resources	17
CSS Resources	3

vorwerk.at mobile page usability

Last tested: 2018-12-31

Mobile Usability Good

98/100

vorwerk.at Mobile Usability Test Quick Summary

priority - 1Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a id="ga_ela_1325066843_1" href="http://kobold.vorwerk.at" class="btn btn-link">Jetzt Kobold entdecken</a> is close to 1 other tap targets.

The tap target <a id="ga_ela_cookie_…icy__883670144" href="/at/datenschutz/">Klicken Sie hi…Informationen.</a> and 1 others are close to other tap targets.

The tap target <a id="ga_ela_cookie_…icy__883670144" href="/at/datenschutz/">Klicken Sie hi…Informationen.</a> is close to 1 other tap targets.

The tap target <a href="javascript:;" class="policy-close"></a> is close to 1 other tap targets.

vorwerk.at HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Line: 1 Column: - 2
"...<?xml version="1..."

Attribute “xmlns:og” not allowed here.

Line: 3 Column: 16 - 99
"...TYPE html> <html xmlns="http://www.w3.org/1999/xhtml" class="no-js" lang="de_AT" xmlns:og="http://ogp.me/ns#"> <head..."

Bad value “de_AT” for attribute “lang” on element “html”: The language subtag “de_at” is not a valid language subtag.

Line: 3 Column: 16 - 99
"...TYPE html> <html xmlns="http://www.w3.org/1999/xhtml" class="no-js" lang="de_AT" xmlns:og="http://ogp.me/ns#"> <head..."

No “p” element in scope but a “p” end tag seen.

Line: 83 Column: 22 - 25
"...middle" /></p></div>..."

Attribute “alt” not allowed on element “picture” at this point.

Line: 84 Column: 150 - 165
"..."_blank"> <picture alt=""> <sour..." Line: 89 Column: 424 - 439
"..."_blank"> <picture alt=""> <sour..." Line: 94 Column: 453 - 468
"..."_blank"> <picture alt=""> <sour..."

Attribute “src” not allowed on element “source” at this point.

Line: 85 Column: 1 - 114
"...e alt=""> <source src="/fileadmin/_processed_/csm_col_img_4_3_AT_kobold-VKnext_a5149ff09a.jpg" media="(max-width: 300px)" /><sourc..." Line: 85 Column: 115 - 228
"...300px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_kobold-VKnext_4f03ab8584.jpg" media="(max-width: 400px)" /><sourc..." Line: 85 Column: 229 - 342
"...400px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_kobold-VKnext_58f9bc0d4c.jpg" media="(max-width: 600px)" /><sourc..." Line: 85 Column: 343 - 456
"...600px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_kobold-VKnext_10c206af6a.jpg" media="(max-width: 800px)" /><sourc..." Line: 85 Column: 457 - 573
"...800px)" /><source src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_kobold-VKnext.jpg" media="" /> <nosc..." Line: 90 Column: 1 - 122
"...e alt=""> <source src="/fileadmin/_processed_/csm_col_img_4_3_AT_thermomix_TM5-cookkey_72e89d058d.jpg" media="(max-width: 300px)" /><sourc..." Line: 90 Column: 123 - 244
"...300px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_thermomix_TM5-cookkey_ef4cdf80c3.jpg" media="(max-width: 400px)" /><sourc..." Line: 90 Column: 245 - 366
"...400px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_thermomix_TM5-cookkey_9d1769ccc4.jpg" media="(max-width: 600px)" /><sourc..." Line: 90 Column: 367 - 488
"...600px)" /><source src="/fileadmin/_processed_/csm_col_img_4_3_AT_thermomix_TM5-cookkey_ad4765ab8b.jpg" media="(max-width: 800px)" /><sourc..." Line: 90 Column: 489 - 613
"...800px)" /><source src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_thermomix_TM5-cookkey.jpg" media="" /> <nosc..." Line: 95 Column: 1 - 113
"...e alt=""> <source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_1d18041fa7.jpg" media="(max-width: 300px)" /><sourc..." Line: 95 Column: 114 - 226
"...300px)" /><source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_593d23ef66.jpg" media="(max-width: 400px)" /><s..." Line: 95 Column: 227 - 339
"...400px)" /><source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_247eddcc91.jpg" media="(max-width: 600px)" /><sourc..." Line: 95 Column: 340 - 452
"...600px)" /><source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_8166b5270b.jpg" media="(max-width: 800px)" /><sourc..." Line: 95 Column: 453 - 547
"...800px)" /><source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_fa704c748b.jpg" media="" /> <nosc..."

Element “source” is missing required attribute “srcset”.

Bad value “” for attribute “media” on element “source”: Media query ended prematurely.

Line: 85 Column: 457 - 573
"...800px)" /><source src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_kobold-VKnext.jpg" media="" /> <nosc..." Line: 90 Column: 489 - 613
"...800px)" /><source src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_thermomix_TM5-cookkey.jpg" media="" /> <nosc..." Line: 95 Column: 453 - 547
"...800px)" /><source src="/fileadmin/_processed_/csm_col_img_12_4_vorwerk_stores_fa704c748b.jpg" media="" /> <nosc..."

Element “noscript” not allowed as child of element “picture” in this context. (Suppressing further errors from this subtree.)

Line: 86 Column: 1 - 10
"...dia="" /> <noscript> ..." Line: 91 Column: 1 - 10
"...dia="" /> <noscript> ..." Line: 96 Column: 1 - 10
"...dia="" /> <noscript> ..."

Element “picture” is missing a required instance of child element “img”.

Line: 89 Column: 1 - 10
"...noscript> </picture></a></..." Line: 94 Column: 1 - 10
"...noscript> </picture></a></..." Line: 99 Column: 1 - 10
"...noscript> </picture></a></..."

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 3 Column: 16 - 99
"...TYPE html> <html xmlns="http://www.w3.org/1999/xhtml" class="no-js" lang="de_AT" xmlns:og="http://ogp.me/ns#"> <head..."

Consider avoiding viewport values that prevent users from resizing documents.

Line: 17 Column: 1 - 90
"...t="de" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no" /> <meta..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 72 Column: 42 - 163
"...ar-brand"><img src="/typo3conf/Resources/Public/Media/img/logo-vorwerk.png" width="268" height="95" border="0" alt="Logo Vorwerk" /></a> <..." Line: 87 Column: 21 - 143
"... <img src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_kobold-VKnext.jpg" border="0" alt="" /> ..." Line: 92 Column: 21 - 151
"... <img src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_4_3_AT_thermomix_TM5-cookkey.jpg" border="0" alt="" /> ..." Line: 97 Column: 21 - 142
"... <img src="/fileadmin/data/master_corporate/08_Microsites/02_Gates/AT/col_img_12_4_vorwerk_stores.jpg" border="0" alt="" /> ..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 82 Column: 1 - 34
"...ntainer"> <section class="centered-teaser "><div c..." Line: 84 Column: 1 - 34
".../section> <section class="centered-teaser "><div c..." Line: 103 Column: 7 - 38
"...--> </div> <section class="footer-area-products"><div c..." Line: 105 Column: 1 - 29
"...entinfo"> <section class="footer-meta"> <div ..." Line: 115 Column: 1 - 36
"...y ### --> <section data-widget="cookiepolicy"> <div ..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 104 Column: 1 - 44
".../section> <footer class="clearfix" role="contentinfo"> <sect..."

vorwerk.at similar domains

Similar domains:

www.vorwerk.com
www.vorwerk.net
www.vorwerk.org
www.vorwerk.info
www.vorwerk.biz
www.vorwerk.us
www.vorwerk.mobi
www.orwerk.at
www.vorwerk.at
www.corwerk.at
www.vcorwerk.at
www.cvorwerk.at
www.forwerk.at
www.vforwerk.at
www.fvorwerk.at
www.gorwerk.at
www.vgorwerk.at
www.gvorwerk.at
www.borwerk.at
www.vborwerk.at
www.bvorwerk.at
www.vrwerk.at
www.virwerk.at
www.voirwerk.at
www.viorwerk.at
www.vkrwerk.at
www.vokrwerk.at
www.vkorwerk.at
www.vlrwerk.at
www.volrwerk.at
www.vlorwerk.at
www.vprwerk.at
www.voprwerk.at
www.vporwerk.at
www.vowerk.at
www.voewerk.at
www.vorewerk.at
www.voerwerk.at
www.vodwerk.at
www.vordwerk.at
www.vodrwerk.at
www.vofwerk.at
www.vorfwerk.at
www.vofrwerk.at
www.votwerk.at
www.vortwerk.at
www.votrwerk.at
www.vorerk.at
www.vorqerk.at
www.vorwqerk.at
www.vorqwerk.at
www.voraerk.at
www.vorwaerk.at
www.vorawerk.at
www.vorserk.at
www.vorwserk.at
www.vorswerk.at
www.voreerk.at
www.vorweerk.at
www.vorwrk.at
www.vorwwrk.at
www.vorwewrk.at
www.vorwwerk.at
www.vorwsrk.at
www.vorwesrk.at
www.vorwdrk.at
www.vorwedrk.at
www.vorwderk.at
www.vorwrrk.at
www.vorwerrk.at
www.vorwrerk.at
www.vorwek.at
www.vorweek.at
www.vorwerek.at
www.vorwedk.at
www.vorwerdk.at
www.vorwefk.at
www.vorwerfk.at
www.vorwefrk.at
www.vorwetk.at
www.vorwertk.at
www.vorwetrk.at
www.vorwer.at
www.vorwerj.at
www.vorwerkj.at
www.vorwerjk.at
www.vorweri.at
www.vorwerki.at
www.vorwerik.at
www.vorwerm.at
www.vorwerkm.at
www.vorwermk.at
www.vorwerl.at
www.vorwerkl.at
www.vorwerlk.at
www.vorwero.at
www.vorwerko.at
www.vorwerok.at

vorwerk.at Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

vorwerk.at TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

VORWERK.AT Thermomix® und Kobold Staubsauger | Vorwerk

vorwerk.at Website Information

Advertisement

vorwerk.at Alexa Rank

vorwerk.at whois

vorwerk.at server information

Servers Location

vorwerk.at desktop page speed rank

vorwerk.at Desktop Speed Test Quick Summary

priority - 14Reduce server response time

In our test, your server responded in 0.70 seconds.

priority - 14Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 10Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 98KiB (32% reduction).

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 37.1KiB (14% reduction).

priority - 3Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 452B (13% reduction).

vorwerk.at Desktop Resource Breakdown

vorwerk.at mobile page speed rank

vorwerk.at Mobile Speed Test Quick Summary

priority - 56Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 28Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 277.4KiB (41% reduction).

priority - 10Reduce server response time

In our test, your server responded in 0.49 seconds.

priority - 10Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

priority - 6Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 4Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 36.9KiB (14% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 471B (11% reduction).

vorwerk.at Mobile Resource Breakdown

vorwerk.at mobile page usability

vorwerk.at Mobile Usability Test Quick Summary

priority - 1Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

vorwerk.at HTML validation

Errors

Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)

Attribute “xmlns:og” not allowed here.

Bad value “de_AT” for attribute “lang” on element “html”: The language subtag “de_at” is not a valid language subtag.

No “p” element in scope but a “p” end tag seen.

Attribute “alt” not allowed on element “picture” at this point.

Attribute “src” not allowed on element “source” at this point.

Element “source” is missing required attribute “srcset”.

Bad value “” for attribute “media” on element “source”: Media query ended prematurely.

Element “noscript” not allowed as child of element “picture” in this context. (Suppressing further errors from this subtree.)

Element “picture” is missing a required instance of child element “img”.

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Consider avoiding viewport values that prevent users from resizing documents.

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.