4.5 sec in total
1.1 sec
3.1 sec
292 ms
Welcome to poznan.travel homepage info - get ready to check POZnan best content for Poland right away, or after learning these important things about poznan.travel
POZnan.travel
Visit poznan.travelWe analyzed Poznan.travel page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
poznan.travel performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.9 s
81/100
25%
Value4.7 s
68/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value4.0 s
88/100
10%
1073 ms
111 ms
551 ms
222 ms
91 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 57% of them (42 requests) were addressed to the original Poznan.travel, 14% (10 requests) were made to Static.xx.fbcdn.net and 8% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Poznan.travel.
Page size can be reduced by 391.2 kB (27%)
1.5 MB
1.1 MB
In fact, the total size of Poznan.travel main page is 1.5 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 24.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. 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 24.9 kB or 79% of the original size.
Potential reduce by 59.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. POZnan images are well optimized though.
Potential reduce by 278.7 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 278.7 kB or 69% of the original size.
Potential reduce by 27.9 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. Poznan.travel needs all CSS files to be minified and compressed as it can save up to 27.9 kB or 79% of the original size.
Number of requests can be reduced by 15 (22%)
69
54
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of POZnan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
poznan.travel
1073 ms
6e8ba81f764fadabba80c977b76bcfbe_compressed.css
111 ms
0765644b6bb5870c44938ab72f0d5e5b_compressed.js
551 ms
main.js
222 ms
wejs
91 ms
all.js
178 ms
TBEX15-Sponsor-Badge-150x150.png
69 ms
12-sniezycowy_jar_720_260.jpg
113 ms
340swf16_plakat_poziom_bezbelki_720_260.jpg
222 ms
593flowRoot6542_720_260.png
881 ms
506zamek_w_Korniku_720_260.JPG
422 ms
12-sniezycowy_jar_170_120.jpg
218 ms
340swf16_plakat_poziom_bezbelki_170_120.jpg
219 ms
593flowRoot6542_170_120.png
328 ms
506zamek_w_Korniku_170_120.JPG
326 ms
glowna_karta_en.png
761 ms
glowna_audio_en.png
659 ms
183zoom_1146_o_165_160.jpg
432 ms
274fot_45_palac_rogalin_165_160.jpg
435 ms
142net_165_160.jpg
527 ms
157Studyjne_165_160.jpg
540 ms
glowne_en_planer.png
542 ms
glowna_en_budget.png
637 ms
glowna_en_dzieci.png
647 ms
glowna_en_okolice.png
648 ms
glowne_en_gry.png
743 ms
glowne_en_bizkal.png
761 ms
glowne_en_oferty.png
761 ms
glowne_en_materialy.png
767 ms
glowne_en_cim(2).png
858 ms
glowne_en_blog.png
860 ms
glowne_pl_wlkp(3).png
861 ms
analytics.js
15 ms
logo_biale.png
860 ms
hr.png
874 ms
jak_dojechac.png
975 ms
gdzie_spac.png
976 ms
gdzie_zjesc.png
977 ms
warto_zobaczyc.png
976 ms
co_robic.png
983 ms
turystyka_biznesowa.png
984 ms
flags.png
1054 ms
css.png
1062 ms
tchotel_2015_LL_TM-13096-2.jpg
62 ms
Ubuntu-R-webfont.woff
1166 ms
collect
13 ms
WidgetEmbed-tcdestre
21 ms
t4b_widget_tcd-v21145001207a.css%20%27%29%3B
2 ms
cdswidgets_m-c-v2102084671a.js
146 ms
TBEX15-Sponsor-Badge-150x150.png
4 ms
t4b_widget_tcd-v21145001207a.css
156 ms
181 ms
xd_arbiter.php
149 ms
xd_arbiter.php
250 ms
panorama.png
829 ms
eu-info.png
845 ms
like_box.php
151 ms
UThj8VI7Xhd.css
173 ms
FL1kvZ1wVUz.css
216 ms
q68gy-v_YMF.js
301 ms
GIPX3YHTHu1.js
370 ms
0wM5s1Khldu.js
297 ms
1bNoFZUdlYZ.js
298 ms
12376340_10153486952787893_6051363302381596063_n.png
297 ms
537959_10151289925967893_626185301_n.png
337 ms
12321273_175039169552688_8577314092022426376_n.jpg
377 ms
9554_173166166402241_5839242746819794321_n.jpg
463 ms
1379841_10150004552801901_469209496895221757_n.jpg
413 ms
12219449_931044816983631_3632524387951655226_n.jpg
445 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
49 ms
I6-MnjEovm5.js
46 ms
pQrUxxo5oQp.js
81 ms
tchotel_2015_LL_TM-13096-2.jpg
20 ms
poznan.travel accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
poznan.travel 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
poznan.travel SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poznan.travel can be misinterpreted by Google and other search engines. Our service has detected that English 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 Poznan.travel 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.
poznan.travel
Open Graph description is not detected on the main page of POZnan. 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: