3.9 sec in total
778 ms
3 sec
149 ms
Click here to check amazing Kiehl S content for Austria. Otherwise, check out these important facts you probably never knew about kiehls.at
Herzlich Willkommen bei Kiehl's! Bereits seit 1851 schätzen anspruchsvolle Kunden unsere einzigartigen und effizienten Haut- und Haarpflegeprodukte.
Visit kiehls.atWe analyzed Kiehls.at page load time and found that the first response time was 778 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kiehls.at performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value13.5 s
0/100
25%
Value7.0 s
33/100
10%
Value4,720 ms
0/100
30%
Value0.584
11/100
15%
Value17.7 s
4/100
10%
778 ms
478 ms
852 ms
336 ms
507 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 85% of them (68 requests) were addressed to the original Kiehls.at, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (852 ms) belongs to the original domain Kiehls.at.
Page size can be reduced by 110.6 kB (40%)
279.8 kB
169.1 kB
In fact, the total size of Kiehls.at main page is 279.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 109.4 kB which makes up the majority of the site volume.
Potential reduce by 60.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 8.8 kB, which is 12% 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 60.4 kB or 82% of the original size.
Potential reduce by 5.1 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. Kiehl S images are well optimized though.
Potential reduce by 45.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 45.1 kB or 47% of the original size.
Number of requests can be reduced by 46 (60%)
77
31
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kiehl S. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
index.aspx
778 ms
facadecss_1.min.axd
478 ms
facadejs_1.min.axd
852 ms
indexcss_1.min.axd
336 ms
carouseljs_1.min.axd
507 ms
gtm.js
122 ms
COMMON_INPUT_TEXT_CENTER_BORDER.gif
89 ms
HEADER_SIGN_IN_POPIN_CLOSE.gif
97 ms
HEADER_SIGN_IN_POPIN_LOGIN.gif
99 ms
HEADER_SIGN_IN_OFF.gif
86 ms
HEADER_REGISTER_OFF.gif
97 ms
HEADER_FULL_LOGO.gif
177 ms
HEADER_MY_BASKET.gif
181 ms
HEADER_VIEW_OFF.gif
178 ms
HEADER_BAG_OPEN_BASKET_LAYER.gif
197 ms
bouton_close.gif
213 ms
headerb_btn_ViewBskt_OFF.gif
213 ms
headerb_bottom.png
251 ms
HEADER_BAG_CLOSE_BASKET_LAYER.gif
252 ms
HEADER_MN_SRCH_ICN_GLASS_OFF.GIF
270 ms
TN_BTN_AbtKhls.gif
291 ms
TN_BTN_OrFvrts.gif
308 ms
TN_BTN_OrFvrts.gif
342 ms
TN_BTN_StrLctr.gif
332 ms
LCH_Kiehls_Februar_Carousel2_DE_01_el.jpg
847 ms
Kiehls_MASQUES_Banner_316x129_1.jpg
704 ms
homepage_doubleseparator.gif
386 ms
S1949901_s.jpg
406 ms
homepage_arrow.gif
414 ms
S1949301_s.jpg
436 ms
792_s.jpg
520 ms
S0762200_s.jpg
502 ms
facebook.jpg
493 ms
versand.jpg
548 ms
service.jpg
618 ms
FOOTER_JOIN_NOW_OFF.gif
603 ms
HEADER_LOGO_BLACK.gif
613 ms
POPIN_LOADING.gif
642 ms
TLN_SMPL_BTN_Close.png
721 ms
BTN_Rgstr_OFF.png
709 ms
BTN_SgnIn_OFF.png
698 ms
HEADER_SIGN_IN_POPIN_ON.gif
753 ms
gtm.js
42 ms
gtm.js
84 ms
55.js
723 ms
HEADER_SIGN_IN_BORDERCENTER_REPEAT.gif
722 ms
HEADER_SIGN_IN_BG.gif
753 ms
HEADER_SIGN_IN_BORDERBOTTOM.gif
752 ms
HEADER_BAG_POPIN_OFF.gif
812 ms
conversion_async.js
14 ms
fbevents.js
6 ms
105 ms
55 ms
HEADER_BAG_INPUT_TEXT_ROUND_BORDER_LEFT.gif
733 ms
HEADER_BAG_INPUT_TEXT_ROUND_BORDER_RIGHT.gif
734 ms
HEADER_CATALOG_NAV_BAR_ROUND_BORDER_LEFT.gif
741 ms
42 ms
HEADER_CATALOG_NAV_BAR_LIST.png
717 ms
HEADER_CATALOG_NAV_BAR_ROUND_BORDER_RIGHT.gif
709 ms
HEADER_CATALOG_NAV_TOPLEFT.GIF
763 ms
HEADER_CATALOG_NAV_TOPRIGHT.GIF
720 ms
HEADER_CATALOG_NAV_BOTTOMLEFT.GIF
732 ms
HEADER_CATALOG_NAV_BOTTOMRIGHT.GIF
710 ms
FOOTER_MENU_CONTENT_BOTTOM.gif
716 ms
FOOTER_BODY_CONTENT_BOTTOM.gif
711 ms
FOOTER_BACKGROUND.gif
722 ms
POPIN_LITEBOX_TOP_LEFT_CORNER.gif
739 ms
POPIN_LITEBOX_TOP_RIGHT_CORNER.gif
674 ms
POPIN_LITEBOX_CENTER_LEFT_BORDER.gif
664 ms
POPIN_LITEBOX_CENTER_RIGHT_BORDER.gif
688 ms
POPIN_LITEBOX_BOTTOM_LEFT_CORNER.gif
679 ms
POPIN_LITEBOX_BOTTOM_RIGHT_CORNER.gif
639 ms
POPIN_LITEBOX_BOTTOM_BORDER.gif
654 ms
COMMON_INPUT_TEXT_LEFT_ROUND_BORDER.gif
639 ms
COMMON_INPUT_TEXT_RIGHT_ROUND_BORDER.gif
627 ms
dc.js
28 ms
analytics.js
4 ms
collect
44 ms
__utm.gif
17 ms
ga-audiences
19 ms
kiehls.at 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 toggle fields do not have accessible names
ARIA IDs are not unique
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
Form elements do not have associated labels
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.
kiehls.at 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
kiehls.at 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kiehls.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Kiehls.at 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.
kiehls.at
Open Graph description is not detected on the main page of Kiehl S. 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: