12.9 sec in total
413 ms
11.9 sec
575 ms
Visit clinimax.es now to see the best up-to-date Clinimax content and also check out these interesting facts you probably never knew about clinimax.es
Fabricantes y especialistas en equipamiento para colectividades. Secadoras de manos, fuentes de agua, dispensadores de jabón y de papel, barras de ayuda, equipamiento hoteles, etc.
Visit clinimax.esWe analyzed Clinimax.es page load time and found that the first response time was 413 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
clinimax.es performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.4 s
1/100
25%
Value13.6 s
2/100
10%
Value3,800 ms
1/100
30%
Value0.041
99/100
15%
Value26.1 s
0/100
10%
413 ms
1456 ms
277 ms
282 ms
558 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Clinimax.es, 86% (59 requests) were made to Simex.es and 7% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.9 sec) relates to the external source Simex.es.
Page size can be reduced by 1.5 MB (17%)
8.9 MB
7.3 MB
In fact, the total size of Clinimax.es main page is 8.9 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. 25% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 37.7 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 5.8 kB, which is 13% 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 37.7 kB or 82% of the original size.
Potential reduce by 1.1 MB
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, Clinimax needs image optimization as it can save up to 1.1 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 334.7 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 334.7 kB or 71% of the original size.
Potential reduce by 41.3 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. Clinimax.es needs all CSS files to be minified and compressed as it can save up to 41.3 kB or 81% of the original size.
Number of requests can be reduced by 25 (40%)
62
37
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Clinimax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
clinimax.es
413 ms
simex.es
1456 ms
styles.css
277 ms
language-selector.css
282 ms
style.css
558 ms
fancybox.css
418 ms
chronology-pro.css
287 ms
wpgmza_style.css
554 ms
jquery.js
1253 ms
jquery-migrate.min.js
710 ms
wp-e-commerce.js
1012 ms
jquery.livequery.js
700 ms
user.js
967 ms
thickbox.js
981 ms
jquery.form.min.js
870 ms
scripts.js
869 ms
masonry.min.js
1363 ms
jquery.masonry.min.js
974 ms
mason-grid.js
998 ms
small-menu.js
1108 ms
comment-reply.min.js
1108 ms
mason-grid-pro.js
1113 ms
jquery.fancybox.js
1508 ms
raphael-min.js
1954 ms
jquery.easing.js
1528 ms
iview.js
1819 ms
css
33 ms
css
48 ms
logo-clinimax-pie-simex.png
281 ms
logos-redes-linkedin-web.png
529 ms
logos-redes-twitter-web.png
780 ms
logos-redes-facebook-web.png
804 ms
simex_logo_contacto-esp1.png
1071 ms
simex_sello_24h.png
1088 ms
category-10.jpg
2093 ms
category-13.jpg
2196 ms
category-16.jpg
2331 ms
category-12.jpg
2398 ms
category-9.jpg
2578 ms
category-8.jpg
2607 ms
category-121.jpg
3584 ms
category-14.jpg
4310 ms
category-7.jpg
5201 ms
category-17.jpg
3542 ms
category-15.jpg
3530 ms
category-11.jpg
4391 ms
category-3.jpg
5048 ms
category-6.jpg
4950 ms
analytics.js
36 ms
es_ES.png
4581 ms
en_GB.png
4659 ms
caption-bg.png
4855 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
28 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
29 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
30 ms
LIom94sU9XlcGbVvjBz0oJ0EAVxt0G0biEntp43Qt6E.ttf
28 ms
M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf
29 ms
chronology.woff
4832 ms
collect
21 ms
simex-cabecera-papeleras.jpg
4925 ms
simex-cabecera-cambiapanales.jpg
5036 ms
simex-cabecera-dispensadores-papel.jpg
5588 ms
simex-cabecera-barras.jpg
5282 ms
simex-cabecera-accesorios.jpg
5353 ms
simex-cabecera-saneamiento.jpg
5436 ms
simex-cabecera-secamanos.jpg
6327 ms
simex-cabecera-secadores-cabellos.jpg
6406 ms
simex-cabecera-fuentes-agua.jpg
6808 ms
simex-cabecera-lavaojos.jpg
6922 ms
clinimax.es 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-*] attributes do not match their roles
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
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
Some elements have a [tabindex] value greater than 0
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.
clinimax.es 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
clinimax.es SEO score
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 Clinimax.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 Clinimax.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.
clinimax.es
Open Graph description is not detected on the main page of Clinimax. 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: