4.5 sec in total
341 ms
3.8 sec
341 ms
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.czWe analyzed Trigema.cz page load time and found that the first response time was 341 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
trigema.cz performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value7.1 s
5/100
25%
Value9.8 s
10/100
10%
Value530 ms
55/100
30%
Value0.026
100/100
15%
Value9.4 s
31/100
10%
341 ms
1222 ms
25 ms
110 ms
204 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 86% of them (92 requests) were addressed to the original Trigema.cz, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to C.imedia.cz. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Trigema.cz.
Page size can be reduced by 365.3 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Trigema.cz main page is 2.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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 52.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 7.4 kB, which is 12% 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 52.8 kB or 83% of the original size.
Potential reduce by 69.0 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. Trigema images are well optimized though.
Potential reduce by 144.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 144.4 kB or 61% of the original size.
Potential reduce by 99.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. Trigema.cz needs all CSS files to be minified and compressed as it can save up to 99.2 kB or 84% of the original size.
Number of requests can be reduced by 50 (49%)
102
52
The browser has sent 102 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 15 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
trigema.cz
341 ms
www.trigema.cz
1222 ms
css
25 ms
system.base.css
110 ms
system.menus.css
204 ms
system.messages.css
216 ms
system.theme.css
214 ms
aggregator.css
216 ms
date.css
217 ms
datepicker.1.7.css
215 ms
field.css
302 ms
node.css
319 ms
search.css
320 ms
user.css
322 ms
views.css
324 ms
ckeditor.css
322 ms
colorbox.css
403 ms
ctools.css
422 ms
menu_icons.css
427 ms
locale.css
426 ms
style.css
431 ms
responsive.css
428 ms
jquery.js
608 ms
jquery.once.js
528 ms
drupal.js
530 ms
cs_sm7d2g2ar8uAsGF3bEnF3FI0Gtsm7Muf7lcPLly8eIA.js
531 ms
colorbox.js
533 ms
colorbox_load.js
532 ms
scripts.js
632 ms
colorbox.css
685 ms
jquery.colorbox-min.js
688 ms
conversion.js
16 ms
retargeting.js
352 ms
analytics.js
57 ms
cclose.png
121 ms
logo-top.png
123 ms
home.png
123 ms
logo-home.png
120 ms
sitemap.png
124 ms
fbm.png
123 ms
twm.png
252 ms
ytm.png
251 ms
slider-prev.png
252 ms
slider-next.png
251 ms
menu_icon_758.png
947 ms
menu_icon_1203.png
873 ms
menu_icon_1182.jpg
449 ms
menu_icon_561.jpg
462 ms
menu_icon_1211.jpg
449 ms
menu_icon_1195.jpg
425 ms
menu_icon_1194.jpg
625 ms
menu_icon_1193.jpg
663 ms
menu_icon_899.jpg
661 ms
menu_icon_676.jpg
566 ms
menu_icon_679.jpg
679 ms
menu_icon_890.jpg
738 ms
menu_icon_900.jpg
772 ms
phone.png
757 ms
fbw.png
768 ms
tww.png
826 ms
ytw.png
858 ms
search.png
857 ms
menu.png
857 ms
menu-expanded.png
910 ms
menu-leaf.png
938 ms
socials-box-grey.png
946 ms
fb.png
948 ms
tw.png
963 ms
yt.png
1006 ms
homebg.png
1006 ms
menu_icon_874.png
973 ms
menu_icon_406.jpg
1084 ms
menu_icon_408.jpg
1087 ms
menu_icon_412.png
1100 ms
menu_icon_410.png
1044 ms
collect
11 ms
58b1ac06-3f05-438d-9e78-70fc357046c7.js
47 ms
menu_icon_405.png
1019 ms
collect
112 ms
WRf4.js
7 ms
118 ms
L.js
336 ms
menu_icon_409.png
949 ms
menu_icon_411.png
1018 ms
underline.png
1021 ms
news-vertical-border.png
1055 ms
retargeting
124 ms
ga-audiences
113 ms
piwik.js
572 ms
28 ms
i-napsali.png
882 ms
i-blog.png
864 ms
i-tisk.png
877 ms
i-news.png
907 ms
pie-blank.png
807 ms
pie-fill2.png
785 ms
pie-fill.png
750 ms
socials-box-black.png
758 ms
fb2.png
751 ms
tw2.png
728 ms
yt2.png
702 ms
top.png
738 ms
bee.png
730 ms
loading.gif
682 ms
controls.png
671 ms
hexagon-overlay.png
693 ms
collect
4 ms
trigema.cz accessibility score
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
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
trigema.cz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
trigema.cz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
CS
CS
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.
trigema.cz
Open Graph description is not detected on the main page of Trigema. 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: