Tools & Wizards About Us
kanoe.sk screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

kanoe.sk

Kanoe.sk - rýchlostná kanoistika na Slovensku

Page Load Speed

4.8 sec in total

First Response

428 ms

Resources Loaded

4.2 sec

Page Rendered

233 ms

kanoe.sk screenshot

About Website

Welcome to kanoe.sk homepage info - get ready to check Kanoe best content for Slovakia right away, or after learning these important things about kanoe.sk

Slovenská kanoistika z každého uhla a omnoho viac.

Visit kanoe.sk

Key Findings

We analyzed Kanoe.sk page load time and found that the first response time was 428 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

kanoe.sk performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

kanoe.sk

428 ms

www.kanoe.sk

1353 ms

kanoe.css

320 ms

script.js

214 ms

show_ads.js

4 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 38% of them (26 requests) were addressed to the original Kanoe.sk, 21% (14 requests) were made to Scontent.xx.fbcdn.net and 12% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Kanoe.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.8 kB (22%)

Content Size

257.0 kB

After Optimization

199.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kanoe.sk main page is 257.0 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. 35% of websites need less resources to load. Images take 155.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 48.5 kB

  • Original 62.3 kB
  • After minification 62.0 kB
  • After compression 13.7 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 48.5 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 3.6 kB

  • Original 155.2 kB
  • After minification 151.6 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. Kanoe images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.4 kB

  • Original 34.5 kB
  • After minification 33.8 kB
  • After compression 33.1 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.

CSS Optimization

-85%

Potential reduce by 4.3 kB

  • Original 5.0 kB
  • After minification 3.9 kB
  • After compression 777 B

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. Kanoe.sk needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (39%)

Requests Now

64

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kanoe.sk

kanoe.sk

428 ms

www.kanoe.sk

www.kanoe.sk

1353 ms

kanoe.css

kanoe.css

320 ms

script.js

script.js

214 ms

show_ads.js

show_ads.js

4 ms

marek.gif

marek.gif

876 ms

uvod_top.jpg

uvod_top.jpg

532 ms

percento2.jpg

percento2.jpg

319 ms

rr_145.gif

rr_145.gif

304 ms

nic.gif

nic.gif

216 ms

sita_kanoe_logo.jpg

sita_kanoe_logo.jpg

312 ms

kanoe_google.jpg

kanoe_google.jpg

323 ms

pda_468.jpg

pda_468.jpg

615 ms

enel.gif

enel.gif

415 ms

ca-pub-7110175428108273.js

ca-pub-7110175428108273.js

128 ms

zrt_lookup.html

zrt_lookup.html

48 ms

show_ads_impl.js

show_ads_impl.js

69 ms

online.php

online.php

426 ms

fb_dole.php

fb_dole.php

382 ms

ads

ads

205 ms

percento.jpg

percento.jpg

542 ms

kanoe_sponzor2.jpg

kanoe_sponzor2.jpg

380 ms

nyna.gif

nyna.gif

390 ms

sc88.gif

sc88.gif

619 ms

uvod_bottom.jpg

uvod_bottom.jpg

697 ms

osd.js

osd.js

7 ms

menu_nbs_data.php

menu_nbs_data.php

535 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

24 ms

ads

ads

137 ms

kanoe_static.html

kanoe_static.html

440 ms

kanoe_static.html

kanoe_static.html

433 ms

sk_SK

sk_SK

207 ms

162 ms

245 ms

xd_arbiter.php

xd_arbiter.php

212 ms

xd_arbiter.php

xd_arbiter.php

419 ms

247 ms

us.gif

us.gif

113 ms

cz.gif

cz.gif

112 ms

gb.gif

gb.gif

112 ms

hu.gif

hu.gif

107 ms

pl.gif

pl.gif

176 ms

getbanner.php

getbanner.php

241 ms

fan.php

fan.php

240 ms

kanoe_print.css

kanoe_print.css

108 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

284 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

352 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

486 ms

hHAUS9q05ns.js

hHAUS9q05ns.js

623 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

508 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

508 ms

482012_448020928554005_995953842_n.jpg

482012_448020928554005_995953842_n.jpg

431 ms

25862_114791931876908_4904180_n.jpg

25862_114791931876908_4904180_n.jpg

556 ms

12235041_1067050026660832_1708935305213022389_n.jpg

12235041_1067050026660832_1708935305213022389_n.jpg

702 ms

1461197_586813391446105_8168927120905638789_n.jpg

1461197_586813391446105_8168927120905638789_n.jpg

633 ms

12548861_159523954423440_3219573809732102447_n.jpg

12548861_159523954423440_3219573809732102447_n.jpg

635 ms

72836_115776585261171_345842490_n.jpg

72836_115776585261171_345842490_n.jpg

706 ms

10479153_298333306994944_2555229307689827758_n.jpg

10479153_298333306994944_2555229307689827758_n.jpg

656 ms

11692661_1465278983786980_2024257495322057722_n.jpg

11692661_1465278983786980_2024257495322057722_n.jpg

818 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

700 ms

10383041_836267446440982_2147606068764057520_n.jpg

10383041_836267446440982_2147606068764057520_n.jpg

772 ms

1379841_10150004552801901_469209496895221757_n.jpg

1379841_10150004552801901_469209496895221757_n.jpg

722 ms

1927646_126292094414178_704825020282243683_n.jpg

1927646_126292094414178_704825020282243683_n.jpg

767 ms

12745647_1001374393262531_95069623636970173_n.jpg

12745647_1001374393262531_95069623636970173_n.jpg

770 ms

12027_562198470481366_1302517997_n.jpg

12027_562198470481366_1302517997_n.jpg

846 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

77 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

76 ms

Accessibility Review

kanoe.sk accessibility score

76

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

ARIA progressbar elements do not have accessible names.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

kanoe.sk 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

Missing source maps for large first-party JavaScript

SEO Factors

kanoe.sk SEO score

100

Search Engine Optimization Advices

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

    SK

  • Language Claimed

    SK

  • Encoding

    WINDOWS-1250

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kanoe.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Kanoe.sk main page’s claimed encoding is windows-1250. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

kanoe.sk

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