Tools & Wizards About Us
flox.cz screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

flox.cz

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

Page Load Speed

17.1 sec in total

First Response

409 ms

Resources Loaded

10.2 sec

Page Rendered

6.5 sec

flox.cz screenshot

About Website

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.cz

Key Findings

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

Performance Metrics

flox.cz performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

flox.cz

409 ms

www.byznysweb.cz

844 ms

webflox.css

198 ms

webflox.js

646 ms

loading.svg

315 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Flox.cz, 57% (12 requests) were made to Byznysweb.cz and 19% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (8.6 sec) relates to the external source Byznysweb.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.0 kB (8%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Flox.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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 88.8 kB

  • Original 107.6 kB
  • After minification 79.4 kB
  • After compression 18.8 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 28.2 kB, which is 26% 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 88.8 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 16.1 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 6 (40%)

Requests Now

15

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 15 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

flox.cz

flox.cz

409 ms

www.byznysweb.cz

www.byznysweb.cz

844 ms

webflox.css

webflox.css

198 ms

webflox.js

webflox.js

646 ms

loading.svg

loading.svg

315 ms

gtm.js

gtm.js

147 ms

fbevents.js

fbevents.js

107 ms

miriam-dugovicova-miniplanetsk.jpg

miriam-dugovicova-miniplanetsk.jpg

831 ms

dusan-marian-durmekovci-liliana.jpg

dusan-marian-durmekovci-liliana.jpg

444 ms

marian-hornik-autobiznis.jpg

marian-hornik-autobiznis.jpg

878 ms

create_bg_img_3.jpg

create_bg_img_3.jpg

1001 ms

bariol_bold-webfont.woff

bariol_bold-webfont.woff

599 ms

bariol_regular-webfont.woff

bariol_regular-webfont.woff

8575 ms

bariol_regular_italic-webfont.woff

bariol_regular_italic-webfont.woff

502 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

633 ms

js

js

101 ms

analytics.js

analytics.js

27 ms

destination

destination

48 ms

destination

destination

96 ms

collect

collect

87 ms

landing

landing

76 ms

Accessibility Review

flox.cz accessibility score

89

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

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

flox.cz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

flox.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 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.

Social Sharing Optimization

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: