Tools & Wizards About Us
topone.cz screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

topone.cz

Topone.cz consulting s.r.o

Page Load Speed

4.7 sec in total

First Response

468 ms

Resources Loaded

4 sec

Page Rendered

251 ms

topone.cz screenshot

About Website

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

Visit topone.cz

Key Findings

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

Performance Metrics

topone.cz performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

www.topone.cz

468 ms

style.css

122 ms

jquery-1.5.2.min.js

352 ms

global.js

226 ms

ga.js

62 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 94% of them (33 requests) were addressed to the original Topone.cz, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Topone.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.0 kB (19%)

Content Size

457.1 kB

After Optimization

372.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-65%

Potential reduce by 6.5 kB

  • Original 9.9 kB
  • After minification 9.2 kB
  • After compression 3.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 6.5 kB or 65% of the original size.

Image Optimization

-4%

Potential reduce by 11.9 kB

  • Original 329.5 kB
  • After minification 317.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. Topone images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 56.5 kB

  • Original 104.1 kB
  • After minification 103.8 kB
  • After compression 47.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 56.5 kB or 54% of the original size.

CSS Optimization

-75%

Potential reduce by 10.1 kB

  • Original 13.5 kB
  • After minification 12.2 kB
  • After compression 3.4 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. Topone.cz needs all CSS files to be minified and compressed as it can save up to 10.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (41%)

Requests Now

32

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.topone.cz

www.topone.cz

468 ms

style.css

style.css

122 ms

jquery-1.5.2.min.js

jquery-1.5.2.min.js

352 ms

global.js

global.js

226 ms

ga.js

ga.js

62 ms

body.jpg

body.jpg

115 ms

top-line.png

top-line.png

137 ms

logo.png

logo.png

124 ms

nav-bg.jpg

nav-bg.jpg

224 ms

nav-active-first.png

nav-active-first.png

243 ms

nav-li.png

nav-li.png

249 ms

site-search.png

site-search.png

228 ms

search-btn.png

search-btn.png

232 ms

nav-corner.jpg

nav-corner.jpg

248 ms

prologue-bg.jpg

prologue-bg.jpg

337 ms

prologue-li.png

prologue-li.png

338 ms

prologue-deco.jpg

prologue-deco.jpg

445 ms

prologue-shadow.jpg

prologue-shadow.jpg

352 ms

box-bg.png

box-bg.png

353 ms

box-li.png

box-li.png

367 ms

box-more.jpg

box-more.jpg

449 ms

box-deco.png

box-deco.png

454 ms

box-corner.png

box-corner.png

463 ms

info-line.png

info-line.png

464 ms

info-ico.png

info-ico.png

488 ms

photo-bg.png

photo-bg.png

556 ms

airstop-207x136.png

airstop-207x136.png

777 ms

ipojistenicz1.png

ipojistenicz1.png

1205 ms

col-side-bg.png

col-side-bg.png

579 ms

dictionary.png

dictionary.png

573 ms

vcard.png

vcard.png

638 ms

aller_bd-webfont.woff

aller_bd-webfont.woff

776 ms

aller_rg-webfont.woff

aller_rg-webfont.woff

784 ms

__utm.gif

__utm.gif

12 ms

print.css

print.css

111 ms

Accessibility Review

topone.cz accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

SEO Factors

topone.cz SEO score

91

Search Engine Optimization Advices

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

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

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

topone.cz

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