Tools & Wizards About Us
trafika.pl screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

trafika.pl

TRAFIKA.pl ™ - Kawa, Papierosy, Tytoń do papierosów - Sklep tytoniowy

Page Load Speed

4.3 sec in total

First Response

1.2 sec

Resources Loaded

2.9 sec

Page Rendered

274 ms

trafika.pl screenshot

About Website

Visit trafika.pl now to see the best up-to-date TRAFIKA content for Poland and also check out these interesting facts you probably never knew about trafika.pl

TRAFIKA.pl ™ - Sklep tytoniowy, sprzedaż tanich papierosów i innych wyrobów tytoniowych. Największy wybór Kawy w internecie

Visit trafika.pl

Key Findings

We analyzed Trafika.pl page load time and found that the first response time was 1.2 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

trafika.pl performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.trafika.pl

1174 ms

widget.css

197 ms

ruch.css

115 ms

theme-6e630f362.css

574 ms

head-b98a83361.js

328 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Trafika.pl, 12% (2 requests) were made to Ruch-osm.sysadvisors.pl and 6% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Trafika.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.2 kB (28%)

Content Size

560.0 kB

After Optimization

405.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trafika.pl main page is 560.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. 30% of websites need less resources to load. Javascripts take 252.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 150.9 kB

  • Original 176.2 kB
  • After minification 137.8 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 38.4 kB, which is 22% 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 150.9 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.9 kB
  • After minification 5.9 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. TRAFIKA images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 786 B

  • Original 252.1 kB
  • After minification 252.1 kB
  • After compression 251.4 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

-2%

Potential reduce by 2.5 kB

  • Original 125.7 kB
  • After minification 125.7 kB
  • After compression 123.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. Trafika.pl has all CSS files already compressed.

Requests Breakdown

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

Requests Now

14

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.trafika.pl

www.trafika.pl

1174 ms

widget.css

widget.css

197 ms

ruch.css

ruch.css

115 ms

theme-6e630f362.css

theme-6e630f362.css

574 ms

head-b98a83361.js

head-b98a83361.js

328 ms

bottom-53a9ab361.js

bottom-53a9ab361.js

874 ms

cart.js

cart.js

341 ms

cart17.js

cart17.js

346 ms

widget.js

widget.js

362 ms

slick-theme.css

slick-theme.css

352 ms

slick.min.js

slick.min.js

434 ms

trafika-logo-17176565611.jpg

trafika-logo-17176565611.jpg

141 ms

fbevents.js

fbevents.js

102 ms

placeholder_icon.svg

placeholder_icon.svg

122 ms

icon-cart.svg

icon-cart.svg

120 ms

GILROY-MEDIUM.TTF

GILROY-MEDIUM.TTF

570 ms

GILROY-BOLD.TTF

GILROY-BOLD.TTF

595 ms

Accessibility Review

trafika.pl accessibility score

86

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

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

trafika.pl 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

trafika.pl SEO score

92

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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trafika.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Trafika.pl 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

trafika.pl

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