Tools & Wizards About Us
k-report.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

k-report.net

K-REPORT ?esk? dopravn? server

Page Load Speed

4.3 sec in total

First Response

216 ms

Resources Loaded

3.8 sec

Page Rendered

250 ms

k-report.net screenshot

About Website

Welcome to k-report.net homepage info - get ready to check K REPORT best content for Czech Republic right away, or after learning these important things about k-report.net

Server pro p??tele ?eleznice, MHD, a dopravn? problematiky obecn?

Visit k-report.net

Key Findings

We analyzed K-report.net page load time and found that the first response time was 216 ms and then it took 4 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

k-report.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

k-report.net

216 ms

www.k-report.net

437 ms

style.css

348 ms

adsbygoogle.js

108 ms

tc-string-parse.js

346 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original K-report.net, 2% (1 request) were made to Pagead2.googlesyndication.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain K-report.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.9 kB (13%)

Content Size

260.0 kB

After Optimization

225.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of K-report.net main page is 260.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. 25% of websites need less resources to load. Images take 133.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 25.1 kB

  • Original 34.0 kB
  • After minification 26.7 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 7.3 kB, which is 21% 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 25.1 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 8.1 kB

  • Original 133.7 kB
  • After minification 125.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. K REPORT images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 516 B

  • Original 80.0 kB
  • After minification 80.0 kB
  • After compression 79.5 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

-10%

Potential reduce by 1.2 kB

  • Original 12.4 kB
  • After minification 12.4 kB
  • After compression 11.2 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. K-report.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

47

After Optimization

34

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

k-report.net

k-report.net

216 ms

www.k-report.net

www.k-report.net

437 ms

style.css

style.css

348 ms

adsbygoogle.js

adsbygoogle.js

108 ms

tc-string-parse.js

tc-string-parse.js

346 ms

dffunkce4.js

dffunkce4.js

447 ms

js

js

72 ms

pozadi11.gif

pozadi11.gif

305 ms

pozadi11.jpg

pozadi11.jpg

305 ms

pozadi13.gif

pozadi13.gif

306 ms

pozadi12.gif

pozadi12.gif

306 ms

logo10.gif

logo10.gif

304 ms

logo_tisk.gif

logo_tisk.gif

307 ms

pozadi15.gif

pozadi15.gif

607 ms

pozadi16.gif

pozadi16.gif

607 ms

pozadi14.gif

pozadi14.gif

607 ms

pozadi25.gif

pozadi25.gif

608 ms

pozadi26.gif

pozadi26.gif

608 ms

pozadi22.gif

pozadi22.gif

608 ms

pozadi27.gif

pozadi27.gif

908 ms

pozadi28.gif

pozadi28.gif

908 ms

1132349.jpg

1132349.jpg

1065 ms

1533209.jpg

1533209.jpg

995 ms

768450.jpg

768450.jpg

964 ms

1422965.jpg

1422965.jpg

1028 ms

carbosped.gif

carbosped.gif

1209 ms

spedica.jpg

spedica.jpg

1210 ms

rss.gif

rss.gif

1265 ms

pozadi29.gif

pozadi29.gif

1297 ms

titulni-aktuality-1776.jpg

titulni-aktuality-1776.jpg

1330 ms

titulni-aktuality-1775.jpg

titulni-aktuality-1775.jpg

1366 ms

titulni-aktuality-1774.jpg

titulni-aktuality-1774.jpg

1510 ms

titulni-aktuality-1773.jpg

titulni-aktuality-1773.jpg

1511 ms

titulni-aktuality-1772.jpg

titulni-aktuality-1772.jpg

1568 ms

titulni-clanky-404.jpg

titulni-clanky-404.jpg

1598 ms

titulni-clanky-403.jpg

titulni-clanky-403.jpg

1631 ms

titulni-clanky-402.jpg

titulni-clanky-402.jpg

1667 ms

titulni-clanky-400.jpg

titulni-clanky-400.jpg

1812 ms

titulni-clanky-397.jpg

titulni-clanky-397.jpg

1912 ms

titulni-clanky-396.JPG

titulni-clanky-396.JPG

1869 ms

titulni-clanky-395.jpg

titulni-clanky-395.jpg

1899 ms

titulni-clanky-394.jpg

titulni-clanky-394.jpg

1933 ms

titulni-clanky-393.jpg

titulni-clanky-393.jpg

1918 ms

titulni-clanky-391.jpg

titulni-clanky-391.jpg

1814 ms

pozadi17.gif

pozadi17.gif

1870 ms

pozadi19.gif

pozadi19.gif

1900 ms

pozadi18.gif

pozadi18.gif

1912 ms

style1.css

style1.css

161 ms

style_tisk.css

style_tisk.css

304 ms

Accessibility Review

k-report.net accessibility score

87

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

k-report.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

k-report.net SEO score

91

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

    WINDOWS-1250

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise K-report.net 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 K-report.net 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

k-report.net

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