Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

tri-o.rs

Tri O – Tehnika, građevinski materijali i alati za Vaš dom

Page Load Speed

5.6 sec in total

First Response

372 ms

Resources Loaded

4.8 sec

Page Rendered

409 ms

tri-o.rs screenshot

About Website

Click here to check amazing Tri O content for Serbia. Otherwise, check out these important facts you probably never knew about tri-o.rs

Širok asortiman proizvoda – bela tehnika, televizori, građevinski materijali, alati, elektro materijal, rasveta i svi ostali uređaji. Pogledajte našu ponudu i opremite svoj dom.

Visit tri-o.rs

Key Findings

We analyzed Tri-o.rs page load time and found that the first response time was 372 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tri-o.rs performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

tri-o.rs

372 ms

www.tri-o.rs

1434 ms

kubcwckmetxbwyexronndnbmwufxvrleyytv75e0hrc1-s1-tdefault

462 ms

w7ar7xaahjxetk7y541-liwb0fnuimdqdas0qtmrxoa1

708 ms

js

46 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 86% of them (95 requests) were addressed to the original Tri-o.rs, 11% (12 requests) were made to Embed.tawk.to and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Tri-o.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 259.4 kB (37%)

Content Size

695.3 kB

After Optimization

435.9 kB

In fact, the total size of Tri-o.rs main page is 695.3 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. 40% of websites need less resources to load. Images take 290.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 209.6 kB

  • Original 232.2 kB
  • After minification 184.8 kB
  • After compression 22.5 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 47.3 kB, which is 20% 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 209.6 kB or 90% of the original size.

Image Optimization

-9%

Potential reduce by 25.9 kB

  • Original 290.3 kB
  • After minification 264.5 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. Tri O images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 23.9 kB

  • Original 172.8 kB
  • After minification 172.8 kB
  • After compression 148.9 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 23.9 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

103

After Optimization

71

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

Accessibility Review

tri-o.rs accessibility score

64

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 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-*] attributes do not have valid values

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

tri-o.rs 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tri-o.rs SEO score

81

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SR

  • Language Claimed

    SR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tri-o.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it matches the claimed language. Our system also found out that Tri-o.rs 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

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