Tools & Wizards About Us
flox1.cz screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

flox1.cz

Vlastní e-shop levně. Tvorba eshopu a webových stránek | ByznysWeb.cz

Page Load Speed

5.4 sec in total

First Response

720 ms

Resources Loaded

4.3 sec

Page Rendered

443 ms

flox1.cz screenshot

About Website

Click here to check amazing Flox 1 content. Otherwise, check out these important facts you probably never knew about flox1.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 flox1.cz

Key Findings

We analyzed Flox1.cz page load time and found that the first response time was 720 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

flox1.cz performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

www.flox1.cz

720 ms

main.css

528 ms

ie6fix.css

406 ms

slideshow.css

431 ms

pop_up.css

431 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Flox1.cz, 67% (56 requests) were made to Byznysweb-new1.biznisweb.sk and 10% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Byznysweb-new1.biznisweb.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.5 kB (31%)

Content Size

945.5 kB

After Optimization

656.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flox1.cz main page is 945.5 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 558.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 47.4 kB

  • Original 60.1 kB
  • After minification 53.6 kB
  • After compression 12.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 6.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 47.4 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 36.0 kB

  • Original 558.2 kB
  • After minification 522.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. Flox 1 images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 148.7 kB

  • Original 258.3 kB
  • After minification 251.9 kB
  • After compression 109.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 148.7 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 57.3 kB

  • Original 69.0 kB
  • After minification 57.3 kB
  • After compression 11.7 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. Flox1.cz needs all CSS files to be minified and compressed as it can save up to 57.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (45%)

Requests Now

77

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flox 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.flox1.cz

www.flox1.cz

720 ms

main.css

main.css

528 ms

ie6fix.css

ie6fix.css

406 ms

slideshow.css

slideshow.css

431 ms

pop_up.css

pop_up.css

431 ms

jquery.js

jquery.js

632 ms

jquery.shadow.js

jquery.shadow.js

421 ms

jquery.cookie.js

jquery.cookie.js

648 ms

main.js

main.js

645 ms

jquery.tools.min.js

jquery.tools.min.js

1008 ms

pop_up.js

pop_up.js

655 ms

jquery.slide.js

jquery.slide.js

744 ms

plusone.js

plusone.js

61 ms

conversion.js

conversion.js

16 ms

tracking.js

tracking.js

343 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

button_blog.png

button_blog.png

423 ms

pinterest-button.png

pinterest-button.png

40 ms

9.png

9.png

216 ms

7.png

7.png

218 ms

bg_top_1.png

bg_top_1.png

207 ms

ucho_new_cz.png

ucho_new_cz.png

225 ms

bg_header_2.png

bg_header_2.png

437 ms

bg_header_1.png

bg_header_1.png

382 ms

logo_flox_png.png

logo_flox_png.png

233 ms

button_create_small.png

button_create_small.png

349 ms

bg_li_selected.png

bg_li_selected.png

415 ms

bg_li_a.png

bg_li_a.png

432 ms

li_arrow_2.png

li_arrow_2.png

440 ms

button_fb.png

button_fb.png

581 ms

button_tw.png

button_tw.png

594 ms

button_yt.png

button_yt.png

627 ms

button_rss.png

button_rss.png

643 ms

biznisweb-start.png

biznisweb-start.png

780 ms

biznisweb-standard.png

biznisweb-standard.png

773 ms

biznisweb-maximum.png

biznisweb-maximum.png

932 ms

cross.png

cross.png

803 ms

tick.png

tick.png

827 ms

templates_411.jpg

templates_411.jpg

980 ms

templates_409.jpg

templates_409.jpg

1073 ms

templates_460.jpg

templates_460.jpg

1093 ms

templates_322.jpg

templates_322.jpg

1123 ms

templates_410.jpg

templates_410.jpg

1145 ms

templates_347.jpg

templates_347.jpg

1233 ms

templates_480.jpg

templates_480.jpg

1275 ms

templates_374.jpg

templates_374.jpg

1394 ms

templates_483.jpg

templates_483.jpg

1407 ms

templates_366.jpg

templates_366.jpg

1436 ms

templates_362.jpg

templates_362.jpg

1463 ms

templates_373.jpg

templates_373.jpg

1545 ms

templates_371.jpg

templates_371.jpg

1594 ms

templates_442.jpg

templates_442.jpg

1709 ms

templates_323.jpg

templates_323.jpg

1727 ms

templates_398.jpg

templates_398.jpg

1736 ms

templates_418.jpg

templates_418.jpg

1782 ms

button_google_plus.png

button_google_plus.png

407 ms

button_linkedin_mini.png

button_linkedin_mini.png

526 ms

li_arrow_3.png

li_arrow_3.png

1688 ms

ga.js

ga.js

17 ms

53 ms

swfobject.js

swfobject.js

735 ms

myx.js

myx.js

741 ms

__utm.gif

__utm.gif

24 ms

39 ms

37 ms

bg_blue_footer.png

bg_blue_footer.png

969 ms

bg_zavolame_spat.png

bg_zavolame_spat.png

1067 ms

bg_input.png

bg_input.png

1084 ms

bg_button_submit.png

bg_button_submit.png

1099 ms

bg_line.png

bg_line.png

1112 ms

bg_nase_programy.png

bg_nase_programy.png

1141 ms

bg_button_footer.png

bg_button_footer.png

1176 ms

bg_novinky_emailom.png

bg_novinky_emailom.png

1264 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

15 ms

fastbutton

fastbutton

68 ms

postmessageRelay

postmessageRelay

54 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

28 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

46 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

40 ms

rpc:shindig_random.js

rpc:shindig_random.js

34 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

print.css

print.css

127 ms

Accessibility Review

flox1.cz accessibility score

95

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

flox1.cz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

flox1.cz SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flox1.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 Flox1.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.

Social Sharing Optimization

flox1.cz

Open Graph description is not detected on the main page of Flox 1. 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: