Tools & Wizards About Us
quix.cz screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

quix.cz

QUIX = All in one agency for your event production in Prague

Page Load Speed

4.4 sec in total

First Response

518 ms

Resources Loaded

3.3 sec

Page Rendered

604 ms

quix.cz screenshot

About Website

Visit quix.cz now to see the best up-to-date QUIX content and also check out these interesting facts you probably never knew about quix.cz

We are a reliable partner for your event. We provide everything from 3D animations, complete technical equipment, scenography up to production and original performances.

Visit quix.cz

Key Findings

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

Performance Metrics

quix.cz performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

quix.cz

518 ms

quix.cz

433 ms

cs

396 ms

3c97d8d11f24b10e.css

108 ms

427e3d4fb11effe6.css

227 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 99% of them (76 requests) were addressed to the original Quix.cz, 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (955 ms) belongs to the original domain Quix.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.2 kB (2%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images

In fact, the total size of Quix.cz main page is 2.7 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. 50% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 62.8 kB

  • Original 75.6 kB
  • After minification 75.6 kB
  • After compression 12.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. 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 62.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 3.4 kB

  • Original 2.6 MB
  • After minification 2.6 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. QUIX images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 28 (38%)

Requests Now

73

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

quix.cz

quix.cz

518 ms

quix.cz

quix.cz

433 ms

cs

cs

396 ms

3c97d8d11f24b10e.css

3c97d8d11f24b10e.css

108 ms

427e3d4fb11effe6.css

427e3d4fb11effe6.css

227 ms

35f2d180b682783d.css

35f2d180b682783d.css

337 ms

fd9d1056-fb8a91bb6df355e5.js

fd9d1056-fb8a91bb6df355e5.js

634 ms

7023-3dade2ca3d194e7b.js

7023-3dade2ca3d194e7b.js

545 ms

main-app-a7b2761b260700ae.js

main-app-a7b2761b260700ae.js

437 ms

8173-e859fe3863b5edc6.js

8173-e859fe3863b5edc6.js

441 ms

4327-0800f099cef1d5c6.js

4327-0800f099cef1d5c6.js

442 ms

8087-40de429688938945.js

8087-40de429688938945.js

447 ms

layout-096f9f2848484091.js

layout-096f9f2848484091.js

543 ms

1027-c68986f418874b58.js

1027-c68986f418874b58.js

652 ms

3153-54edf8f6d380c6ec.js

3153-54edf8f6d380c6ec.js

551 ms

5008-e867812ef73a0da2.js

5008-e867812ef73a0da2.js

553 ms

page-8162b02a76752fc9.js

page-8162b02a76752fc9.js

650 ms

layout-aa8e4601b13907db.js

layout-aa8e4601b13907db.js

650 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

664 ms

webpack-1281c1de1806a20e.js

webpack-1281c1de1806a20e.js

657 ms

css

css

32 ms

close.03ca13b6.png

close.03ca13b6.png

112 ms

loading.99fd1e91.gif

loading.99fd1e91.gif

113 ms

prev.491323f3.png

prev.491323f3.png

108 ms

next.87312056.png

next.87312056.png

109 ms

image

image

110 ms

instagram.b252a471.png

instagram.b252a471.png

109 ms

facebook.f0a932d9.png

facebook.f0a932d9.png

211 ms

linkedin.c70173ee.png

linkedin.c70173ee.png

214 ms

vimeo.b7255ac4.png

vimeo.b7255ac4.png

215 ms

arrow-small-down.e724186f.png

arrow-small-down.e724186f.png

219 ms

image

image

320 ms

image

image

319 ms

image

image

518 ms

image

image

318 ms

image

image

423 ms

image

image

324 ms

image

image

526 ms

arrow-down.808c696a.png

arrow-down.808c696a.png

423 ms

image

image

531 ms

image

image

633 ms

image

image

632 ms

image

image

529 ms

image

image

827 ms

image

image

634 ms

image

image

638 ms

image

image

637 ms

image

image

739 ms

image

image

737 ms

image

image

742 ms

arrow-right.bd901768.png

arrow-right.bd901768.png

741 ms

arrow-left.f1abc24f.png

arrow-left.f1abc24f.png

744 ms

image

image

947 ms

image

image

846 ms

image

image

850 ms

image

image

953 ms

arrow-right.98f16334.png

arrow-right.98f16334.png

827 ms

slick.653a4cbb.woff

slick.653a4cbb.woff

827 ms

image

image

950 ms

image

image

955 ms

image

image

859 ms

location.f2660594.png

location.f2660594.png

927 ms

phone.b7c5a3d4.png

phone.b7c5a3d4.png

943 ms

mail.7ae10e3d.png

mail.7ae10e3d.png

850 ms

image

image

860 ms

phone-dark.4420c729.png

phone-dark.4420c729.png

929 ms

mail-dark.ea57ab06.png

mail-dark.ea57ab06.png

940 ms

instagram-dark.9eb4d850.png

instagram-dark.9eb4d850.png

843 ms

facebook-dark.60cf80f1.png

facebook-dark.60cf80f1.png

845 ms

linkedin-dark.49780613.png

linkedin-dark.49780613.png

849 ms

vimeo-dark.b1aafe06.png

vimeo-dark.b1aafe06.png

853 ms

image

image

824 ms

image

image

841 ms

image

image

748 ms

image

image

743 ms

image

image

742 ms

image

image

751 ms

Accessibility Review

quix.cz accessibility score

95

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Best Practices

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

SEO Factors

quix.cz SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    CS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quix.cz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Czech language. Our system also found out that Quix.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

quix.cz

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