6 sec in total
264 ms
3.8 sec
1.9 sec
Click here to check amazing STIHL content for Poland. Otherwise, check out these important facts you probably never knew about stihl.pl
Odkryj produkty STIHL, poradniki dotyczące ogrodnictwa i pielęgnacji, urządzenia oraz nowości ze świata STIHL
Visit stihl.plWe analyzed Stihl.pl page load time and found that the first response time was 264 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
stihl.pl performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value21.8 s
0/100
25%
Value19.0 s
0/100
10%
Value2,750 ms
3/100
30%
Value0.076
95/100
15%
Value31.3 s
0/100
10%
264 ms
133 ms
433 ms
42 ms
16 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 86% of them (51 requests) were addressed to the original Stihl.pl, 5% (3 requests) were made to Cdn.cookielaw.org and 3% (2 requests) were made to Sgtm.stihl.pl. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Stihl.pl.
Page size can be reduced by 1.1 MB (8%)
13.8 MB
12.7 MB
In fact, the total size of Stihl.pl main page is 13.8 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. 65% of websites need less resources to load. Images take 13.5 MB which makes up the majority of the site volume.
Potential reduce by 172.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 172.3 kB or 88% of the original size.
Potential reduce by 913.8 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 45 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 26 (47%)
55
29
The browser has sent 55 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 27 to 1 for JavaScripts and as a result speed up the page load time.
stihl.pl
264 ms
www.stihl.pl
133 ms
pl
433 ms
otSDKStub.js
42 ms
stihl-styles.3cab6d037c8fa35110901934d1e8fbe4.css
16 ms
stihl-i18n.2ac3e08fb8a1314822d6afb3c9923ea2.js
21 ms
prod.a95d4261366ac3172141e62a7eb8f807.js
20 ms
prod.74ab454fafc5c89860f6a4770a7ef065.js
22 ms
prod.9e6fb0b27da26ba91af5fa472dd69db7.js
23 ms
stihl-mainnav-prod.3c919fb1aaf747cf39f57504cb836cf1.js
23 ms
prod.76968ae05196d733077ea26f87f47c48.js
33 ms
prod.d949b1ed4e6db0cc9ab75d747da86331.js
23 ms
prod.2246e1b6dcb82bc5e17bf5dc648e2dd7.js
22 ms
prod.e1f5e9659119d0ee5931a07b1ddc9a16.js
23 ms
prod.dc7379b072a0041068b925233e638966.js
27 ms
prod.87cbb0cc3a0c741cd361a67c19c1b2a7.js
25 ms
prod.acc8e0fda30ff5acb5cfffd01f9bca92.js
34 ms
stihl-showmore-prod.3660c78ac362885abe7337299d85c957.js
24 ms
stihl-promotions-prod.fda344eb7995fa6792270598e4c00390.js
25 ms
stihl-footer-prod.c46babe87f3f2121e0a9806d267253f3.js
30 ms
prod.95777142033a05b2396ea12c11b70e27.js
30 ms
stihl-browserhint-prod.ff147abfafd96e0db61d22306a7bec65.js
29 ms
prod.6ed944904147c2dd52fb3cd913025440.js
30 ms
prod.e8c63a9f1131b51cf82ac09206e4b1ba.js
289 ms
prod.d85cb26dc79e5fecc0b9ec49c25baac3.js
294 ms
prod.c8a0d4dbe51af1bd314f643e3d4fb47f.js
289 ms
12f6367d-5e38-4d32-afcd-ef770a6bb93f.json
257 ms
gtm.js
401 ms
icon-envelope-16.svg
274 ms
stihl-logo.svg
662 ms
icon-plus-16.svg
359 ms
stihl-wiosna2024-AkuGratis-2400x1200-01.jpg
998 ms
95523_na%20stron%C4%99%20g%C5%82%C3%B3wn%C4%85_v2.jpg
995 ms
icon-arrow-right-16.svg
106 ms
4d43bc1ef76e44eebd875d52011e3836.jpg
702 ms
c29a2ed781ba4b84af210270bc312a6d.jpg
999 ms
95157.jpg
1028 ms
2951f5a92c1f487884a482b520615b76.jpg
804 ms
be163127173d41b78c19eef8da7576fd.jpg
1136 ms
e73b5005c8b048d1acfb93116e45d012.jpg
2729 ms
9c8ada1a816d47ecad14b87860714385.jpg
1656 ms
6329.jpg
1591 ms
7fdf3030f4b849adbbdbfe3112ce29dd.jpg
1681 ms
e7cf214c9bf647bd8683abb2dc30162c.jpg
1347 ms
e67063ffd9564969a5fd1573a376a648.jpg
2075 ms
121335.jpg
1609 ms
13100.jpg
2266 ms
13748.jpg
1700 ms
95146.jpg
1927 ms
105381.jpg
2344 ms
52363.jpg
1891 ms
99870.jpg
2063 ms
13741.jpg
2027 ms
icon-pen-white-32.svg
2330 ms
location
59 ms
otBannerSdk.js
37 ms
js
231 ms
web-vitals.iife.js
101 ms
web-vitals.iife.js
16 ms
stihl.pl 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.
stihl.pl 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
stihl.pl 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
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stihl.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Stihl.pl 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.pl
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: