4 sec in total
475 ms
3.2 sec
348 ms
Visit fajnpodnik.cz now to see the best up-to-date Fajn Podnik content and also check out these interesting facts you probably never knew about fajnpodnik.cz
Jedinečný internetový systém poskytující komplexní informace o pohostinských podnicích v naší databázi.
Visit fajnpodnik.czWe analyzed Fajnpodnik.cz page load time and found that the first response time was 475 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fajnpodnik.cz performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value8.6 s
1/100
25%
Value7.1 s
31/100
10%
Value220 ms
88/100
30%
Value0.002
100/100
15%
Value8.4 s
39/100
10%
475 ms
1121 ms
20 ms
381 ms
193 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 50% of them (53 requests) were addressed to the original Fajnpodnik.cz, 27% (28 requests) were made to Fonts.gstatic.com and 13% (14 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fajnpodnik.cz.
Page size can be reduced by 329.8 kB (43%)
765.0 kB
435.2 kB
In fact, the total size of Fajnpodnik.cz main page is 765.0 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. 60% of websites need less resources to load. Javascripts take 359.2 kB which makes up the majority of the site volume.
Potential reduce by 93.0 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 93.0 kB or 84% of the original size.
Potential reduce by 14.2 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. Fajn Podnik images are well optimized though.
Potential reduce by 167.1 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 167.1 kB or 47% of the original size.
Potential reduce by 55.5 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. Fajnpodnik.cz needs all CSS files to be minified and compressed as it can save up to 55.5 kB or 84% of the original size.
Number of requests can be reduced by 29 (43%)
68
39
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fajn Podnik. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fajnpodnik.cz
475 ms
www.fajnpodnik.cz
1121 ms
css
20 ms
stylebea6.css
381 ms
calendar.css
193 ms
colorbox.css
193 ms
jqueryeccb.js
384 ms
jquery.colorbox-min.js
196 ms
jquery.dynDateTime.js
365 ms
calendar-en.js
287 ms
jquery.scrollTo-min.js
286 ms
jquery.serialScroll-1.2.2.js
293 ms
tiny_mce_gzip.js
383 ms
fvalidate.js
487 ms
scripteccb.js
392 ms
jQuery.styledSelect.js
457 ms
js
28 ms
map.js
475 ms
reset.css
97 ms
gen_204
44 ms
analytics.js
124 ms
head_strip.jpg
120 ms
head.jpg
307 ms
index_search_bg.png
120 ms
index_search.png
119 ms
no_podnik.jpg
118 ms
door.gif
218 ms
4c932173bc91f8.279590119.jpg
229 ms
4c8f6bee6e17a0.985102458.jpg
229 ms
4c73954ce639d0.176195436.jpg
229 ms
4c346ad009eec0.407984489.jpg
228 ms
4c29a64167b6f0.347644154.jpg
277 ms
4bea8a637af5c0.547341769.jpg
307 ms
4be97d31600d45.240254072.jpg
305 ms
4cb8493dd00ff8.391268810.jpg
306 ms
4c1e702f1edbc3.938469732.jpg
305 ms
4bb324ed2d8f51.124860028.jpg
357 ms
4d8b533596f5a2.280514061.jpg
397 ms
4d89b5b582aeb9.963568481.jpg
391 ms
4d89b4c6ca7702.194091457.jpg
396 ms
4cc7fbf96fa111.208984747.jpg
396 ms
4cc589e2efb567.542955160.jpg
396 ms
4c06672b938a04.705652823.jpg
448 ms
4be2b7173e3c54.453522607.gif
486 ms
4bd05447dc4b12.127353841.jpg
492 ms
4bc829d389ee26.662457133.jpg
493 ms
bg_bar_info.png
472 ms
common.js
29 ms
util.js
29 ms
geocoder.js
33 ms
map.js
27 ms
marker.js
24 ms
foot_fire.png
385 ms
foot.png
435 ms
lqd.png
476 ms
external.html
480 ms
external.html
481 ms
external.html
480 ms
external.html
485 ms
external.gif
572 ms
controls.js
53 ms
openhand_8_8.cur
50 ms
onion.js
21 ms
ViewportInfoService.GetViewportInfo
44 ms
infowindow.js
42 ms
google_gray.svg
21 ms
AuthenticationService.Authenticate
29 ms
vt
64 ms
vt
58 ms
vt
55 ms
vt
60 ms
transparent.png
19 ms
vt
59 ms
map_row.png
348 ms
QuotaService.RecordEvent
14 ms
css
38 ms
css
38 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
31 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
32 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
33 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
33 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
31 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
33 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
34 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
34 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
38 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
34 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
41 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
34 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
35 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
35 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
35 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
42 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
35 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
36 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
36 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
48 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
38 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
38 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
39 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
40 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
40 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
48 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
48 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
48 ms
fajnpodnik.cz accessibility score
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
fajnpodnik.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
Browser errors were logged to the console
fajnpodnik.cz SEO score
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fajnpodnik.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 Fajnpodnik.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.
fajnpodnik.cz
Open Graph data is detected on the main page of Fajn Podnik. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: