Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

woko.cz

Služba Woko.cz, která sledovala změny na webech, skončila - Lupa.cz

Page Load Speed

6.8 sec in total

First Response

512 ms

Resources Loaded

5.9 sec

Page Rendered

358 ms

woko.cz screenshot

About Website

Visit woko.cz now to see the best up-to-date Woko content and also check out these interesting facts you probably never knew about woko.cz

Svět IT, dění na trhu, bezpečnost na internetu, připojení k internetu, mobilní internet, online média a reklama, cloudové služby.

Visit woko.cz

Key Findings

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

Performance Metrics

woko.cz performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value15.4 s

0/100

10%

TBT (Total Blocking Time)

Value2,920 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.239

52/100

15%

TTI (Time to Interactive)

Value33.3 s

0/100

10%

Network Requests Diagram

woko.cz

512 ms

1738 ms

gtm.js

56 ms

webfont.js

30 ms

css

45 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Woko.cz, 27% (26 requests) were made to F.lupa.cz and 17% (17 requests) were made to I.iinfo.cz. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Lupa.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (47%)

Content Size

2.3 MB

After Optimization

1.2 MB

In fact, the total size of Woko.cz main page is 2.3 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 662.3 kB

  • Original 928.6 kB
  • After minification 926.9 kB
  • After compression 266.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 662.3 kB or 71% of the original size.

Image Optimization

-12%

Potential reduce by 13.7 kB

  • Original 117.3 kB
  • After minification 103.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. Obviously, Woko needs image optimization as it can save up to 13.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-31%

Potential reduce by 357.0 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 783.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 357.0 kB or 31% of the original size.

CSS Optimization

-26%

Potential reduce by 18.0 kB

  • Original 70.0 kB
  • After minification 70.0 kB
  • After compression 52.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. Woko.cz needs all CSS files to be minified and compressed as it can save up to 18.0 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (71%)

Requests Now

90

After Optimization

26

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

Accessibility Review

woko.cz accessibility score

84

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

woko.cz best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

woko.cz SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

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