2.7 sec in total
340 ms
1.3 sec
1.1 sec
Welcome to stihl.be homepage info - get ready to check STIHL best content for Belgium right away, or after learning these important things about stihl.be
Bij STIHL vind je een ruime keuze aan kettingzagen, heggenscharen, grasmaaiers en nog veel meer. Ontdek ons assortiment!
Visit stihl.beWe analyzed Stihl.be page load time and found that the first response time was 340 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.
stihl.be performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value20.6 s
0/100
25%
Value15.1 s
1/100
10%
Value3,970 ms
1/100
30%
Value0.067
97/100
15%
Value24.1 s
0/100
10%
340 ms
484 ms
14 ms
32 ms
39 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 91% of them (52 requests) were addressed to the original Stihl.be, 5% (3 requests) were made to Cdn.cookielaw.org and 2% (1 request) were made to Sgtm.stihl.be. The less responsive or slowest element that took the longest time to load (484 ms) belongs to the original domain Stihl.be.
Page size can be reduced by 316.8 kB (4%)
8.2 MB
7.9 MB
In fact, the total size of Stihl.be main page is 8.2 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. Only a small number of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 199.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. 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 199.4 kB or 89% of the original size.
Potential reduce by 117.4 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. STIHL images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 23 (43%)
54
31
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STIHL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
stihl.be
340 ms
www.stihl.be
484 ms
nl
14 ms
otSDKStub.js
32 ms
stihl-styles.c5ba5a8d0e4b39d485c6a9b09e8bc50e.css
39 ms
stihl-i18n.2ac3e08fb8a1314822d6afb3c9923ea2.js
26 ms
prod.091f778f6391ee1dd63a51479df271e4.js
21 ms
prod.6dc969c21d84f668c3232ca8ffca50e6.js
25 ms
prod.02e91aeef241375d22dda2f80b06bb6c.js
271 ms
stihl-mainnav-prod.d92b14163080e655305beba117c060d0.js
21 ms
prod.306095def4ba6caa58b55d8ba6db47f4.js
271 ms
prod.0df3d281c234b44f2e10485fa5e3221d.js
28 ms
prod.615ea683ad98783725049f4ec773c015.js
36 ms
prod.25d5ee7802e0604069b2fef6b0173470.js
276 ms
prod.7719e2ae65b5de858508775ba867277d.js
387 ms
prod.bc3837cfe4761b2b56113ed6d96b2b98.js
269 ms
stihl-showmore-prod.c9f762394df79f7acf2f31f2c3cbf0b1.js
261 ms
stihl-promotions-prod.e8b2498e4f4baf8c47e7077083e8224f.js
270 ms
prod.85e6ea972a7dc42721e22d1262e62c6c.js
269 ms
stihl-footer-prod.eec7a067209186ed591edc1b50123e42.js
272 ms
prod.fe643f5279488d220981688e9537fdc6.js
273 ms
stihl-browserhint-prod.938b7e14d662e4b360f88682ce951224.js
274 ms
prod.f48ad5b064c06ba6d2b96db384e32177.js
272 ms
prod.82fef8fe2f444337e023a0ebc965b5ba.js
278 ms
prod.441e9708f9a0f10073ef6cd6caa43c54.js
275 ms
fe90a9ec-a7c8-40e1-83e5-39fde1bec85e.json
241 ms
gtm.js
315 ms
icon-envelope-16.svg
60 ms
stihl-logo.svg
59 ms
icon-plus-16.svg
57 ms
Accurange_HP_big.jpg
75 ms
Accurange_HP_small.jpg
62 ms
icon-arrow-right-16.svg
73 ms
e7cf214c9bf647bd8683abb2dc30162c.jpg
97 ms
50079.jpg
60 ms
50433.jpg
73 ms
13104.jpg
98 ms
53157.jpg
104 ms
96939.jpg
103 ms
95347.jpg
100 ms
118357.jpg
102 ms
118358.jpg
103 ms
36549.jpg
125 ms
95125.jpg
105 ms
13743.jpg
104 ms
105381.jpg
123 ms
117659.jpg
112 ms
13748.jpg
110 ms
96938.jpg
94 ms
105039.jpg
89 ms
13100.jpg
102 ms
16882.jpg
88 ms
9877.jpg
99 ms
location
70 ms
icon-pen-white-32.svg
71 ms
icon-cross-white-16.svg
92 ms
otBannerSdk.js
26 ms
stihl.be 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
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
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>).
stihl.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
stihl.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stihl.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Stihl.be 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.
stihl.be
Open Graph description is not detected on the main page of STIHL. 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: