3.8 sec in total
573 ms
2.6 sec
627 ms
Click here to check amazing FARE content for Czech Republic. Otherwise, check out these important facts you probably never knew about fare.cz
FARE je český výrobce kvalitní a zdravé obuvi, zaměřuje se na dětské boty, ale také chlapeckou, dívčí, dámskou a pánskou obuv. Všechny boty skladem. Rychlé odeslání, skvělý zákaznický servis, ušetřete...
Visit fare.czWe analyzed Fare.cz page load time and found that the first response time was 573 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fare.cz performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value27.9 s
0/100
25%
Value14.8 s
1/100
10%
Value4,670 ms
0/100
30%
Value0.303
39/100
15%
Value24.5 s
0/100
10%
573 ms
203 ms
313 ms
227 ms
228 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 80% of them (77 requests) were addressed to the original Fare.cz, 13% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Fare.cz.
Page size can be reduced by 999.3 kB (30%)
3.4 MB
2.4 MB
In fact, the total size of Fare.cz main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 61.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 9.6 kB, which is 13% 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 61.5 kB or 85% of the original size.
Potential reduce by 262.1 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. Obviously, FARE needs image optimization as it can save up to 262.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 413.7 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 413.7 kB or 73% of the original size.
Potential reduce by 262.0 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. Fare.cz needs all CSS files to be minified and compressed as it can save up to 262.0 kB or 84% of the original size.
Number of requests can be reduced by 29 (36%)
80
51
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FARE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fare.cz
573 ms
bootstrap.min.css
203 ms
app.css
313 ms
media.css
227 ms
jquery.fancybox.css
228 ms
jquery-ui.css
229 ms
font-awesome.css
237 ms
jquery.suggest.css
299 ms
css
67 ms
css
79 ms
jquery-1.9.1.min.js
14 ms
bootstrap.min.js
341 ms
jquery.min.js
423 ms
jquery.json.suggest.js
348 ms
jquery.fancybox.pack.js
348 ms
jquery.nette.js
391 ms
jquery.ajaxform.js
407 ms
jquery.qtip.js
412 ms
netteForms.js
438 ms
jquery.ui.js
647 ms
jquery.flow.js
486 ms
jquery.sticky.js
509 ms
responsiveslides.js
509 ms
modernizr.js
519 ms
owl.carousel.min.js
525 ms
jquery.elevateZoom-3.0.8.min.js
584 ms
jquery.bxslider-rahisified.min.js
615 ms
scripts.js
616 ms
jquery.bxslider.css
622 ms
jquery.pageless.js
627 ms
jcarousel.css
717 ms
jquery.jcarousel.min.js
720 ms
d03oiboZGiaNuMDvH253Ci3USBnSvpkopQaUR-2r7iU.ttf
85 ms
G28Ny31cr5orMqEQy6ljt7OLyRJkM5aLlPlkJMOAyH0.ttf
86 ms
1.png
258 ms
2.png
258 ms
logo.png
252 ms
nakupny-vozik.png
254 ms
1_23.jpg
651 ms
1_38.jpg
553 ms
1_37.jpg
833 ms
1_36.jpg
853 ms
icon-1.png
396 ms
icon-2.png
367 ms
icon-3.png
449 ms
241676_1498_th.jpg
476 ms
241811_2350_th.jpg
649 ms
241949_1697_th.jpg
577 ms
242001_1437_th.jpg
652 ms
242077_1579_th.jpg
680 ms
242408_1527_th.jpg
750 ms
242581_1900_th.jpg
750 ms
242588_1908_th.jpg
755 ms
242594_1963_th.jpg
781 ms
242596_1965_th.jpg
851 ms
242672_2108_th.jpg
853 ms
242690_2150_th.jpg
856 ms
242725_2197_th.jpg
883 ms
242820_2302_th.jpg
921 ms
242862_2367_th.jpg
945 ms
242874_2396_th.jpg
947 ms
bottom-icon-1.png
963 ms
bottom-icon-2.png
964 ms
bottom-icon-3.png
982 ms
bottom-icon-4.png
1019 ms
sdk.js
12 ms
menu-bg.png
1037 ms
prihlasenie-icon.png
1038 ms
lupa.png
1042 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
172 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
230 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
237 ms
IgZJs4-7SA1XX_edsoXWog.ttf
237 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
207 ms
321 ms
icon-bg.jpg
958 ms
gray.png
983 ms
xd_arbiter.php
89 ms
xd_arbiter.php
137 ms
O4NhV7_qs9r9seTo7fnsVKCWcynf_cDxXwCLxiixG1c.ttf
119 ms
PRmiXeptR36kaC0GEAetxi9-WlPSxbfiI49GsXo3q0g.ttf
126 ms
PRmiXeptR36kaC0GEAetxpZ7xm-Bj30Bj2KNdXDzSZg.ttf
120 ms
PRmiXeptR36kaC0GEAetxne1Pd76Vl7zRpE7NLJQ7XU.ttf
120 ms
PRmiXeptR36kaC0GEAetxg89PwPrYLaRFJ-HNCU9NbA.ttf
119 ms
fontawesome-webfont.woff
879 ms
6.jpg
913 ms
5.jpg
910 ms
3.jpg
887 ms
kontakt-pero.png
778 ms
bottom-bg.png
801 ms
bx_loader.gif
776 ms
btn-slider-prev.png
780 ms
btn-slider-next.png
709 ms
slider-home-left.png
688 ms
slider-home-right.png
627 ms
spinner.gif
649 ms
fare.cz accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
fare.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fare.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 Fare.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 Fare.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.
fare.cz
Open Graph description is not detected on the main page of FARE. 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: