2.7 sec in total
320 ms
2.2 sec
193 ms
Welcome to rittal.es homepage info - get ready to check Rittal best content right away, or after learning these important things about rittal.es
Cajas y armarios para la industria y las telecomunicaciones, soluciones para la distribución de corriente, componentes para la climatización de armarios eléctricos, infraestructura TI para Data Center...
Visit rittal.esWe analyzed Rittal.es page load time and found that the first response time was 320 ms and then it took 2.4 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.
rittal.es performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value2.4 s
91/100
25%
Value6.5 s
39/100
10%
Value1,260 ms
19/100
30%
Value0.005
100/100
15%
Value9.2 s
32/100
10%
320 ms
411 ms
215 ms
198 ms
207 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rittal.es, 95% (69 requests) were made to Rittal.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (860 ms) relates to the external source Rittal.com.
Page size can be reduced by 570.4 kB (60%)
946.5 kB
376.0 kB
In fact, the total size of Rittal.es main page is 946.5 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. 30% of websites need less resources to load. Javascripts take 454.3 kB which makes up the majority of the site volume.
Potential reduce by 54.4 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 19.2 kB, which is 30% 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 54.4 kB or 86% of the original size.
Potential reduce by 72.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, Rittal needs image optimization as it can save up to 72.7 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 325.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 325.5 kB or 72% of the original size.
Potential reduce by 117.9 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. Rittal.es needs all CSS files to be minified and compressed as it can save up to 117.9 kB or 83% of the original size.
Number of requests can be reduced by 34 (49%)
70
36
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rittal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
rittal.es
320 ms
411 ms
style.css
215 ms
ls.css
198 ms
popup.css
207 ms
modernizr-16min.js
204 ms
jquerymin.js
316 ms
mootools-yui-compressed.js
324 ms
merged-uncompressed.js
527 ms
rittal.js
318 ms
ls.js
314 ms
start.css
110 ms
nav.css
206 ms
base.css
208 ms
analytics.js
88 ms
slogan_en_new_print.png
177 ms
logo_rittal.png
179 ms
slogan_en_new.png
177 ms
440 ms
463 ms
465 ms
465 ms
510 ms
meta-nav-li-bg.png
177 ms
bg-nav-s.gif
176 ms
bg-nav-1st-a.png
177 ms
bg-nav-1st-span.png
273 ms
bg-navigation-flyout.png
271 ms
bg-search.png
273 ms
bg-start.gif
271 ms
657 ms
bg_slider_start.png
273 ms
bg-anc-left.png
269 ms
bg-anc-right.png
372 ms
626 ms
560 ms
661 ms
658 ms
714 ms
756 ms
815 ms
bg_control_nav.png
562 ms
753 ms
757 ms
758 ms
813 ms
854 ms
860 ms
858 ms
791 ms
collect
18 ms
suggest
236 ms
sliderarrowleft~1.png
201 ms
sliderarrowright~1.png
202 ms
bg_teaser_start_content.gif
203 ms
bg_teaser_start_top.gif
304 ms
765 ms
785 ms
collect
56 ms
702 ms
a_right.gif
206 ms
bg_teaser_start_bottom.gif
207 ms
footer-absolute-bg2.png
209 ms
bg_power_en.png
230 ms
logo_friedhelmlohgroup.png
302 ms
bg-nav-firstchild-roundcorner.png
207 ms
arrow-right-pink-small.gif
206 ms
bg-nav-flyout-bl.png
207 ms
bg-nav-flyout-br.png
223 ms
bg-nav-flyout-r.png
258 ms
528 ms
icon_forward.png
217 ms
close_x.gif
219 ms
rittal.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
rittal.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rittal.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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rittal.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 Rittal.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.
rittal.es
Open Graph data is detected on the main page of Rittal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: