Tools & Wizards About Us
tempo-oopp.cz screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

tempo-oopp.cz

Úvod | Tempo O.O.P.P. spol. s.r.o.

Page Load Speed

3.6 sec in total

First Response

356 ms

Resources Loaded

3 sec

Page Rendered

249 ms

tempo-oopp.cz screenshot

About Website

Welcome to tempo-oopp.cz homepage info - get ready to check Tempo O P best content right away, or after learning these important things about tempo-oopp.cz

Úvod

Visit tempo-oopp.cz

Key Findings

We analyzed Tempo-oopp.cz page load time and found that the first response time was 356 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tempo-oopp.cz performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

tempo-oopp.cz

356 ms

www.tempo-oopp.cz

1079 ms

format.css

132 ms

boxes.css

243 ms

modules.css

247 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 56% of them (57 requests) were addressed to the original Tempo-oopp.cz, 13% (13 requests) were made to Maps.googleapis.com and 11% (11 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Tempo-oopp.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 693.5 kB (61%)

Content Size

1.1 MB

After Optimization

443.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tempo-oopp.cz main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 861.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.4 kB

  • Original 36.7 kB
  • After minification 34.3 kB
  • After compression 8.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. 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 28.4 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 6.3 kB

  • Original 166.2 kB
  • After minification 159.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. Tempo O P images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 595.6 kB

  • Original 861.3 kB
  • After minification 799.4 kB
  • After compression 265.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 595.6 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 63.2 kB

  • Original 73.3 kB
  • After minification 45.9 kB
  • After compression 10.1 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. Tempo-oopp.cz needs all CSS files to be minified and compressed as it can save up to 63.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (57%)

Requests Now

94

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tempo O P. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tempo-oopp.cz

tempo-oopp.cz

356 ms

www.tempo-oopp.cz

www.tempo-oopp.cz

1079 ms

format.css

format.css

132 ms

boxes.css

boxes.css

243 ms

modules.css

modules.css

247 ms

thickbox.css

thickbox.css

245 ms

ui.tabs.css

ui.tabs.css

243 ms

hover.js

hover.js

245 ms

header.js

header.js

250 ms

swfobject.js

swfobject.js

366 ms

globals.js.php

globals.js.php

495 ms

main.js

main.js

402 ms

elements.js

elements.js

401 ms

ajax.js

ajax.js

399 ms

ajax_app.js

ajax_app.js

487 ms

jquery-1.2.6.pack.js

jquery-1.2.6.pack.js

611 ms

jquery.autocomplete.js

jquery.autocomplete.js

495 ms

jquery.scrollTo-1.3.3-min.js

jquery.scrollTo-1.3.3-min.js

544 ms

jquery.form.js

jquery.form.js

610 ms

jquery.custom.js

jquery.custom.js

628 ms

custom.jquery.init.js

custom.jquery.init.js

682 ms

thickbox.patch.js

thickbox.patch.js

669 ms

im_links.js

im_links.js

729 ms

body.gif

body.gif

499 ms

netfirmy130-1-p1.png

netfirmy130-1-p1.png

324 ms

a.jpg

a.jpg

622 ms

logo.gif

logo.gif

406 ms

slogan.gif

slogan.gif

423 ms

topmenu.gif

topmenu.gif

470 ms

topmenu_r.gif

topmenu_r.gif

469 ms

topmenu_active.gif

topmenu_active.gif

527 ms

ico_map.gif

ico_map.gif

529 ms

bg-search.gif

bg-search.gif

544 ms

submit.gif

submit.gif

620 ms

tn_obrazek_785.jpg

tn_obrazek_785.jpg

620 ms

tn_obrazek_389.jpg

tn_obrazek_389.jpg

684 ms

tn_obrazek_2247.jpg

tn_obrazek_2247.jpg

682 ms

tn_obrazek_517.jpg

tn_obrazek_517.jpg

681 ms

ebrana.gif

ebrana.gif

739 ms

wa.gif

wa.gif

739 ms

netfirmy130-1-p2.png

netfirmy130-1-p2.png

324 ms

analytics.js

analytics.js

12 ms

maps

maps

34 ms

h1.gif

h1.gif

726 ms

h2.gif

h2.gif

798 ms

strom_bottom.gif

strom_bottom.gif

798 ms

strom_top.gif

strom_top.gif

796 ms

hlavicka_strom.gif

hlavicka_strom.gif

838 ms

strom_li.gif

strom_li.gif

838 ms

sloupecbox_bottom.gif

sloupecbox_bottom.gif

837 ms

collect

collect

4 ms

collect

collect

62 ms

embed

embed

385 ms

L.js

L.js

238 ms

sloupecbox_top.gif

sloupecbox_top.gif

822 ms

hlavicka.gif

hlavicka.gif

818 ms

kosik_bottom.gif

kosik_bottom.gif

821 ms

hlavicka_kosik.gif

hlavicka_kosik.gif

835 ms

kosik_button.gif

kosik_button.gif

815 ms

eshop_top_bottom.gif

eshop_top_bottom.gif

732 ms

eshop_top_top.gif

eshop_top_top.gif

798 ms

li.gif

li.gif

799 ms

bottom.gif

bottom.gif

808 ms

loadingAnimation.gif

loadingAnimation.gif

730 ms

js

js

64 ms

init_embed.js

init_embed.js

36 ms

common.js

common.js

51 ms

map.js

map.js

64 ms

google4.png

google4.png

88 ms

overlay.js

overlay.js

24 ms

util.js

util.js

84 ms

onion.js

onion.js

83 ms

search_impl.js

search_impl.js

84 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

168 ms

stats.js

stats.js

87 ms

openhand_8_8.cur

openhand_8_8.cur

59 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

108 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

52 ms

kh

kh

134 ms

transparent.png

transparent.png

64 ms

controls.js

controls.js

23 ms

css

css

77 ms

entity11.png

entity11.png

41 ms

mapcnt6.png

mapcnt6.png

35 ms

tmapctrl.png

tmapctrl.png

24 ms

vt

vt

74 ms

vt

vt

150 ms

vt

vt

80 ms

vt

vt

80 ms

vt

vt

72 ms

vt

vt

70 ms

vt

vt

118 ms

vt

vt

101 ms

vt

vt

102 ms

vt

vt

106 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

62 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

75 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

84 ms

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff

97 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

18 ms

print.css

print.css

122 ms

Accessibility Review

tempo-oopp.cz accessibility score

89

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

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

High

<object> elements do not have alternate text

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

tempo-oopp.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

SEO Factors

tempo-oopp.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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    CS

  • Encoding

    WINDOWS-1250

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tempo-oopp.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), while the claimed language is Czech. Our system also found out that Tempo-oopp.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

tempo-oopp.cz

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