Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

treasy.com.br

Treasy | Orçamento Empresarial, Planejamento e Controladoria

Page Load Speed

4.4 sec in total

First Response

184 ms

Resources Loaded

2.9 sec

Page Rendered

1.3 sec

About Website

Visit treasy.com.br now to see the best up-to-date Treasy content for Brazil and also check out these interesting facts you probably never knew about treasy.com.br

A solução completa de Planejamento e Controladoria para sua empresa. Orçamento Empresarial, Cenários, Indicadores de Desempenho e integração com seu ERP.

Visit treasy.com.br

Key Findings

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

Performance Metrics

treasy.com.br performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value5,340 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

www.treasy.com.br

184 ms

wp-emoji-release.min.js

40 ms

element-pack-site.css

76 ms

style.min.css

73 ms

member.min.css

66 ms

Our browser made a total of 188 requests to load all elements on the main page. We found that 56% of them (105 requests) were addressed to the original Treasy.com.br, 18% (34 requests) were made to Media.treasy.com.br and 17% (32 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Treasy.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 482.7 kB (16%)

Content Size

3.1 MB

After Optimization

2.6 MB

In fact, the total size of Treasy.com.br main page is 3.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. Only a small number of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 340.4 kB

  • Original 386.1 kB
  • After minification 386.1 kB
  • After compression 45.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. 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 340.4 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 139.6 kB

  • Original 1.6 MB
  • After minification 1.5 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. Treasy images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 466 B

  • Original 858.2 kB
  • After minification 858.2 kB
  • After compression 857.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

-1%

Potential reduce by 2.2 kB

  • Original 239.2 kB
  • After minification 237.2 kB
  • After compression 236.9 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. Treasy.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 109 (73%)

Requests Now

150

After Optimization

41

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

Accessibility Review

treasy.com.br accessibility score

81

Accessibility Issues

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.

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

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

High

Image elements do not have [alt] attributes

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

treasy.com.br 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

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

treasy.com.br 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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Treasy.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Treasy.com.br 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 data is detected on the main page of Treasy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: