3.9 sec in total
933 ms
2.7 sec
226 ms
Visit recko.name now to see the best up-to-date Recko content for Czech Republic and also check out these interesting facts you probably never knew about recko.name
Inspirujte se cestopisy a fotogaleriemi a naplánujte poznávání této krásné země. Zeptejte se v diskuzním fóru, přečtěte recenze hotelů, restaurací, pláží, půjčoven aut, a mnohem více.
Visit recko.nameWe analyzed Recko.name page load time and found that the first response time was 933 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
recko.name performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value2.8 s
83/100
25%
Value5.0 s
63/100
10%
Value470 ms
60/100
30%
Value0.076
95/100
15%
Value7.4 s
48/100
10%
933 ms
309 ms
208 ms
209 ms
210 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 99% of them (73 requests) were addressed to the original Recko.name, 1% (1 request) were made to Toplist.cz. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Recko.name.
Page size can be reduced by 375.6 kB (49%)
771.1 kB
395.5 kB
In fact, the total size of Recko.name main page is 771.1 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. 20% of websites need less resources to load. Javascripts take 362.4 kB which makes up the majority of the site volume.
Potential reduce by 39.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. 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 39.3 kB or 83% of the original size.
Potential reduce by 30.4 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. Recko images are well optimized though.
Potential reduce by 262.6 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 262.6 kB or 72% of the original size.
Potential reduce by 43.4 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. Recko.name needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 82% of the original size.
Number of requests can be reduced by 36 (49%)
73
37
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
recko.name
933 ms
main45.css
309 ms
stars1.css
208 ms
activemenu.css
209 ms
tooltipster1.css
210 ms
datepicker.css
211 ms
autocomplete.css
304 ms
jquery-1.7.1.min.js
622 ms
jquery-ui-1.8.11.custom.min.js
825 ms
jquery-tooltipster.min.js
311 ms
jquery-active-menu.js
312 ms
jquery-datepicker.js
406 ms
jquery-autocomplete.min.js
408 ms
jquery-seting.js
412 ms
datepicker.js
414 ms
ajax.js
509 ms
main1.js
510 ms
formPlus.js
516 ms
hoverIntent.js
516 ms
index.js
611 ms
background.png
107 ms
tops_1_01.jpg
307 ms
cestujeme.png
105 ms
turecko.png
108 ms
load.gif
105 ms
submit_Big_hover_3.png
106 ms
submit_Smal_hover_3.png
207 ms
submit_Litl_hover_3.png
208 ms
img_bg_focus.png
209 ms
tops_1_03.jpg
209 ms
top_1_04.jpg
210 ms
top_1_05.jpg
309 ms
tops_1_06.jpg
311 ms
tops_1_07.jpg
311 ms
tops_1_08.jpg
312 ms
tops_1_09.jpg
314 ms
tops_1_10.jpg
409 ms
tops_1_11.jpg
410 ms
tops_1_12.jpg
412 ms
n_m1t.jpg
413 ms
n_prihlaseni.png
413 ms
bg_login.png
414 ms
bg_jmeno.png
509 ms
bg_heslo.png
512 ms
thumbLogin.png
516 ms
MC.gif
514 ms
n_m1b.jpg
516 ms
alex_left.png
518 ms
invia_first_left_2016.png
612 ms
n_m2t.jpg
613 ms
n_cestopisy.png
616 ms
n_thumbNew.png
617 ms
n_m2b.jpg
618 ms
n_dovolena16.png
621 ms
n_m3t.jpg
713 ms
count.asp
215 ms
n_informace.png
676 ms
rss.png
622 ms
n_m3b.jpg
621 ms
n_pratelweby.png
622 ms
n_2cloud.png
624 ms
n_3cloud.png
715 ms
n_4cloud_modrain.png
632 ms
mapkaGR.png
724 ms
n_1cloud.png
632 ms
4cloud.png
621 ms
bg_kat1.png
624 ms
n_bgBoxTop.png
721 ms
bgBoxEnd.png
624 ms
vtt16.png
731 ms
marted16_2.jpg
627 ms
invia_first.jpg
835 ms
arrows-ffffff.png
720 ms
shadow.png
628 ms
recko.name accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
recko.name 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
recko.name SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
CS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recko.name can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Recko.name 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.
recko.name
Open Graph description is not detected on the main page of Recko. 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: