Access pivoteka.cz. Pivotéka.cz - pivo, pivní chlazení, potřeby pro vaření piva

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.251

49/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

pivoteka.cz

395 ms

www.pivoteka.cz

986 ms

css

51 ms

style.min.css

300 ms

js

73 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 55% of them (62 requests) were addressed to the original Pivoteka.cz, 5% (6 requests) were made to Api.mapy.cz and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Pivoteka.cz.

Content Size

9.2 MB

After Optimization

7.0 MB

In fact, the total size of Pivoteka.cz main page is 9.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 133.9 kB

Original 152.8 kB
After minification 109.5 kB
After compression 18.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 43.2 kB, which is 28% 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 133.9 kB or 88% of the original size.

Image Optimization

-24%

Potential reduce by 2.0 MB

Original 8.3 MB
After minification 6.2 MB

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, Pivote Ka needs image optimization as it can save up to 2.0 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 37.6 kB

Original 692.8 kB
After minification 692.8 kB
After compression 655.2 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

-1%

Potential reduce by 760 B

Original 98.4 kB
After minification 98.4 kB
After compression 97.7 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. Pivoteka.cz has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Document uses legible font sizes

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

pivoteka.cz

Open Graph data is detected on the main page of Pivote Ka. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Pivotéka.cz - pivo, pivní chlazení, potřeby pro vaření piva | PIVOTÉKA s.r.o.

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

pivoteka.cz

www.pivoteka.cz

css

style.min.css

js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

pivoteka.cz

www.pivoteka.cz

css

style.min.css

js

loader.js

cc-gtm.js

api.js

script.min.js

virtual-key.js

smap-jak.js

config.js

cs.js

smap-jak.css

gtm.js

cz.svg

pivoteka-logo-svg.svg

10-sada-pivo-baner.png

15-pygmy.png

44-poukaz.jpg

24-maxipet.png

39-slad.png

29-no-change.png.png

31-BrewZillaGen4-65-02.png

36-kyvety.png

47-sladovka-admin-product-large.jpg.png

4-bg-green.png

4-domaci-vyroba-piva-1.png

5-bg-yellow.png

5-vycepni-technika.png

6-bg-brown.png

6-rumoteka.png

7-bg-red.png

7-pivo-cider-limo.png

22-bg-banner-kufriky.png

22-baner-degusta.png

23-bg-banner-ostatni.png

23-img-banner-ostatni.png

503911-product-preview.jpg

essox.png

503912-product-preview.jpg

503906-product-preview.jpg

503904-product-preview.jpg