4.5 sec in total
362 ms
3.8 sec
335 ms
Welcome to partystan.cz homepage info - get ready to check Party Stan best content for Czech Republic right away, or after learning these important things about partystan.cz
Párty stany s širokým výběrem rozměrů a možnostmi použití. Díky husté síti poboček jsme všude blízko.
Visit partystan.czWe analyzed Partystan.cz page load time and found that the first response time was 362 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
partystan.cz performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value10.6 s
0/100
25%
Value10.7 s
7/100
10%
Value8,370 ms
0/100
30%
Value0.022
100/100
15%
Value16.8 s
5/100
10%
362 ms
1038 ms
120 ms
236 ms
242 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 41% of them (43 requests) were addressed to the original Partystan.cz, 21% (22 requests) were made to Maps.google.com and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Partystan.cz.
Page size can be reduced by 723.5 kB (50%)
1.4 MB
714.3 kB
In fact, the total size of Partystan.cz main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 773.9 kB which makes up the majority of the site volume.
Potential reduce by 46.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 46.7 kB or 83% of the original size.
Potential reduce by 17.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. Party Stan images are well optimized though.
Potential reduce by 509.5 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 509.5 kB or 66% of the original size.
Potential reduce by 149.6 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. Partystan.cz needs all CSS files to be minified and compressed as it can save up to 149.6 kB or 86% of the original size.
Number of requests can be reduced by 42 (44%)
95
53
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Party Stan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
partystan.cz
362 ms
www.partystan.cz
1038 ms
format.css
120 ms
boxes.css
236 ms
modules.css
242 ms
lightbox.css
240 ms
thickbox.css
240 ms
slider.css
255 ms
date.css
257 ms
selectbox.css
349 ms
globals.js.php
473 ms
custom.globals.js.php
473 ms
hover.js
360 ms
header.js
353 ms
swfobject.js
357 ms
ga.js
24 ms
ga-set.js
458 ms
jquery-1.6.min.js
578 ms
js
29 ms
js-set-16a406afee4d23752100838cadad6bc0.js
606 ms
custom.jquery.init.js
502 ms
home_popis.jpg
939 ms
logo.gif
115 ms
search_submit.jpg
144 ms
g%2B32.png
144 ms
__utm.gif
24 ms
L.js
356 ms
homepage_main.gif
241 ms
homepage_main_center.gif
242 ms
topmenu.png
345 ms
topmenu_li.gif
244 ms
mainmenu_odd.gif
244 ms
bg_search.gif
341 ms
li_home.png
342 ms
home_button.png
343 ms
box_shadow.png
384 ms
nadpis_icons.png
448 ms
li_green.gif
448 ms
loadingAnimation.gif
418 ms
bottom.png
419 ms
fb-window.png
437 ms
ubuntu-b-webfont.woff
649 ms
ubuntu-r-webfont.woff
622 ms
ubuntu-m-webfont.woff
745 ms
common.js
25 ms
map.js
24 ms
overlay.js
22 ms
util.js
22 ms
geometry.js
22 ms
directions.js
22 ms
StaticMapService.GetMapImage
260 ms
onion.js
47 ms
openhand_8_8.cur
37 ms
infowindow.js
11 ms
css
42 ms
marker.js
38 ms
likebox.php
225 ms
ViewportInfoService.GetViewportInfo
137 ms
stats.js
27 ms
controls.js
21 ms
transparent.png
69 ms
google4.png
30 ms
mapcnt6.png
32 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
22 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
22 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
54 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
25 ms
sidlo.png
159 ms
pobocka.png
189 ms
tmapctrl.png
21 ms
cb_scout5.png
24 ms
tmapctrl4.png
23 ms
imgs8.png
22 ms
vt
21 ms
vt
33 ms
vt
23 ms
vt
23 ms
vt
27 ms
vt
27 ms
vt
23 ms
vt
25 ms
vt
24 ms
vt
27 ms
410ucuAGgaJ.css
295 ms
tSbl8xBI27R.css
378 ms
q68gy-v_YMF.js
501 ms
FJmpeSpHpjS.js
630 ms
0wM5s1Khldu.js
499 ms
1bNoFZUdlYZ.js
499 ms
AuthenticationService.Authenticate
251 ms
print.css
120 ms
10888522_959488484062580_8420519890163872806_n.jpg
352 ms
38605_150910184920418_3591062_n.jpg
417 ms
12801181_582785608542487_3612387895551110050_n.jpg
487 ms
11988245_10205711597448013_6446212231858524062_n.jpg
553 ms
12190070_119361631759818_2675803377872815132_n.jpg
551 ms
11046475_10207944825356316_9190649152189394259_n.jpg
555 ms
10440748_656206281134952_376628873298312315_n.jpg
602 ms
10926399_829949323717900_5323069732083351373_n.jpg
553 ms
10513414_947531248605597_1830223232197720265_n.jpg
614 ms
wL6VQj7Ab77.png
73 ms
s7jcwEQH7Sx.png
74 ms
I6-MnjEovm5.js
70 ms
pQrUxxo5oQp.js
138 ms
partystan.cz accessibility score
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
<frame> or <iframe> elements do not have a title
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
partystan.cz 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
partystan.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Partystan.cz can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Partystan.cz 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.
partystan.cz
Open Graph description is not detected on the main page of Party Stan. 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: