5.4 sec in total
1.2 sec
3.9 sec
249 ms
Visit r-stahl.com now to see the best up-to-date R STAHL content for Netherlands and also check out these interesting facts you probably never knew about r-stahl.com
Visit r-stahl.comWe analyzed R-stahl.com page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
r-stahl.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value11.8 s
0/100
25%
Value9.9 s
10/100
10%
Value4,070 ms
1/100
30%
Value0.88
3/100
15%
Value14.5 s
9/100
10%
1188 ms
266 ms
272 ms
186 ms
277 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 90% of them (45 requests) were addressed to the original R-stahl.com, 6% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to Wm.wiredminds.de. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain R-stahl.com.
Page size can be reduced by 554.2 kB (26%)
2.1 MB
1.6 MB
In fact, the total size of R-stahl.com main page is 2.1 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.5 MB which makes up the majority of the site volume.
Potential reduce by 27.3 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 27.3 kB or 78% of the original size.
Potential reduce by 109.1 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. R STAHL images are well optimized though.
Potential reduce by 311.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 311.5 kB or 73% of the original size.
Potential reduce by 106.2 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. R-stahl.com needs all CSS files to be minified and compressed as it can save up to 106.2 kB or 65% of the original size.
Number of requests can be reduced by 26 (54%)
48
22
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R STAHL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
r-stahl.com
1188 ms
style.css
266 ms
style.css
272 ms
tx_jfmulticontent_pi1.css
186 ms
stylesheet_3f17b39103.css
277 ms
jquery.fancybox.css
554 ms
jquery.fancybox-thumbs.css
279 ms
seminars_pi1.css
351 ms
default.css
354 ms
screen.css
448 ms
content.css
462 ms
content-news.css
371 ms
photoswipe.css
440 ms
jquery-1.6.2-1.8.11-1.2.5.js
828 ms
jquery.anythingslider-1.8.6.min.js
552 ms
tx_seminars_pi1.js
533 ms
javascript_0b12553063.js
537 ms
jquery.fancybox.js
571 ms
jquery.fancybox-thumbs.js
457 ms
modernizr.custom.93758.js
461 ms
klass.min.js
477 ms
code.photoswipe.jquery-3.0.5.js
829 ms
productAccordeon.js
547 ms
javascript_14c9f9c271.js
549 ms
newsArchive.js
569 ms
wm_autotrack_v10_path.js
556 ms
1eaf27c0-f4de-4273-9f4c-1b3236ad2f3c.woff
210 ms
21decb60-b395-4de2-bd04-e38eb2a56d2f.woff
98 ms
ga.js
32 ms
logo_stahl.png
201 ms
bg-top.jpg
200 ms
logo-EX.png
102 ms
R-STAHL-Explorer-LED-6002-6402_02.jpg
1292 ms
RTEmagicC_STAHL_Logo_Pixel_CMYK_frei-PNG_03.png.png
201 ms
R-STAHL-Explorer-6002-Langfeldleuchte2_en.jpg
582 ms
Teaser_6148_Handscheinwerfer_01.jpg
355 ms
Seminar_iStock_000017433650_02.jpg
276 ms
Yodalex_teaser5.jpg
1030 ms
explosion_protection.jpg
291 ms
R.STAHL_Web_TeaserBox_Messen_67.jpg
371 ms
R.STAHL_Web_TeaserBox_Produkte_01.jpg
1533 ms
lupe.gif
446 ms
pfeil.gif
461 ms
t3-icon-actions.png
626 ms
youtube_icon_36px.jpg
552 ms
EXcovery_icon_36px.png
645 ms
inpage_linkid.js
11 ms
__utm.gif
13 ms
count.js
189 ms
count.js
394 ms
r-stahl.com accessibility score
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
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.
r-stahl.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
r-stahl.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R-stahl.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that R-stahl.com 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.
r-stahl.com
Open Graph description is not detected on the main page of R STAHL. 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: