12.7 sec in total
4.1 sec
8.3 sec
261 ms
Welcome to sanex.es homepage info - get ready to check Sanex best content for Spain right away, or after learning these important things about sanex.es
Descubre los productos dermatológicos para el cuidado de la piel de la mano de los profesionales. Soluciones avanzadas para proteger tu piel.
Visit sanex.esWe analyzed Sanex.es page load time and found that the first response time was 4.1 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
sanex.es performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value17.7 s
0/100
25%
Value10.0 s
9/100
10%
Value3,580 ms
1/100
30%
Value0.078
95/100
15%
Value13.7 s
10/100
10%
4105 ms
20 ms
99 ms
176 ms
182 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 79% of them (65 requests) were addressed to the original Sanex.es, 10% (8 requests) were made to Hubsanex.qa.contrapuntoservers.com and 6% (5 requests) were made to C.betrad.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Sanex.es.
Page size can be reduced by 302.8 kB (33%)
904.3 kB
601.5 kB
In fact, the total size of Sanex.es main page is 904.3 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. 55% of websites need less resources to load. Images take 525.7 kB which makes up the majority of the site volume.
Potential reduce by 24.2 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 24.2 kB or 79% of the original size.
Potential reduce by 28.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. Sanex images are well optimized though.
Potential reduce by 184.4 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 184.4 kB or 70% of the original size.
Potential reduce by 66.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. Sanex.es needs all CSS files to be minified and compressed as it can save up to 66.0 kB or 79% of the original size.
Number of requests can be reduced by 52 (64%)
81
29
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sanex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.sanex.es
4105 ms
ga.js
20 ms
system.base.css
99 ms
system.menus.css
176 ms
system.messages.css
182 ms
system.theme.css
187 ms
comment.css
190 ms
field.css
191 ms
node.css
194 ms
search.css
268 ms
user.css
274 ms
views.css
283 ms
ckeditor.css
290 ms
ctools.css
289 ms
customwidgets_multiselect.css
291 ms
custommenu.css
358 ms
slider.css
368 ms
blog-widget.css
376 ms
reset.css
390 ms
reset-fonts-grids.css
388 ms
screen.css
390 ms
screenInner.css
450 ms
all.css
462 ms
print.css
468 ms
jquery.js
574 ms
jquery.once.js
488 ms
drupal.js
484 ms
customwidgets.js
541 ms
customwidgets_multiselect.js
560 ms
es_zZYe2oTLjbf9TE_qKqqyq-yQbbupuAtgK9Xog-TOr_A.js
563 ms
sanex.blog.widget.js
590 ms
custommenu.js
588 ms
jquery.easing.1.3.js
640 ms
slider.js
652 ms
home.js
663 ms
all.js
677 ms
swfobject.js
681 ms
jquery.fancybox.css
708 ms
__utm.gif
15 ms
__utm.gif
7 ms
jquery.fancybox.js
730 ms
opacity_home_background.png
114 ms
logo_2.png
106 ms
top_menu.png
111 ms
bottom_menu.png
111 ms
360x180_banner_atopiderm_20may_2015.gif
2941 ms
7in1_%28363x180%29.png
2948 ms
banner_180x363_v2.jpg
2942 ms
banner_apollo.gif
2944 ms
SanexZero_%28360X180%29.jpg
2943 ms
bio_response_360x180-2.jpg
2940 ms
banner_formen_v5.jpg
2943 ms
banner_home.jpg
2945 ms
background_home.jpg
2948 ms
slider_background.png
2926 ms
logo_pie_sanex.png
2818 ms
footer_background.png
2819 ms
2817 ms
h1.js
2801 ms
flechas_slider.png
113 ms
header_text_es.png
122 ms
gradient_background.jpg
112 ms
gradient_background_content.jpg
116 ms
gradient_background_header.jpg
116 ms
gradient_background_arrow.jpg
114 ms
arrows.png
217 ms
open_comillas.png
212 ms
date_corner.jpg
219 ms
close_comillas.png
216 ms
loading_rss.gif
224 ms
4003.js
98 ms
app.css
100 ms
bottom_left.png
194 ms
top_left.png
196 ms
ric-info.png
19 ms
ric-close.png
33 ms
css
28 ms
768.css
101 ms
640.css
192 ms
dynamic.css
194 ms
bg1.png
19 ms
linkhub_layer_bg_transparent.png
98 ms
sanex.es accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
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.
sanex.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
Missing source maps for large first-party JavaScript
sanex.es SEO score
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 Sanex.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 Sanex.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.
sanex.es
Open Graph description is not detected on the main page of Sanex. 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: