4.6 sec in total
355 ms
3.5 sec
751 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 355 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% 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%
355 ms
398 ms
135 ms
244 ms
392 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 98% of them (78 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 (1.3 sec) belongs to the original domain Planq.pl.
Page size can be reduced by 168.3 kB (19%)
894.3 kB
726.0 kB
In fact, the total size of Planq.pl main page is 894.3 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. 30% of websites need less resources to load. Images take 766.9 kB which makes up the majority of the site volume.
Potential reduce by 11.9 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.9 kB or 75% of the original size.
Potential reduce by 97.7 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. Obviously, PlanQ needs image optimization as it can save up to 97.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 58.3 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 58.3 kB or 54% of the original size.
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%)
78
62
The browser has sent 78 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
355 ms
www.planq.pl
398 ms
style.css
135 ms
anythingslider.css
244 ms
jquery-1.5.1.min.js
392 ms
jquery.anythingslider.js
271 ms
custom.js
269 ms
ga.js
256 ms
ga.js
65 ms
bg.png
197 ms
bg-none.png
273 ms
bg-top.png
259 ms
planQ-logo.png
227 ms
menu-top1.png
210 ms
menu-top2.png
201 ms
menu-top3.png
309 ms
menu-language.png
327 ms
language-pl1.png
327 ms
pl.png
351 ms
box-frame.png
380 ms
picture_4.jpg
628 ms
picture_3.jpg
662 ms
picture_2.jpg
677 ms
picture_5.jpg
818 ms
arrow-content.png
479 ms
box-content.png
501 ms
tel-content.png
719 ms
line-content.png
615 ms
box-bottom1.png
754 ms
nr1-box.png
754 ms
box-bottom2.png
779 ms
nr2-box.png
783 ms
box-bottom3.png
845 ms
nr3-box.png
878 ms
box-bottom4.png
887 ms
nr4-box.png
889 ms
box-bottom5.png
903 ms
nr5-box.png
928 ms
box1.png
983 ms
box2.png
1016 ms
box3.png
1075 ms
box4.png
1065 ms
box5.png
1117 ms
footer-top.png
1108 ms
footer-all.png
1138 ms
__utm.gif
11 ms
sep-left.png
966 ms
1.png
993 ms
3.png
991 ms
4.png
1029 ms
6.png
1000 ms
9.png
1327 ms
10.png
1281 ms
19.png
1245 ms
31.png
1215 ms
13.png
1186 ms
18.png
1138 ms
15.png
1169 ms
16.png
1160 ms
17.png
1062 ms
21.png
1068 ms
22.png
1052 ms
23.png
1053 ms
24.png
1042 ms
25.png
1022 ms
26.png
1048 ms
27.png
1025 ms
28.png
1052 ms
29.png
1042 ms
30.png
1056 ms
32.png
1056 ms
sep-right.png
1064 ms
help.png
1047 ms
arrow-bottom.png
1073 ms
footer-menu1.png
1073 ms
footer-menu2.png
1032 ms
top-layer.png
1280 ms
top-layer-x.jpg
1021 ms
slide-li-hover.png
996 ms
slide-li.png
982 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: