11 sec in total
3.8 sec
6.4 sec
799 ms
Welcome to fct.put.poznan.pl homepage info - get ready to check Fct Put best content for Poland right away, or after learning these important things about fct.put.poznan.pl
Visit fct.put.poznan.plWe analyzed Fct.put.poznan.pl page load time and found that the first response time was 3.8 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fct.put.poznan.pl performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value20.3 s
0/100
25%
Value15.2 s
1/100
10%
Value840 ms
34/100
30%
Value0.005
100/100
15%
Value19.6 s
2/100
10%
3768 ms
309 ms
210 ms
217 ms
432 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 53% of them (46 requests) were addressed to the original Fct.put.poznan.pl, 25% (22 requests) were made to Maps.googleapis.com and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Fct.put.poznan.pl.
Page size can be reduced by 851.5 kB (51%)
1.7 MB
831.0 kB
In fact, the total size of Fct.put.poznan.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. 60% of websites need less resources to load. Javascripts take 841.8 kB which makes up the majority of the site volume.
Potential reduce by 48.7 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 48.7 kB or 80% of the original size.
Potential reduce by 50.3 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. Fct Put images are well optimized though.
Potential reduce by 601.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 601.6 kB or 71% of the original size.
Potential reduce by 150.8 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. Fct.put.poznan.pl needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 82% of the original size.
Number of requests can be reduced by 51 (67%)
76
25
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fct Put. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
fct.put.poznan.pl
3768 ms
system.base.css
309 ms
views_slideshow.css
210 ms
ldap_user.css
217 ms
calendar_multiday.css
432 ms
date.css
226 ms
datepicker.1.7.css
339 ms
date_repeat_field.css
332 ms
field.css
335 ms
views.css
411 ms
ctools.css
441 ms
ldap_servers.admin.css
448 ms
lightbox.css
442 ms
taxonomy_access.css
451 ms
views_slideshow_cycle.css
514 ms
gmap.css
545 ms
eu_cookie_compliance.css
551 ms
bootstrap.min.css
8 ms
overrides.css
762 ms
jquery.min.js
904 ms
jquery.once.js
553 ms
drupal.js
767 ms
views_slideshow.js
757 ms
bootstrap.min.js
14 ms
pl_iMVQi_W5-wEkFWd5XyXb9kNT6Hom0tYhxAb9XTjowgo.js
666 ms
auto_image_handling.js
765 ms
lightbox.js
1096 ms
jquery.cycle.all.min.js
890 ms
views_slideshow_cycle.js
883 ms
infobubble.js
866 ms
infobubble_extended.js
792 ms
gmap.js
1001 ms
js
27 ms
icon.js
919 ms
marker.js
969 ms
highlight.js
1030 ms
poly.js
1030 ms
gmap_markers.js
1045 ms
markerloader_static.js
1074 ms
markermanager_packed.js
1691 ms
markermanager_marker.js
996 ms
eu_cookie_compliance.js
891 ms
bootstrap.js
898 ms
logo_pp_header.png
533 ms
logo_wtch-wh.png
621 ms
1%20-%20Kopia.jpg
535 ms
Untitled%202_1.jpg
309 ms
Obraz1.png
1010 ms
Untitled%202.jpg
308 ms
7XUFZ5tgS-tD6QamInJTcYp67VRGBZnLJtqE-R4vad8.woff
88 ms
anMUvcNT0H1YN4FII8wpr0ERAIQjr9YjizTbIg8xdMI.woff
88 ms
anMUvcNT0H1YN4FII8wpr01BFkczmy2u5hEk7x1peg4.woff
88 ms
anMUvcNT0H1YN4FII8wprxeP0gNict45QRonF_H_dPw.woff
88 ms
glyphicons-halflings-regular.woff
85 ms
common.js
9 ms
map.js
8 ms
overlay.js
108 ms
util.js
105 ms
infowindow.js
104 ms
onion.js
47 ms
openhand_8_8.cur
109 ms
ViewportInfoService.GetViewportInfo
72 ms
stats.js
70 ms
controls.js
59 ms
transparent.png
60 ms
css
44 ms
google4.png
25 ms
mapcnt6.png
57 ms
sv5.png
66 ms
vt
62 ms
vt
62 ms
vt
59 ms
vt
51 ms
vt
57 ms
vt
86 ms
vt
108 ms
vt
86 ms
vt
98 ms
vt
106 ms
vt
107 ms
tmapctrl.png
39 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
7 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
6 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
5 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
7 ms
imgs8.png
33 ms
AuthenticationService.Authenticate
250 ms
fct.put.poznan.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
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
fct.put.poznan.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fct.put.poznan.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 Fct.put.poznan.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 Fct.put.poznan.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.
fct.put.poznan.pl
Open Graph description is not detected on the main page of Fct Put. 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: