5.5 sec in total
323 ms
4.9 sec
260 ms
Welcome to loewe.it homepage info - get ready to check LOEWE best content right away, or after learning these important things about loewe.it
Experience brilliant color reproduction and a special sound experience with televisions and home cinema products from the LOEWE brand.
Visit loewe.itWe analyzed Loewe.it page load time and found that the first response time was 323 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
loewe.it performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value12.8 s
0/100
25%
Value12.2 s
3/100
10%
Value960 ms
29/100
30%
Value0.003
100/100
15%
Value11.7 s
17/100
10%
323 ms
531 ms
102 ms
265 ms
1621 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Loewe.it, 86% (67 requests) were made to Loewe.tv and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Loewe.tv.
Page size can be reduced by 822.8 kB (55%)
1.5 MB
683.1 kB
In fact, the total size of Loewe.it 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. 50% of websites need less resources to load. Javascripts take 720.8 kB which makes up the majority of the site volume.
Potential reduce by 17.6 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 17.6 kB or 77% of the original size.
Potential reduce by 16.6 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. LOEWE images are well optimized though.
Potential reduce by 509.5 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 509.5 kB or 71% of the original size.
Potential reduce by 279.1 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. Loewe.it needs all CSS files to be minified and compressed as it can save up to 279.1 kB or 85% of the original size.
Number of requests can be reduced by 50 (77%)
65
15
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOEWE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
loewe.it
323 ms
www.loewe.it
531 ms
102 ms
265 ms
1621 ms
stylesheet_1ecf0d21a5.css
104 ms
tx_dscviocontact_default.css
205 ms
tx_dscloewefaq_default.css
305 ms
font-awesome.min.css
309 ms
tx_dscnotifier.css
302 ms
forms.css
311 ms
loewe_chosen.css
313 ms
haendlersucheStyle_v2.css
315 ms
dsc_retailer.css
403 ms
login.css
404 ms
responiveform.css
407 ms
dsc_loeweproductreg.css
409 ms
tx_dscloegewinnspiel.css
412 ms
javascript_93077bb238.js
415 ms
screen.css
600 ms
mootools-core-1.3.2-full-compat-yc.js
606 ms
mootools-more-1.3.2.1-yc.js
806 ms
fonts.css
502 ms
css_browser_selector.js
506 ms
jquery-1.9.1.min.js
623 ms
jquery-migrate-1.2.1.js
623 ms
chosen.js
623 ms
jquery.easing-1.3.js
699 ms
jquery.timers-1.2.js
704 ms
onepagescroll.css
704 ms
jquery.onepage-scroll.js
709 ms
idle-timer.js
712 ms
lptoolkit.js
801 ms
jquery.dualslider.0.3.js
846 ms
jquery.tools.min.js
902 ms
ext_dsc_wizard_frontend.js
846 ms
chosen.jquery.css
910 ms
chosen.jquery.min.js
913 ms
lptoolkit.css
917 ms
mSlider.css
929 ms
raphstyle.css
839 ms
dsc.styledformfields.js
812 ms
jquery.cookie.js
711 ms
tx_dscnotifier.js
716 ms
notouch.js
712 ms
tx_dscviocontact_script.js
710 ms
tx_dscloewefaq_default.js
712 ms
jquery.placeholder.min.js
801 ms
dsc_loeweproductreg.js
712 ms
tx_dscloegewinnspiel.js
716 ms
fbevents.js
174 ms
lptoolkit-fonts.css
196 ms
68 ms
analytics.js
70 ms
logo_loewe_107x27.svg
103 ms
progress-end.png
106 ms
connect_herokachel_XL_1860x584_neu.jpg
396 ms
reference_doppelkachel_concert_XL_915x1206.jpg
529 ms
LOI_XL_915x588_.jpg
594 ms
art_uhd_XL_915x588_.jpg
298 ms
ico-facebook.png
205 ms
ico-instagram.png
204 ms
totop.png
280 ms
opensans-regular-webfont.woff
373 ms
opensans-light-webfont.woff
468 ms
opensans-semibold-webfont.woff
480 ms
opensans-bold-webfont.woff
571 ms
opensans-extrabold-webfont.woff
480 ms
fontawesome-webfont.woff
771 ms
loewemenue.woff
580 ms
icomoon.woff
580 ms
chosen-sprite.png
574 ms
linkid.js
4 ms
collect
13 ms
collect
24 ms
iframe_api
38 ms
www-widgetapi.js
26 ms
print.css
103 ms
loewe.it accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
loewe.it 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
Missing source maps for large first-party JavaScript
loewe.it SEO score
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
IT
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loewe.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it does not match the claimed German language. Our system also found out that Loewe.it 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.
loewe.it
Open Graph description is not detected on the main page of LOEWE. 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: