Tools & Wizards About Us
trigema.cz screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

trigema.cz

Trigema

Page Load Speed

3.9 sec in total

First Response

317 ms

Resources Loaded

2.9 sec

Page Rendered

679 ms

trigema.cz screenshot

About Website

Welcome to trigema.cz homepage info - get ready to check Trigema best content for Czech Republic right away, or after learning these important things about trigema.cz

Skupina Trigema je primárně developerskou a stavební společností s přesahem do dalších aktivit. Jsme ryze česká investiční společnost, která se rozhoduje samostatně, na základě vlastních vizí a motiva...

Visit trigema.cz

Key Findings

We analyzed Trigema.cz page load time and found that the first response time was 317 ms and then it took 3.6 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

trigema.cz performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

trigema.cz

317 ms

www.trigema.cz

547 ms

cookieconsent.css

521 ms

cookieconsent_custom.css

523 ms

cookieconsent.js

630 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 14% of them (10 requests) were addressed to the original Trigema.cz, 41% (29 requests) were made to C.trigema.cz and 13% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source C.trigema.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.4 kB (4%)

Content Size

3.8 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trigema.cz main page is 3.8 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 112.0 kB

  • Original 133.8 kB
  • After minification 96.3 kB
  • After compression 21.9 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 37.5 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 112.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 37.4 kB

  • Original 3.4 MB
  • After minification 3.3 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. Trigema images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 9.9 kB

  • Original 256.7 kB
  • After minification 256.7 kB
  • After compression 246.8 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

-5%

Potential reduce by 3.1 kB

  • Original 57.8 kB
  • After minification 57.8 kB
  • After compression 54.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. Trigema.cz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

58

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trigema.cz

trigema.cz

317 ms

www.trigema.cz

www.trigema.cz

547 ms

cookieconsent.css

cookieconsent.css

521 ms

cookieconsent_custom.css

cookieconsent_custom.css

523 ms

cookieconsent.js

cookieconsent.js

630 ms

stylesheet.css

stylesheet.css

212 ms

bootstrap_2024.css

bootstrap_2024.css

636 ms

all.min.css

all.min.css

24 ms

aos.css

aos.css

30 ms

tiny-slider.css

tiny-slider.css

34 ms

video-js.css

video-js.css

43 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

18 ms

jquery-ui.js

jquery-ui.js

41 ms

1689170031.css

1689170031.css

846 ms

1712757267.css

1712757267.css

488 ms

popper.min.js

popper.min.js

39 ms

504 ms

video-js.css

video-js.css

15 ms

api.js

api.js

31 ms

420 ms

bootstrap4_6_0.js

bootstrap4_6_0.js

533 ms

aos.js

aos.js

15 ms

tiny-slider.js

tiny-slider.js

11 ms

js.cookie.min.js

js.cookie.min.js

12 ms

440 ms

986 ms

527 ms

gtm.js

gtm.js

98 ms

gtm.js

gtm.js

147 ms

css2

css2

35 ms

logo-black-full.svg

logo-black-full.svg

112 ms

logo-white-full.svg

logo-white-full.svg

215 ms

search.svg

search.svg

215 ms

KS_Blue.png

KS_Blue.png

392 ms

TRE_developer-of-different.jpg

TRE_developer-of-different.jpg

676 ms

logo.svg

logo.svg

214 ms

arrow-up-blue.svg

arrow-up-blue.svg

416 ms

logo-text.svg

logo-text.svg

417 ms

tovarna_komin.jpg

tovarna_komin.jpg

709 ms

slider-item-FRGMNT.jpg

slider-item-FRGMNT.jpg

807 ms

BoR.png

BoR.png

607 ms

arrow-white.svg

arrow-white.svg

528 ms

arrow-up-white.svg

arrow-up-white.svg

528 ms

vizu_ext_2.jpg

vizu_ext_2.jpg

912 ms

LIH_erektus.jpeg

LIH_erektus.jpeg

1020 ms

Paprsek_F.jpg

Paprsek_F.jpg

1013 ms

SKV_detail1.jpeg

SKV_detail1.jpeg

886 ms

slider-item-3.jpg

slider-item-3.jpg

929 ms

HR_JK.jpg

HR_JK.jpg

1015 ms

HR_MT.jpg

HR_MT.jpg

991 ms

HR_RK.jpg

HR_RK.jpg

1120 ms

guard-icon.png

guard-icon.png

1031 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

157 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

332 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

360 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

362 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

363 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

361 ms

jamtype-bold.woff2

jamtype-bold.woff2

1037 ms

recaptcha__en.js

recaptcha__en.js

157 ms

vizu_ext_4.jpg

vizu_ext_4.jpg

1030 ms

anchor

anchor

76 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

11 ms

b6Oii9STWY88IrJNtLPoIZTrW6o6yVtlax6xgU_Rli0.js

b6Oii9STWY88IrJNtLPoIZTrW6o6yVtlax6xgU_Rli0.js

35 ms

webworker.js

webworker.js

62 ms

logo_48.png

logo_48.png

21 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

43 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

42 ms

recaptcha__en.js

recaptcha__en.js

18 ms

Accessibility Review

trigema.cz accessibility score

69

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-*] attributes do not match their roles

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

trigema.cz SEO score

79

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

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

trigema.cz

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