12.7 sec in total
2.2 sec
10.1 sec
466 ms
Visit rocal.es now to see the best up-to-date Rocal content for Spain and also check out these interesting facts you probably never knew about rocal.es
La nostra aposta per la millora constant dels nostres productes, per la innovació i l'eficiència, ha situat la gamma de xemeneies Rocal a primera línia d'avantguarda
Visit rocal.esWe analyzed Rocal.es page load time and found that the first response time was 2.2 sec and then it took 10.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.
rocal.es performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.2 s
2/100
25%
Value21.5 s
0/100
10%
Value380 ms
70/100
30%
Value0.038
100/100
15%
Value8.1 s
42/100
10%
2171 ms
964 ms
246 ms
252 ms
261 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 90% of them (64 requests) were addressed to the original Rocal.es, 3% (2 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Rocal.es.
Page size can be reduced by 671.6 kB (25%)
2.7 MB
2.0 MB
In fact, the total size of Rocal.es main page is 2.7 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 80.1 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 14.5 kB, which is 14% 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 80.1 kB or 78% of the original size.
Potential reduce by 55.5 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. Rocal images are well optimized though.
Potential reduce by 404.6 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 404.6 kB or 68% of the original size.
Potential reduce by 131.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. Rocal.es needs all CSS files to be minified and compressed as it can save up to 131.4 kB or 84% of the original size.
Number of requests can be reduced by 17 (27%)
64
47
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rocal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rocal.es
2171 ms
bootstrap.min.css
964 ms
owl.carousel.css
246 ms
validationEngine.jquery.css
252 ms
lightbox.css
261 ms
styles.css
548 ms
panelClose.png
369 ms
hotspothebar.jpg
1708 ms
01-D10-Hotspot.jpg
1101 ms
02-City-Hotspot.jpg
1498 ms
03-Drop-Hotspot.jpg
1555 ms
04-Vertex-Hotspot.jpg
1506 ms
05-Oban-Hotspot.jpg
1789 ms
06-Born-Hotspot.jpg
2309 ms
no_image.png
1756 ms
timthumb.php
2050 ms
timthumb.php
2278 ms
timthumb.php
2418 ms
timthumb.php
2541 ms
timthumb.php
2783 ms
timthumb.php
3081 ms
timthumb.php
3297 ms
timthumb.php
3540 ms
timthumb.php
3813 ms
timthumb.php
4041 ms
timthumb.php
3922 ms
timthumb.php
4295 ms
timthumb.php
4541 ms
timthumb.php
4940 ms
timthumb.php
6165 ms
timthumb.php
5446 ms
timthumb.php
5592 ms
timthumb.php
5851 ms
timthumb.php
5831 ms
timthumb.php
5764 ms
timthumb.php
6121 ms
timthumb.php
6254 ms
timthumb.php
6608 ms
timthumb.php
6754 ms
jquery.min.js
14 ms
addthis_widget.js
12 ms
bootstrap.min.js
6165 ms
jquery.flexslider-min.js
6454 ms
owl.carousel.min.js
6617 ms
jquery.validationEngine.js
6327 ms
jquery.validationEngine_ENG.js
5680 ms
navigation.js
5537 ms
slider.js
5543 ms
form.js
5543 ms
client.js
5524 ms
gallery.js
5569 ms
2C9452_1_0.woff
5851 ms
2C9452_0_0.woff
5615 ms
timthumb.php
5467 ms
up.png
5202 ms
cookies.png
4990 ms
logo.png
4916 ms
down.png
4834 ms
bigclose.png
4536 ms
bigleft.png
4399 ms
bigright.png
4252 ms
close.png
3993 ms
loading.gif
3907 ms
prev.png
3803 ms
next.png
3589 ms
ga.js
42 ms
300lo.json
60 ms
sh.8e5f85691f9aaa082472a194.html
97 ms
__utm.gif
76 ms
collect
85 ms
more.png
123 ms
rocal.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
rocal.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
Issues were logged in the Issues panel in Chrome Devtools
rocal.es SEO score
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
CA
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rocal.es can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it does not match the claimed Spanish language. Our system also found out that Rocal.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.
rocal.es
Open Graph description is not detected on the main page of Rocal. 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: