2.7 sec in total
320 ms
2.1 sec
210 ms
Click here to check amazing Gliss content. Otherwise, check out these important facts you probably never knew about gliss.es
El cuidado capilar específico para las necesidades de tu cabello
Visit gliss.esWe analyzed Gliss.es page load time and found that the first response time was 320 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
gliss.es performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value17.2 s
0/100
25%
Value9.5 s
12/100
10%
Value460 ms
62/100
30%
Value0
100/100
15%
Value11.6 s
18/100
10%
320 ms
418 ms
109 ms
102 ms
299 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Gliss.es, 76% (25 requests) were made to Gliss.schwarzkopf.es and 9% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Gliss.schwarzkopf.es.
Page size can be reduced by 271.1 kB (21%)
1.3 MB
992.6 kB
In fact, the total size of Gliss.es main page is 1.3 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. 30% of websites need less resources to load. Images take 898.9 kB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 2.4 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 15.6 kB or 79% of the original size.
Potential reduce by 9.3 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. Gliss images are well optimized though.
Potential reduce by 211.3 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 211.3 kB or 70% of the original size.
Potential reduce by 35.0 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. Gliss.es needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 80% of the original size.
Number of requests can be reduced by 7 (23%)
30
23
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gliss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
gliss.es
320 ms
www.gliss.schwarzkopf.es
418 ms
home.html
109 ms
cookiepolicydisclaimer.min.css
102 ms
glisskur.css
299 ms
jquery-1.4.4.min.js
336 ms
glisskur.js
490 ms
tracking.min.js
202 ms
cookiepolicydisclaimer.min.js
200 ms
Gliss.jpg
348 ms
logo_Skpf.png
334 ms
header-home_fuerza_resistencia.jpg
985 ms
banner_gliss_keratin_corto.jpg
786 ms
banner_gliss.jpg
1179 ms
banner_gliss_videos.jpg
594 ms
banner_home_lisoasiatico.jpg
1006 ms
facebook_teaser2.jpg
585 ms
banner_million_gloss_home.jpg
776 ms
home_teaser_dryshampoo.jpg
696 ms
footer_gliss.jpg
793 ms
like.php
248 ms
gk_silver_back.jpg
566 ms
icon-sprite.png
576 ms
nav_bg.png
585 ms
navi_sprite.png
663 ms
footer_bg.jpg
677 ms
qeKvIRsJabD.js
41 ms
LVx-xkvaJ0b.png
35 ms
gtm.js
31 ms
analytics.js
7 ms
linkid.js
8 ms
collect
13 ms
glisskur-print.css
102 ms
gliss.es 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.
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
gliss.es 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
gliss.es 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
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gliss.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Gliss.es 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.
gliss.es
Open Graph description is not detected on the main page of Gliss. 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: