5.9 sec in total
156 ms
4.4 sec
1.4 sec
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 156 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
loewe.it performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.6 s
8/100
25%
Value10.5 s
7/100
10%
Value4,130 ms
1/100
30%
Value0.119
85/100
15%
Value16.3 s
5/100
10%
156 ms
835 ms
70 ms
562 ms
85 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Loewe.it, 4% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Loewe.tv.
Page size can be reduced by 527.3 kB (7%)
7.6 MB
7.0 MB
In fact, the total size of Loewe.it main page is 7.6 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. 60% of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.
Potential reduce by 514.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. This page needs HTML code to be minified as it can gain 104.8 kB, which is 17% 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 514.9 kB or 85% of the original size.
Potential reduce by 0 B
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 11.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.
Potential reduce by 860 B
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 has all CSS files already compressed.
Number of requests can be reduced by 19 (37%)
51
32
The browser has sent 51 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 9 to 1 for JavaScripts and as a result speed up the page load time.
gl
156 ms
en
835 ms
css2
70 ms
app.min.css
562 ms
js
85 ms
api.js
55 ms
lightgallery-bundle.css
50 ms
router.js
316 ms
routing
366 ms
app.min.js
713 ms
uc.js
29 ms
video.min.js
20 ms
gtm.js
101 ms
loewe-logo.svg
284 ms
envelope.svg
276 ms
bild-v-55xx_10.png
289 ms
bild-i-65-dr-xx_05.png
299 ms
stellar%2055%20main_7.png
293 ms
bild-s-77xx_07.png
346 ms
Iconic55_pure_white_main.png
563 ms
we.see%20oled%2048%20main.png
567 ms
Bild_c.43_main.png
595 ms
We-SEE-50-aqua-bluexx_54.png
582 ms
we.beam%20catalogue%20images.png
582 ms
WE.HEAR%20PRO_front_yellow%20square.png
639 ms
We.%20HEAR%201%20storm%20grey%20main.png
849 ms
klang%20mr5%20main.png
845 ms
klang%20s3%20lichtgrau%20main.png
866 ms
Klang_bar3mr_main.png
858 ms
klang%20sub1%20main.png
880 ms
multi.room%20amp%20main.png
927 ms
Aura.pure%20main.png
1130 ms
arrow_down_regular.svg
1131 ms
user.svg
1155 ms
search.svg
1163 ms
arrow-right.svg
1170 ms
WE_HEAR_KV_06_FULL_V1.jpg
1217 ms
truck-svgrepo-com_1.svg
1418 ms
shield-check-svgrepo-com.svg
1414 ms
refresh-ccw-svgrepo-com.svg
1462 ms
certificate-check-svgrepo-com.svg
1449 ms
Grid%201_Yellow_We%20Hear%20Pro.png
1464 ms
Grid%201_Black_We%20Hear%20Pro.png
1500 ms
Grid%201_Blue_We%20Hear%20Pro.png
1706 ms
HOME%20BANNER_Loewe_stellar_lifestyle_day_light%20-%20screenfill%20%281%29.jpg
1704 ms
Loewe_Iconic_lifestyle_white@2x.jpg
2206 ms
klang_mr1_lifestyle%201@2x.jpg
1567 ms
1923.svg
1699 ms
Below%20Section%20Home%20Page_Kylian%20We%20Hear%20Pro.jpg
1726 ms
recaptcha__en.js
69 ms
BentonSans-Medium.woff
1576 ms
BentonSans-Black.woff
1706 ms
BentonModernDisplay-Regular.woff
1718 ms
Virtual%20experience.png
1754 ms
Offline%20experience.jpg
1772 ms
arrow_down_regular_white.svg
1788 ms
loewe.it 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
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
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
Links do not have descriptive text
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
EN
EN
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 English is used on the page, and it matches the claimed 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: