1.5 sec in total
163 ms
1.3 sec
95 ms
Click here to check amazing Redken content. Otherwise, check out these important facts you probably never knew about redken.ch
Schau durch unsere professionelle Haarfarbe, Haarpflege und Styling Produkte. Entdecke Conditioner, Shampoos, Masken, Trockenshampoos, Haarfarben & vieles mehr.
Visit redken.chWe analyzed Redken.ch page load time and found that the first response time was 163 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
redken.ch performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value8.3 s
2/100
25%
Value7.1 s
32/100
10%
Value1,610 ms
12/100
30%
Value0.004
100/100
15%
Value11.6 s
18/100
10%
163 ms
711 ms
32 ms
96 ms
87 ms
Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Redken.ch, 74% (14 requests) were made to Redken.eu and 16% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Redken.eu.
Page size can be reduced by 229.6 kB (39%)
588.6 kB
358.9 kB
In fact, the total size of Redken.ch main page is 588.6 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. 15% of websites need less resources to load. Javascripts take 218.1 kB which makes up the majority of the site volume.
Potential reduce by 156.0 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 34.5 kB, which is 19% 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 156.0 kB or 85% of the original size.
Potential reduce by 2.7 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. Obviously, Redken needs image optimization as it can save up to 2.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 16.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. This website has mostly compressed JavaScripts.
Potential reduce by 54.4 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. Redken.ch needs all CSS files to be minified and compressed as it can save up to 54.4 kB or 33% of the original size.
Number of requests can be reduced by 11 (73%)
15
4
The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Redken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
redken.ch
163 ms
711 ms
otSDKStub.js
32 ms
redken-bundle.css
96 ms
jquery-3.6.0.min.js
87 ms
jquery.unobtrusive-ajax.min.js
90 ms
jquery.validate.min.js
58 ms
jquery.validate.unobtrusive.min.js
182 ms
form.tracking.js
88 ms
captcha.validatev2.js
187 ms
redken-bundle.js
207 ms
secondary-bundle.js
180 ms
3905de2d-64b9-49bd-b690-f5635502913e.json
38 ms
location
144 ms
redkenlogo.png
102 ms
otBannerSdk.js
22 ms
main.js
54 ms
helveticanowdisplay-regular.woff
20 ms
helveticanowdisplay-bold.woff
60 ms
redken.ch accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
redken.ch best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
redken.ch 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
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Redken.ch can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Redken.ch 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.
redken.ch
Open Graph description is not detected on the main page of Redken. 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: