5.1 sec in total
439 ms
3.9 sec
781 ms
Click here to check amazing IStore content for Poland. Otherwise, check out these important facts you probably never knew about istore.pl
Otwórz własny sklep internetowy i sprzedawaj online. Oprogramowanie Shoper ma wszystko, czego potrzebujesz. Wypróbuj przez 14 dni za darmo.
Visit istore.plWe analyzed Istore.pl page load time and found that the first response time was 439 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
istore.pl performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value9.1 s
1/100
25%
Value8.6 s
17/100
10%
Value1,980 ms
8/100
30%
Value0.005
100/100
15%
Value15.9 s
6/100
10%
439 ms
629 ms
373 ms
1912 ms
69 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Istore.pl, 33% (25 requests) were made to Assets-global.website-files.com and 17% (13 requests) were made to Development--shoper-web.netlify.app. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Shoper.pl.
Page size can be reduced by 304.8 kB (29%)
1.1 MB
752.4 kB
In fact, the total size of Istore.pl main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 676.7 kB which makes up the majority of the site volume.
Potential reduce by 217.6 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 217.6 kB or 75% of the original size.
Potential reduce by 87.2 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 87.2 kB or 13% of the original size.
Potential reduce by 0 B
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. Istore.pl has all CSS files already compressed.
Number of requests can be reduced by 37 (60%)
62
25
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IStore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
istore.pl
439 ms
629 ms
istore
373 ms
www.shoper.pl
1912 ms
shoper-lb.webflow.4c3fcd305.min.css
69 ms
webfont.js
63 ms
scrolldisable.js
61 ms
intlTelInput.css
215 ms
swiper-bundle.min.css
95 ms
uc.js
68 ms
gsap.min.js
93 ms
ScrollTrigger.min.js
232 ms
css
41 ms
swiper-bundle.min.css
25 ms
tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf
20 ms
tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf
24 ms
tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf
27 ms
tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf
29 ms
6NUh8FyLNQOQZAnv9bYEvDiIdE9Ea92uemAk_WBq8U_9v0c2Wa0K7iN7hzFUPJH58nib1603gg7S2nfgRYIctxuTCf7W.ttf
62 ms
6NUh8FyLNQOQZAnv9bYEvDiIdE9Ea92uemAk_WBq8U_9v0c2Wa0K7iN7hzFUPJH58nib1603gg7S2nfgRYIcNxyTCf7W.ttf
122 ms
email-decode.min.js
78 ms
gtm.js
162 ms
6374d2281cf709d489ffc789_ant-design_exclamation-circle-filled.svg
109 ms
66309f1871e48d033b9a68e7_hero_maj_v2.webp
118 ms
65d7504764d4a1455a547b98_631775e5eb31882819ad4723_phot0%20(1)-p-1080.webp
122 ms
65d7504764d4a1455a547827_ANSIN_logo%201.svg
120 ms
65d7504764d4a1455a5477f7_Mask%20group%20(2).webp
222 ms
65d7504764d4a1455a547c40_logo-posterilla.webp
124 ms
65d7504764d4a1455a547b4a_s2.webp
222 ms
65d7504764d4a1455a547b22_logo-mieta.webp
223 ms
65d7504764d4a1455a547b42_s3.webp
223 ms
65d7504764d4a1455a547c20_Group%201997.webp
241 ms
65d7504764d4a1455a547992_Group%202018.webp
222 ms
65d7504764d4a1455a54798f_Group%202017.webp
240 ms
65d7504764d4a1455a547994_Group%202016.webp
241 ms
65d7504764d4a1455a547a38_Group%202068.webp
242 ms
65d7504764d4a1455a547a36_Group%202070.webp
241 ms
65d7504764d4a1455a547b37_Group%202069.webp
278 ms
65d7504764d4a1455a5479a3_Rectangle%201905.svg
280 ms
65d7504764d4a1455a547a32_Group%2020622.webp
363 ms
65d7504764d4a1455a547b01_Group%20631.webp
364 ms
65d7504764d4a1455a547996_Group%202013.webp
285 ms
65d7504764d4a1455a547990_Group%202015.webp
364 ms
65d7504764d4a1455a5478a9_photo.webp
377 ms
65f0d541593f1776e2e5f967_PlusJakartaSans-VariableFont_wght.ttf
184 ms
jquery-3.5.1.min.dc5e7f18c8.js
162 ms
webflow.fd24bca44.js
276 ms
swiper-bundle.min.js
114 ms
intlTelInput.min.js
114 ms
formsubmit.js
14 ms
blackfriday.js
178 ms
pricelistv2.js
412 ms
navbarBehaviour.js
412 ms
global-data.js
412 ms
trial-step-one.js
488 ms
trial-step-two.js
451 ms
form-handler-main.js
517 ms
accordion.js
500 ms
animations.js
440 ms
gtm.js
412 ms
navigation.js
495 ms
login.js
524 ms
afiliant.js
252 ms
swiper-bundle.min.js
109 ms
nav_sticky.js
486 ms
65d7504764d4a1455a547a01_ant-design_exclamation-circle-filled.svg
267 ms
fbevents.js
193 ms
js
82 ms
js
178 ms
destination
274 ms
widget.js
331 ms
swiper-bundle.min.js
66 ms
minified.js
14 ms
vendors.js
69 ms
tracking.js
51 ms
istore.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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
istore.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
istore.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Tap targets are not sized appropriately
PL
PL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Istore.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 Istore.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.
istore.pl
Open Graph description is not detected on the main page of IStore. 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: