8.4 sec in total
415 ms
7.7 sec
269 ms
Click here to check amazing Friend content. Otherwise, check out these important facts you probably never knew about friend.pl
Od 25 lat budujemy polski internet. home.pl jest największym w Polsce dostawcą usług internetowych. Dołącz do grona naszych zadowolonych klientów.
Visit friend.plWe analyzed Friend.pl page load time and found that the first response time was 415 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
friend.pl performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value16.9 s
0/100
25%
Value11.2 s
5/100
10%
Value2,020 ms
7/100
30%
Value0.375
28/100
15%
Value16.5 s
5/100
10%
415 ms
2089 ms
480 ms
480 ms
479 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Friend.pl, 66% (40 requests) were made to Home.pl and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Home.pl.
Page size can be reduced by 856.6 kB (50%)
1.7 MB
849.2 kB
In fact, the total size of Friend.pl main page is 1.7 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. Javascripts take 939.9 kB which makes up the majority of the site volume.
Potential reduce by 35.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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 16% 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 35.4 kB or 78% of the original size.
Potential reduce by 8.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. Friend images are well optimized though.
Potential reduce by 621.9 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 621.9 kB or 66% of the original size.
Potential reduce by 190.5 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. Friend.pl needs all CSS files to be minified and compressed as it can save up to 190.5 kB or 87% of the original size.
Number of requests can be reduced by 19 (36%)
53
34
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Friend. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
friend.pl
415 ms
home.pl
2089 ms
tipTip.css
480 ms
normalize.css
480 ms
grid.css
479 ms
style.css
832 ms
widgets.css
1577 ms
48-20150127145353.css
590 ms
cpl_jquery.js
1428 ms
cpl_register.js
2484 ms
cpl_www_main.js
602 ms
slides.min.jquery.js
757 ms
ld.js
59 ms
analytics.js
104 ms
logo_home.png
213 ms
button_g_promo.png
260 ms
button_g_webmail.png
259 ms
button_g_panel.png
286 ms
ea5cb4b519e6c386360b0e9df5cfb0d4.png
393 ms
2871d7c075078d8669278113437cbe82.png
393 ms
c975d04490d6210ebe3ed9d3b41b70cf.png
807 ms
93c2af357ccd2d2dc0af7b7d9e76f969.jpg
1418 ms
4197c1b4514d1eec27d485d13f4b9928.jpg
1455 ms
e432f423710079ce765a8499714dd7ac.jpg
1317 ms
d255a8e28cc258d5df197de04cbd3b62.jpg
1302 ms
97f33c3cfcfce86389ed517ad7309341.png
595 ms
6a770d8802eeaff04428f6e0ed6abbab.png
714 ms
504ca3751ee7b1511987bcd3791a27a5.png
950 ms
427261ce13b7276997e47a6af3e8f63d.png
1118 ms
54f9c3d4d3431c0510819f56d94f6a4a.png
1225 ms
afd415cc7f6a8b09200f1743357a6f4f.png
1355 ms
e3a280e2ac3d0e6313924d10fea62265.png
1463 ms
hotjar-60573.js
201 ms
w.js
118 ms
OpenSans-Regular-webfont.woff
1463 ms
OpenSans-Bold-webfont.woff
1480 ms
OpenSans-Light-webfont.woff
1513 ms
bg_policies.png
1610 ms
footer_ico.png
1609 ms
bg_partners.png
1621 ms
ecommerce.js
89 ms
event
125 ms
sm.js
663 ms
collect
25 ms
basket.png
1492 ms
spinner-small-basket.gif
1624 ms
spinner-mid.gif
1708 ms
b8033d70ae481eda8d69bc07ea48c031.png
1769 ms
infobox-sprite.png
1799 ms
clickstream.min.js
90 ms
collect
82 ms
event
352 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
83 ms
ga-audiences
120 ms
storage.luckyorange.net
112 ms
settings.luckyorange.net
53 ms
inspectlet.js
37 ms
815759266
80 ms
visit-data
209 ms
r.gif
483 ms
dis.aspx
370 ms
friend.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-hidden="true"] elements contain focusable descendents
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
friend.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
friend.pl SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Friend.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Friend.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.
friend.pl
Open Graph description is not detected on the main page of Friend. 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: