Tools & Wizards About Us
firotour.cz screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

firotour.cz

firotravel.cz - Cestovní kancelář

Page Load Speed

17.5 sec in total

First Response

5.3 sec

Resources Loaded

11.9 sec

Page Rendered

335 ms

firotour.cz screenshot

About Website

Visit firotour.cz now to see the best up-to-date Firotour content for Czech Republic and also check out these interesting facts you probably never knew about firotour.cz

Cs lipsum dolor sit amet

Visit firotour.cz

Key Findings

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

Performance Metrics

firotour.cz performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.7 s

0/100

25%

SI (Speed Index)

Value24.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,760 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

firotravel.cz

5327 ms

css2

45 ms

icon

62 ms

cookies.min.css

305 ms

magicstrap.min.css

777 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Firotour.cz, 7% (9 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Firotravel.cz.

Page Optimization Overview & Recommendations

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

Content Size

10.7 MB

After Optimization

9.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firotour.cz main page is 10.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. Only a small number of websites need less resources to load. Images take 9.7 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 511.0 kB

  • Original 535.4 kB
  • After minification 226.6 kB
  • After compression 24.3 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 308.8 kB, which is 58% 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 511.0 kB or 95% of the original size.

Image Optimization

-2%

Potential reduce by 209.9 kB

  • Original 9.7 MB
  • After minification 9.5 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. Firotour images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 26.5 kB

  • Original 244.9 kB
  • After minification 244.9 kB
  • After compression 218.4 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 26.5 kB or 11% of the original size.

CSS Optimization

-37%

Potential reduce by 72.3 kB

  • Original 195.8 kB
  • After minification 195.8 kB
  • After compression 123.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. Firotour.cz needs all CSS files to be minified and compressed as it can save up to 72.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (21%)

Requests Now

116

After Optimization

92

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

firotravel.cz

firotravel.cz

5327 ms

css2

css2

45 ms

icon

icon

62 ms

cookies.min.css

cookies.min.css

305 ms

magicstrap.min.css

magicstrap.min.css

777 ms

style.min.css

style.min.css

482 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

28 ms

fancybox.umd.js

fancybox.umd.js

53 ms

fancybox.css

fancybox.css

65 ms

js

js

86 ms

jquery.min.js

jquery.min.js

500 ms

CartSupport.js

CartSupport.js

394 ms

ObjectCreatePolyfill.js

ObjectCreatePolyfill.js

395 ms

SearchForm.js

SearchForm.js

403 ms

WebResource.axd

WebResource.axd

488 ms

ScriptResource.axd

ScriptResource.axd

583 ms

ScriptResource.axd

ScriptResource.axd

499 ms

js

js

575 ms

foot.js

foot.js

516 ms

gtm.js

gtm.js

126 ms

fbevents.js

fbevents.js

127 ms

291 ms

FileHandler.ashx

FileHandler.ashx

290 ms

FileHandler.ashx

FileHandler.ashx

317 ms

FileHandler.ashx

FileHandler.ashx

318 ms

FileHandler.ashx

FileHandler.ashx

318 ms

FileHandler.ashx

FileHandler.ashx

501 ms

FileHandler.ashx

FileHandler.ashx

584 ms

FileHandler.ashx

FileHandler.ashx

416 ms

FileHandler.ashx

FileHandler.ashx

584 ms

FileHandler.ashx

FileHandler.ashx

676 ms

FileHandler.ashx

FileHandler.ashx

583 ms

FileHandler.ashx

FileHandler.ashx

591 ms

FileHandler.ashx

FileHandler.ashx

676 ms

FileHandler.ashx

FileHandler.ashx

790 ms

FileHandler.ashx

FileHandler.ashx

717 ms

FileHandler.ashx

FileHandler.ashx

717 ms

FileHandler.ashx

FileHandler.ashx

809 ms

FileHandler.ashx

FileHandler.ashx

788 ms

FileHandler.ashx

FileHandler.ashx

881 ms

FileHandler.ashx

FileHandler.ashx

812 ms

FileHandler.ashx

FileHandler.ashx

826 ms

FileHandler.ashx

FileHandler.ashx

994 ms

FileHandler.ashx

FileHandler.ashx

1092 ms

FileHandler.ashx

FileHandler.ashx

1351 ms

FileHandler.ashx

FileHandler.ashx

1022 ms

FileHandler.ashx

FileHandler.ashx

1036 ms

FileHandler.ashx

FileHandler.ashx

1091 ms

FileHandler.ashx

FileHandler.ashx

1692 ms

FileHandler.ashx

FileHandler.ashx

1134 ms

FileHandler.ashx

FileHandler.ashx

1137 ms

FileHandler.ashx

FileHandler.ashx

1208 ms

FileHandler.ashx

FileHandler.ashx

1190 ms

FileHandler.ashx

FileHandler.ashx

1251 ms

FileHandler.ashx

FileHandler.ashx

1239 ms

FileHandler.ashx

FileHandler.ashx

1310 ms

FileHandler.ashx

FileHandler.ashx

1272 ms

FileHandler.ashx

FileHandler.ashx

1102 ms

analytics.js

analytics.js

109 ms

destination

destination

109 ms

rc.js

rc.js

760 ms

recorder.js

recorder.js

369 ms

ecmtr-2.4.2.js

ecmtr-2.4.2.js

190 ms

widget.js

widget.js

290 ms

loader.js

loader.js

366 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf

231 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

288 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

289 ms

gok-H7zzDkdnRel8-DQ6KAXJ69wP1tGnf4ZGhUcd.otf

gok-H7zzDkdnRel8-DQ6KAXJ69wP1tGnf4ZGhUcd.otf

312 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

288 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8aX8.ttf

311 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aX8.ttf

287 ms

WnznHAc5bAfYB2QRah7pcpNvOx-pjfJ9SII.ttf

WnznHAc5bAfYB2QRah7pcpNvOx-pjfJ9SII.ttf

365 ms

FileHandler.ashx

FileHandler.ashx

1042 ms

FileHandler.ashx

FileHandler.ashx

1092 ms

FileHandler.ashx

FileHandler.ashx

1130 ms

FileHandler.ashx

FileHandler.ashx

1339 ms

FileHandler.ashx

FileHandler.ashx

1042 ms

collect

collect

182 ms

FileHandler.ashx

FileHandler.ashx

1016 ms

FileHandler.ashx

FileHandler.ashx

930 ms

FileHandler.ashx

FileHandler.ashx

983 ms

FileHandler.ashx

FileHandler.ashx

974 ms

FileHandler.ashx

FileHandler.ashx

1042 ms

collect

collect

71 ms

FileHandler.ashx

FileHandler.ashx

1333 ms

FileHandler.ashx

FileHandler.ashx

999 ms

ga-audiences

ga-audiences

83 ms

FileHandler.ashx

FileHandler.ashx

950 ms

FileHandler.ashx

FileHandler.ashx

1031 ms

FileHandler.ashx

FileHandler.ashx

1171 ms

FileHandler.ashx

FileHandler.ashx

976 ms

FileHandler.ashx

FileHandler.ashx

1056 ms

FileHandler.ashx

FileHandler.ashx

1548 ms

FileHandler.ashx

FileHandler.ashx

1025 ms

FileHandler.ashx

FileHandler.ashx

990 ms

FileHandler.ashx

FileHandler.ashx

967 ms

FileHandler.ashx

FileHandler.ashx

943 ms

FileHandler.ashx

FileHandler.ashx

934 ms

FileHandler.ashx

FileHandler.ashx

1156 ms

FileHandler.ashx

FileHandler.ashx

968 ms

FileHandler.ashx

FileHandler.ashx

945 ms

FileHandler.ashx

FileHandler.ashx

943 ms

FileHandler.ashx

FileHandler.ashx

922 ms

FileHandler.ashx

FileHandler.ashx

953 ms

FileHandler.ashx

FileHandler.ashx

929 ms

FileHandler.ashx

FileHandler.ashx

921 ms

FileHandler.ashx

FileHandler.ashx

900 ms

FileHandler.ashx

FileHandler.ashx

950 ms

FileHandler.ashx

FileHandler.ashx

918 ms

FileHandler.ashx

FileHandler.ashx

924 ms

FileHandler.ashx

FileHandler.ashx

922 ms

FileHandler.ashx

FileHandler.ashx

1128 ms

FileHandler.ashx

FileHandler.ashx

916 ms

FileHandler.ashx

FileHandler.ashx

914 ms

FileHandler.ashx

FileHandler.ashx

879 ms

FileHandler.ashx

FileHandler.ashx

898 ms

FileHandler.ashx

FileHandler.ashx

1182 ms

FileHandler.ashx

FileHandler.ashx

897 ms

FileHandler.ashx

FileHandler.ashx

845 ms

FileHandler.ashx

FileHandler.ashx

834 ms

FileHandler.ashx

FileHandler.ashx

866 ms

FileHandler.ashx

FileHandler.ashx

904 ms

FileHandler.ashx

FileHandler.ashx

908 ms

858 ms

loader.png

loader.png

887 ms

Accessibility Review

firotour.cz accessibility score

73

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.

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

Form elements do not have associated labels

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

firotour.cz best practices score

83

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

Page has valid source maps

SEO Factors

firotour.cz SEO score

82

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

High

Tap targets are not sized appropriately

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

firotour.cz

Open Graph data is detected on the main page of Firotour. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: