5.6 sec in total
539 ms
4.5 sec
513 ms
Welcome to faleza.pl homepage info - get ready to check Faleza best content for Poland right away, or after learning these important things about faleza.pl
Hotel Faleza w Jastrzębiej Górze proponuje Państwu jedyne w swoim rodzaju pokoje z widokiem na morze, jakich nie oferują inne hotele nad polskim morzem
Visit faleza.plWe analyzed Faleza.pl page load time and found that the first response time was 539 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
faleza.pl performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.8 s
4/100
25%
Value13.1 s
3/100
10%
Value580 ms
52/100
30%
Value0.179
68/100
15%
Value14.9 s
8/100
10%
539 ms
644 ms
10 ms
277 ms
330 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 41% of them (67 requests) were addressed to the original Faleza.pl, 16% (26 requests) were made to Static.xx.fbcdn.net and 9% (15 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Faleza.pl.
Page size can be reduced by 1.3 MB (39%)
3.5 MB
2.1 MB
In fact, the total size of Faleza.pl main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 23.6 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 3.5 kB, which is 11% 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 23.6 kB or 76% of the original size.
Potential reduce by 46.6 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. Faleza images are well optimized though.
Potential reduce by 821.0 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 821.0 kB or 70% of the original size.
Potential reduce by 458.3 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. Faleza.pl needs all CSS files to be minified and compressed as it can save up to 458.3 kB or 90% of the original size.
Number of requests can be reduced by 78 (50%)
156
78
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faleza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
faleza.pl
539 ms
index.html
644 ms
analytics.js
10 ms
foundation.css
277 ms
app.css
330 ms
rwd.css
181 ms
reset.css
176 ms
style.css
254 ms
supersized.css
178 ms
supersized.shutter.css
257 ms
jquery.fancybox-1.3.4.css
257 ms
jquery.min.js
80 ms
modernizr.js
258 ms
foundation.min.js
498 ms
jquery.easing.min.js
379 ms
supersized.3.2.7.min.js
377 ms
supersized.shutter.js
378 ms
font-awesome.min.css
21 ms
collect
67 ms
wejs
69 ms
jquery.bxslider.js
307 ms
jquery.jcarousel.min.js
13 ms
superfish.js
331 ms
isotope.pkgd.min.js
412 ms
jquery.fancybox-1.3.4.pack.js
343 ms
foundation.min.js
502 ms
script.js
502 ms
conversion.js
16 ms
collect
61 ms
loading.gif
506 ms
calendar-icon.png
92 ms
gb.gif
91 ms
de.gif
90 ms
ru.gif
89 ms
logo.png
89 ms
close-btn.png
172 ms
google.jpg
173 ms
newsletter.png
172 ms
kamerka.png
173 ms
unia.png
262 ms
box_126.jpg
264 ms
box_199.jpg
263 ms
box_231.jpg
505 ms
box_216.jpg
260 ms
box_232.jpg
505 ms
box_223.jpg
505 ms
box_224.jpg
526 ms
box_225.jpg
525 ms
box_218.jpg
526 ms
box_6.jpg
524 ms
box_76.jpg
524 ms
box_197.jpg
524 ms
box_43.jpg
590 ms
6.th.jpg
1434 ms
45.jpg
706 ms
23.jpg
705 ms
44.jpg
851 ms
27.jpg
794 ms
64x64_green-21690-2.png
50 ms
gothic.woff
812 ms
WidgetEmbed-socialButtonIcon
62 ms
cdswidSOCIAL-v21186289283a.css%20%27%29%3B
13 ms
cdswidgets_m-c-v2102084671a.js
133 ms
embed
145 ms
cdswidSOCIAL-v21186289283a.css
161 ms
.html
688 ms
js
286 ms
init_embed.js
250 ms
nav-icon.png
552 ms
prev-button.png
550 ms
next-button.png
650 ms
marker-icon.png
652 ms
back.png
651 ms
forward.png
647 ms
231 ms
282.th.jpg
453 ms
284.th.jpg
550 ms
283.th.jpg
551 ms
248.th.jpg
549 ms
248.jpg
1071 ms
282.jpg
897 ms
284.jpg
1023 ms
progress.gif
642 ms
103 ms
common.js
99 ms
map.js
99 ms
google4.png
133 ms
overlay.js
132 ms
util.js
223 ms
onion.js
176 ms
search_impl.js
223 ms
StaticMapService.GetMapImage
263 ms
stats.js
195 ms
openhand_8_8.cur
150 ms
ViewportInfoService.GetViewportInfo
127 ms
ViewportInfoService.GetViewportInfo
126 ms
kh
225 ms
kh
196 ms
transparent.png
122 ms
controls.js
77 ms
vt
125 ms
vt
153 ms
vt
138 ms
vt
143 ms
vt
149 ms
vt
142 ms
vt
146 ms
vt
163 ms
vt
160 ms
vt
164 ms
vt
168 ms
vt
162 ms
vt
170 ms
css
125 ms
entity11.png
84 ms
mapcnt6.png
48 ms
tmapctrl.png
38 ms
AuthenticationService.Authenticate
25 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
19 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
33 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
42 ms
64x64_green-21690-2.png
38 ms
shape-one.png
91 ms
likebox.php
389 ms
kyEKgjk51ZE.css
86 ms
xgj7bXhJNEH.css
55 ms
Czh0gDTFcBt.css
53 ms
kE_Z8j4XNUS.css
75 ms
N-k91nHCZS2.css
76 ms
q68gy-v_YMF.js
88 ms
FJmpeSpHpjS.js
111 ms
0wM5s1Khldu.js
108 ms
1bNoFZUdlYZ.js
125 ms
njO1TPvGzoR.js
109 ms
OloiM1PZafe.js
123 ms
LTv6ZK-5zxz.js
130 ms
1FCa-btixu2.js
129 ms
Oagsvfb4VWi.js
168 ms
pObvZSrFc_4.js
175 ms
HgJbVwzBr8E.js
167 ms
H3EKDTObx05.js
163 ms
OZFAYTv-ZUg.js
166 ms
1QuX41zDRrx.js
173 ms
1458599_694490817242332_1828066990_n.jpg
216 ms
1452378_694491970575550_136818834_n.jpg
62 ms
10009276_607108509377667_836113422_n.jpg
66 ms
12646993_1217594708268866_2198976095206482413_n.jpg
66 ms
535142_767838070014009_8710714682535511537_n.jpg
67 ms
10492158_10152336386323163_6645313961614105981_n.jpg
74 ms
267476_468459506509149_2007118986_n.jpg
65 ms
12039605_10205177970308417_6236830733476441765_n.jpg
67 ms
12802933_1157817560909653_5228404038941769499_n.jpg
67 ms
12661748_1135635436461199_4683484580693573307_n.jpg
72 ms
12552929_1131768126847930_4408612821219916495_n.jpg
68 ms
12592687_1129081357116607_8684335592583658039_n.jpg
67 ms
12508972_1129081387116604_8026083915454461024_n.jpg
71 ms
12522969_1128634803827929_5753363721196582343_n.jpg
68 ms
wL6VQj7Ab77.png
59 ms
s7jcwEQH7Sx.png
58 ms
QDwYpIaRyfG.png
53 ms
K00K-UgnsKu.png
57 ms
gxbPuQdXIZP.png
57 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
7 ms
faleza.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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
faleza.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
faleza.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
PL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faleza.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it does not match the claimed English language. Our system also found out that Faleza.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.
faleza.pl
Open Graph description is not detected on the main page of Faleza. 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: