9.8 sec in total
662 ms
5.4 sec
3.8 sec
Visit hs.pl now to see the best up-to-date Hs content for Poland and also check out these interesting facts you probably never knew about hs.pl
Sprzedaż detaliczna i hurtowa komputerów i laptopów poleasingowych, komputery używane, drukarki, AIO, serwery
Visit hs.plWe analyzed Hs.pl page load time and found that the first response time was 662 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hs.pl performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value25.8 s
0/100
25%
Value19.8 s
0/100
10%
Value14,160 ms
0/100
30%
Value0.003
100/100
15%
Value26.5 s
0/100
10%
662 ms
352 ms
331 ms
950 ms
394 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 36% of them (27 requests) were addressed to the original Hs.pl, 28% (21 requests) were made to Google.com and 16% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Hs.pl.
Page size can be reduced by 776.8 kB (14%)
5.6 MB
4.8 MB
In fact, the total size of Hs.pl main page is 5.6 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 4.8 MB which makes up the majority of the site volume.
Potential reduce by 108.8 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 51.5 kB, which is 40% 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 108.8 kB or 85% of the original size.
Potential reduce by 237.9 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. Hs images are well optimized though.
Potential reduce by 20.6 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 20.6 kB or 16% of the original size.
Potential reduce by 409.6 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. Hs.pl needs all CSS files to be minified and compressed as it can save up to 409.6 kB or 83% of the original size.
Number of requests can be reduced by 24 (35%)
69
45
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
hs.pl
662 ms
MTg6NTA2OjUuMjIuMzA.css
352 ms
fastdom.min.js
331 ms
main.bd4d775febf3d5e9771e.min.js
950 ms
pl_PL.js
394 ms
user.js
395 ms
d02_script.js
486 ms
front-api-1.4.0.min.js
509 ms
js
58 ms
loader.js
227 ms
fbevents.js
149 ms
body_bg.jpg
598 ms
1px.gif
222 ms
logo.png
596 ms
loader.svg
219 ms
bgk_1.jpg
3149 ms
5.jpg
597 ms
3.jpg
861 ms
ico_facebook.png
319 ms
bgk_2.jpg
2611 ms
laptopy.jpg
1191 ms
all-in-one.jpg
965 ms
monitory.jpg
1603 ms
komputery.jpg
1435 ms
drukarki.jpg
1259 ms
stacje-robocze.jpg
1581 ms
15-lat.jpg
1671 ms
embed
350 ms
ico_mail.png
1627 ms
loader.png
1626 ms
conversion_async.js
86 ms
fontawesome-webfont.woff
1590 ms
rwd-custom.woff
1554 ms
372745473574339
59 ms
app.js
152 ms
71 ms
20 ms
js
20 ms
gen_204
23 ms
init_embed.js
26 ms
common.js
71 ms
util.js
94 ms
map.js
85 ms
overlay.js
49 ms
onion.js
70 ms
search_impl.js
71 ms
openhand_8_8.cur
56 ms
ViewportInfoService.GetViewportInfo
120 ms
AuthenticationService.Authenticate
94 ms
vt
133 ms
vt
49 ms
vt
100 ms
vt
105 ms
vt
103 ms
vt
99 ms
vt
79 ms
vt
97 ms
vt
111 ms
vt
130 ms
vt
132 ms
vt
140 ms
vt
179 ms
vt
160 ms
vt
157 ms
vt
181 ms
QuotaService.RecordEvent
33 ms
vt
157 ms
vt
134 ms
controls.js
14 ms
css
202 ms
css
203 ms
entity11.png
113 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
84 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
85 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
103 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
104 ms
hs.pl 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
<frame> or <iframe> elements do not have a title
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
Heading elements are not in a sequentially-descending order
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.
hs.pl 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hs.pl SEO score
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
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 Hs.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 Hs.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.
hs.pl
Open Graph description is not detected on the main page of Hs. 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: