Tools & Wizards About Us
podat.cz screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 45

    SEO

    Google-friendlier than
    18% of websites

podat.cz

Page Load Speed

2.8 sec in total

First Response

1.1 sec

Resources Loaded

1.6 sec

Page Rendered

146 ms

podat.cz screenshot

About Website

Welcome to podat.cz homepage info - get ready to check Podat best content right away, or after learning these important things about podat.cz

podat.cz vložit inzrerát bez registrace inzerce .

Visit podat.cz

Key Findings

We analyzed Podat.cz page load time and found that the first response time was 1.1 sec and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

podat.cz performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value1.24

1/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

podat.cz

1070 ms

stylehlavni1.css

200 ms

suggest.js

204 ms

favorite.js

207 ms

eucookie.js

205 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Podat.cz, 17% (6 requests) were made to Inzeratyzdarma.cz and 3% (1 request) were made to Chart.apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Podat.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.6 kB (32%)

Content Size

148.0 kB

After Optimization

100.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Podat.cz main page is 148.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. 15% of websites need less resources to load. Images take 98.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 17.5 kB

  • Original 21.9 kB
  • After minification 19.8 kB
  • After compression 4.4 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 17.5 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 7.7 kB

  • Original 98.5 kB
  • After minification 90.8 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. Podat images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 13.7 kB

  • Original 17.7 kB
  • After minification 9.3 kB
  • After compression 4.0 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 13.7 kB or 78% of the original size.

CSS Optimization

-87%

Potential reduce by 8.7 kB

  • Original 9.9 kB
  • After minification 5.2 kB
  • After compression 1.3 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. Podat.cz needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (9%)

Requests Now

34

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Podat. 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

podat.cz

podat.cz

1070 ms

stylehlavni1.css

stylehlavni1.css

200 ms

suggest.js

suggest.js

204 ms

favorite.js

favorite.js

207 ms

eucookie.js

eucookie.js

205 ms

search_input3.js

search_input3.js

215 ms

android.gif

android.gif

330 ms

fac.bmp

fac.bmp

330 ms

seznam.jpg

seznam.jpg

334 ms

chart

chart

104 ms

autobazar.jpg

autobazar.jpg

197 ms

motorky.jpg

motorky.jpg

201 ms

nakladak.jpg

nakladak.jpg

203 ms

stroje.jpg

stroje.jpg

203 ms

mobily.jpg

mobily.jpg

210 ms

audio-video-foto.jpg

audio-video-foto.jpg

392 ms

pocitace.jpg

pocitace.jpg

402 ms

nemovitosti-reality.jpg

nemovitosti-reality.jpg

405 ms

obleceni.jpg

obleceni.jpg

410 ms

naradi.jpg

naradi.jpg

410 ms

ostatni.jpg

ostatni.jpg

463 ms

zahrada.jpg

zahrada.jpg

591 ms

zvirata.jpg

zvirata.jpg

602 ms

hobby.jpg

hobby.jpg

604 ms

seznamka.jpg

seznamka.jpg

610 ms

sluzby.jpg

sluzby.jpg

619 ms

cestovani.jpg

cestovani.jpg

671 ms

pujcky.jpg

pujcky.jpg

792 ms

twitr.jpg

twitr.jpg

310 ms

plus.jpg

plus.jpg

311 ms

rss2.jpg

rss2.jpg

310 ms

vyziva.jpg

vyziva.jpg

710 ms

prace.jpg

prace.jpg

712 ms

zdarma.jpg

zdarma.jpg

719 ms

dot.asp

dot.asp

207 ms

Accessibility Review

podat.cz accessibility score

53

Accessibility Issues

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

Document doesn't have a <title> element

High

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

podat.cz best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

podat.cz SEO score

45

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1250

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Podat.cz can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Podat.cz 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

podat.cz

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