Tools & Wizards About Us
trezi.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

trezi.com

Trezi - Virtual Reality (VR) architecture & design software

Page Load Speed

11.9 sec in total

First Response

749 ms

Resources Loaded

10.7 sec

Page Rendered

527 ms

trezi.com screenshot

About Website

Welcome to trezi.com homepage info - get ready to check Trezi best content for India right away, or after learning these important things about trezi.com

Trezi is an immersive VR product for the AEC industry enabling designs from 3D modeling software & architecture software to be experienced collaboratively in real-time.

Visit trezi.com

Key Findings

We analyzed Trezi.com page load time and found that the first response time was 749 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

trezi.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,180 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value36.6 s

0/100

10%

Network Requests Diagram

trezi.com

749 ms

trezi.com

2584 ms

8f1ei.css

1442 ms

8f1eg.css

2013 ms

8f1eg.css

1077 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 87% of them (72 requests) were addressed to the original Trezi.com, 6% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Trezi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 334.3 kB (40%)

Content Size

845.2 kB

After Optimization

510.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trezi.com main page is 845.2 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. 70% of websites need less resources to load. HTML takes 394.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 332.6 kB

  • Original 394.6 kB
  • After minification 394.4 kB
  • After compression 61.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. 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 332.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.2 kB
  • After minification 2.2 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. Trezi images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 154 B

  • Original 248.1 kB
  • After minification 248.1 kB
  • After compression 248.0 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

-1%

Potential reduce by 1.5 kB

  • Original 200.4 kB
  • After minification 200.3 kB
  • After compression 198.8 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. Trezi.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

73

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trezi.com

trezi.com

749 ms

trezi.com

trezi.com

2584 ms

8f1ei.css

8f1ei.css

1442 ms

8f1eg.css

8f1eg.css

2013 ms

8f1eg.css

8f1eg.css

1077 ms

8f1eg.css

8f1eg.css

1448 ms

8f1eg.css

8f1eg.css

1807 ms

post-6.css

post-6.css

1804 ms

8f1eg.css

8f1eg.css

2130 ms

post-7.css

post-7.css

2877 ms

8f1eg.css

8f1eg.css

2143 ms

post-19.css

post-19.css

2332 ms

post-21.css

post-21.css

2475 ms

8f1eg.css

8f1eg.css

2458 ms

8f1eg.css

8f1eg.css

2631 ms

js

js

75 ms

8f1eg.css

8f1eg.css

2055 ms

post-10546.css

post-10546.css

2028 ms

post-10559.css

post-10559.css

2149 ms

post-10560.css

post-10560.css

2162 ms

post-10561.css

post-10561.css

2393 ms

8f1eg.css

8f1eg.css

2393 ms

8f1ei.js

8f1ei.js

2634 ms

8f1ei.js

8f1ei.js

2534 ms

8f1ei.js

8f1ei.js

3179 ms

8f1ei.js

8f1ei.js

2535 ms

8f1ei.js

8f1ei.js

2632 ms

8f1ei.js

8f1ei.js

2706 ms

gtm.js

gtm.js

210 ms

Preloader-Final-Render.gif

Preloader-Final-Render.gif

1410 ms

trezi-logo.webp

trezi-logo.webp

563 ms

mhlimg1.webp

mhlimg1.webp

787 ms

mhlimg2.webp

mhlimg2.webp

651 ms

mhlimg3.webp

mhlimg3.webp

801 ms

mhlimg4.webp

mhlimg4.webp

1125 ms

cntmenuimgweb.webp

cntmenuimgweb.webp

1019 ms

aliencemenuimg-web.webp

aliencemenuimg-web.webp

1041 ms

cpeit1.webp

cpeit1.webp

1342 ms

cpeit2.webp

cpeit2.webp

1252 ms

cpeit3-1.webp

cpeit3-1.webp

1519 ms

cpeit4.webp

cpeit4.webp

1600 ms

residential2.webp

residential2.webp

1484 ms

playbtninpopup.svg

playbtninpopup.svg

1573 ms

hpvideothum1.webp

hpvideothum1.webp

1648 ms

Residential.webp

Residential.webp

2176 ms

hpvideothum4.webp

hpvideothum4.webp

1716 ms

hpvideothum5.webp

hpvideothum5.webp

1758 ms

Product-Descovery-1.webp

Product-Descovery-1.webp

1804 ms

cUSTOMER-CENTRICITY-2.webp

cUSTOMER-CENTRICITY-2.webp

1837 ms

Product-Descovery-5.webp

Product-Descovery-5.webp

1887 ms

Product-Descovery-3.webp

Product-Descovery-3.webp

1947 ms

Product-Descovery-4.webp

Product-Descovery-4.webp

1996 ms

Customer-Centricity.webp

Customer-Centricity.webp

2035 ms

Focus.webp

Focus.webp

2074 ms

Fully-immersive.webp

Fully-immersive.webp

2127 ms

Product-Discovery.webp

Product-Discovery.webp

2179 ms

Trust.webp

Trust.webp

2145 ms

eea69b0a-978d-487d-8770-504b47c36995-min.gif

eea69b0a-978d-487d-8770-504b47c36995-min.gif

3518 ms

209 ms

hpt4-1.webp

hpt4-1.webp

2078 ms

gensler-webimg.webp

gensler-webimg.webp

2132 ms

Satoshi-Variable.woff

Satoshi-Variable.woff

2170 ms

js

js

77 ms

fa-solid-900.woff

fa-solid-900.woff

2097 ms

fa-regular-400.woff

fa-regular-400.woff

2105 ms

8f1ej.js

8f1ej.js

2149 ms

29 ms

hpt3-1.webp

hpt3-1.webp

2129 ms

orientbell-webimg.webp

orientbell-webimg.webp

2043 ms

hpt2-1.webp

hpt2-1.webp

1907 ms

hpt1-1.webp

hpt1-1.webp

1981 ms

ramk.png

ramk.png

1912 ms

arrow-right-up-354.svg

arrow-right-up-354.svg

1905 ms

css

css

84 ms

admin-ajax.php

admin-ajax.php

1837 ms

admin-ajax.php

admin-ajax.php

840 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

18 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

58 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

102 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

141 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

140 ms

8f1eg.css

8f1eg.css

239 ms

8f1eg.css

8f1eg.css

239 ms

Accessibility Review

trezi.com accessibility score

76

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

button, link, and menuitem elements do not have accessible names.

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.

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

trezi.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

trezi.com SEO score

91

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

trezi.com

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