Tools & Wizards About Us

Report Summary

  • 0

    Performance

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

traffic.cz

JIP-POTRAVINY.CZ | JIP východočeská a.s. ze skupiny JIP

Page Load Speed

1.9 sec in total

First Response

406 ms

Resources Loaded

1.3 sec

Page Rendered

188 ms

About Website

Click here to check amazing Traffic content. Otherwise, check out these important facts you probably never knew about traffic.cz

Nabízíme velkoobchodní on-line nákup potravin. V okolí Pardubic Vám přivezeme nápoje a potraviny do Vašeho maloobchodu, jídelny, restaurace nebo čerpací stanice.

Visit traffic.cz

Key Findings

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

Performance Metrics

traffic.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)

Value0.093

91/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

traffic.cz

406 ms

style.css

102 ms

analytics.js

14 ms

like.php

416 ms

traffic-logo.jpg

504 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 50% of them (6 requests) were addressed to the original Traffic.cz, 17% (2 requests) were made to Google-analytics.com and 17% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (788 ms) belongs to the original domain Traffic.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.1 kB (2%)

Content Size

486.6 kB

After Optimization

475.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Traffic.cz main page is 486.6 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 453.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.4 kB

  • Original 11.0 kB
  • After minification 9.7 kB
  • After compression 3.6 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 1.3 kB, which is 12% 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 7.4 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 3.5 kB

  • Original 453.8 kB
  • After minification 450.3 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. Traffic images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

-17%

Potential reduce by 149 B

  • Original 889 B
  • After minification 889 B
  • After compression 740 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. Traffic.cz needs all CSS files to be minified and compressed as it can save up to 149 B or 17% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Traffic. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

traffic.cz accessibility score

80

Accessibility Issues

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.

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

traffic.cz best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

traffic.cz SEO score

71

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

    N/A

  • Encoding

    UTF-8

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