3.2 sec in total
280 ms
2.7 sec
219 ms
Visit planq.pl now to see the best up-to-date PlanQ content for Poland and also check out these interesting facts you probably never knew about planq.pl
PlanQ to sprawdzony, nowoczesny system planowania czasu pracy pracowników zatrudnionych w systemie równoważnym.
Visit planq.plWe analyzed Planq.pl page load time and found that the first response time was 280 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
planq.pl performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value8.2 s
2/100
25%
Value4.9 s
64/100
10%
Value710 ms
42/100
30%
Value0.002
100/100
15%
Value5.9 s
66/100
10%
280 ms
277 ms
116 ms
229 ms
347 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 97% of them (77 requests) were addressed to the original Planq.pl, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (975 ms) belongs to the original domain Planq.pl.
Page size can be reduced by 68.6 kB (9%)
790.4 kB
721.8 kB
In fact, the total size of Planq.pl main page is 790.4 kB. 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. Images take 718.6 kB which makes up the majority of the site volume.
Potential reduce by 11.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 2.3 kB, which is 15% 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 11.8 kB or 75% of the original size.
Potential reduce by 53.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. PlanQ images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 442 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. Planq.pl needs all CSS files to be minified and compressed as it can save up to 442 B or 15% of the original size.
Number of requests can be reduced by 16 (21%)
77
61
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PlanQ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
planq.pl
280 ms
www.planq.pl
277 ms
style.css
116 ms
anythingslider.css
229 ms
jquery-1.5.1.min.js
347 ms
jquery.anythingslider.js
240 ms
custom.js
229 ms
ga.js
230 ms
ga.js
39 ms
bg.png
116 ms
bg-none.png
145 ms
bg-top.png
141 ms
planQ-logo.png
116 ms
menu-top1.png
140 ms
menu-top2.png
142 ms
menu-top3.png
230 ms
menu-language.png
229 ms
language-pl1.png
253 ms
pl.png
254 ms
box-frame.png
254 ms
picture_4.jpg
501 ms
picture_3.jpg
573 ms
picture_2.jpg
685 ms
picture_5.jpg
591 ms
arrow-content.png
367 ms
box-content.png
368 ms
tel-content.png
637 ms
line-content.png
485 ms
box-bottom1.png
599 ms
nr1-box.png
620 ms
box-bottom2.png
688 ms
nr2-box.png
706 ms
box-bottom3.png
712 ms
nr3-box.png
739 ms
box-bottom4.png
750 ms
nr4-box.png
798 ms
box-bottom5.png
801 ms
nr5-box.png
819 ms
box1.png
862 ms
box2.png
888 ms
box3.png
889 ms
box4.png
922 ms
box5.png
940 ms
footer-top.png
940 ms
footer-all.png
975 ms
__utm.gif
13 ms
sep-left.png
894 ms
3.png
891 ms
1.png
900 ms
4.png
916 ms
6.png
917 ms
9.png
948 ms
19.png
891 ms
31.png
899 ms
13.png
902 ms
18.png
917 ms
15.png
917 ms
16.png
838 ms
17.png
866 ms
21.png
762 ms
22.png
767 ms
23.png
711 ms
25.png
693 ms
26.png
720 ms
27.png
728 ms
28.png
730 ms
29.png
699 ms
30.png
710 ms
32.png
693 ms
v9.png
721 ms
sep-right.png
723 ms
help.png
734 ms
arrow-bottom.png
698 ms
footer-menu1.png
710 ms
footer-menu2.png
693 ms
top-layer.png
913 ms
top-layer-x.jpg
688 ms
slide-li-hover.png
715 ms
slide-li.png
686 ms
planq.pl accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
planq.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
planq.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
PL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planq.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 Planq.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.
planq.pl
Open Graph description is not detected on the main page of PlanQ. 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: