4.5 sec in total
435 ms
3.7 sec
389 ms
Visit flox.cz now to see the best up-to-date Flox content for Czech Republic and also check out these interesting facts you probably never knew about flox.cz
Vytvořte si snadno vlastní eshop nebo webovou stránku. Vyzkoušejte si na 30 dní zdarma výhody eshop systému ByznysWeb. Profesionální pomoc, administrace eshopu, správa objednávek.
Visit flox.czWe analyzed Flox.cz page load time and found that the first response time was 435 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.
flox.cz performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value4.9 s
28/100
25%
Value5.3 s
59/100
10%
Value530 ms
55/100
30%
Value0.01
100/100
15%
Value8.1 s
42/100
10%
435 ms
739 ms
515 ms
250 ms
31 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Flox.cz, 65% (42 requests) were made to Byznysweb.cz and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Byznysweb.cz.
Page size can be reduced by 200.1 kB (26%)
769.8 kB
569.8 kB
In fact, the total size of Flox.cz main page is 769.8 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. 55% of websites need less resources to load. Images take 486.9 kB which makes up the majority of the site volume.
Potential reduce by 59.5 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 18.5 kB, which is 25% 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 59.5 kB or 79% of the original size.
Potential reduce by 38.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. Flox images are well optimized though.
Potential reduce by 102.3 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 102.3 kB or 49% of the original size.
Number of requests can be reduced by 26 (44%)
59
33
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flox. 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 as a result speed up the page load time.
flox.cz
435 ms
www.byznysweb.cz
739 ms
webcss.css
515 ms
yepnope.js
250 ms
jquery.min.js
31 ms
mvh6woq.js
144 ms
recaptcha_ajax.js
9 ms
js.cookie.js
248 ms
webflox7.js
391 ms
conversion.js
17 ms
retargeting.js
344 ms
www.byznysweb.cz
134 ms
CZ.png
135 ms
SK.png
148 ms
US.png
146 ms
ES.png
146 ms
MX.png
251 ms
cz-logo.png
251 ms
banner_bg.jpg
557 ms
slider_shaper1500.png
436 ms
nb.png
804 ms
blank.cur
273 ms
phone.png
550 ms
tab.png
701 ms
mobileversion-phone2.png
550 ms
mobileversion-phone.png
559 ms
seo.jpg
912 ms
photo_shaper.png
678 ms
support4.jpg
685 ms
flat_sk.png
804 ms
cssprite_title4.png
807 ms
13.jpg
814 ms
14.jpg
826 ms
15.jpg
928 ms
16.jpg
930 ms
17.jpg
935 ms
18.jpg
943 ms
19.jpg
957 ms
20.jpg
1035 ms
1.jpg
1056 ms
5.jpg
1057 ms
7.jpg
1067 ms
9.jpg
1072 ms
bg_opinions.jpg
1046 ms
bg_newsblog.jpg
1125 ms
dc.js
107 ms
widgets.js
6 ms
123 ms
pixel
1081 ms
0Cwg5tARGRICBZybDc5dHUHN_tcxqUOWt4j2lKQ2hg3ffHPsgsMmeMJ6Mk6g5Mb.woff
124 ms
syp57oSSbA4tT1-cxuCmNpLxmmchtDaD_VT6jFczPDjffH-sgsMmeMJ6Mk6g5Mj.woff
175 ms
3bb4caaf-194e-44c5-98a7-8b72acfaa486.js
499 ms
retargeting
127 ms
web.min.js
333 ms
nb_retina4.png
1213 ms
tabScreen3.png
1222 ms
__utm.gif
16 ms
106 ms
tick2.png
933 ms
p.gif
117 ms
41 ms
a.gif
492 ms
roundtrip.js
7 ms
__utm.gif
24 ms
ABSRBTDUUJC7BIE2NJLCZM.js
298 ms
flox.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
flox.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
flox.cz 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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flox.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 Flox.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.
flox.cz
Open Graph data is detected on the main page of Flox. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: