Tools & Wizards About Us
yunit.pt screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

yunit.pt

Yunit Consulting - Consultoria, Corporate Finance, Sustentabilidade

Page Load Speed

2.8 sec in total

First Response

304 ms

Resources Loaded

2 sec

Page Rendered

491 ms

yunit.pt screenshot

About Website

Welcome to yunit.pt homepage info - get ready to check Yunit best content for Portugal right away, or after learning these important things about yunit.pt

Somos uma consultora de gestão especializada no apoio ao investimento e à capitalização das empresas através de incentivos fiscais e financeiros.

Visit yunit.pt

Key Findings

We analyzed Yunit.pt page load time and found that the first response time was 304 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

yunit.pt performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

yunit.pt

304 ms

316 ms

uc.js

97 ms

app.css

200 ms

css2

35 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Yunit.pt, 68% (17 requests) were made to Yunitconsulting.pt and 20% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Yunitconsulting.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.4 kB (43%)

Content Size

468.5 kB

After Optimization

265.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Yunit.pt main page is 468.5 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. 50% of websites need less resources to load. Javascripts take 280.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 112.6 kB

  • Original 140.4 kB
  • After minification 102.6 kB
  • After compression 27.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 37.8 kB, which is 27% 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.6 kB or 80% of the original size.

JavaScript Optimization

-32%

Potential reduce by 89.3 kB

  • Original 280.4 kB
  • After minification 280.4 kB
  • After compression 191.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 89.3 kB or 32% of the original size.

CSS Optimization

-3%

Potential reduce by 1.4 kB

  • Original 47.7 kB
  • After minification 47.7 kB
  • After compression 46.3 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. Yunit.pt has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yunit. According to our analytics all requests are already optimized.

Network Requests Diagram

yunit.pt

yunit.pt

304 ms

316 ms

uc.js

uc.js

97 ms

app.css

app.css

200 ms

css2

css2

35 ms

app.js

app.js

684 ms

L08zbS8tME0zWnJTbS9aa2pNam0vRmpyam0xa25udHp0ZGty.webp

L08zbS8tME0zWnJTbS9aa2pNam0vRmpyam0xa25udHp0ZGty.webp

229 ms

L08zbS8tME0zWnJTbS92Uy1NLVptMU0zWnJTMzE5WkpKU24xYU03U3Q0dGRrcg.webp

L08zbS8tME0zWnJTbS92Uy1NLVptMU0zWnJTMzE5WkpKU24xYU03U3Q0dGRrcg.webp

520 ms

L08zbS8tME0zWnJTbS9LakpLU003ai9NYTdqSzgxem82ejV6THFRenR6dGRrcg.webp

L08zbS8tME0zWnJTbS9LakpLU003ai9NYTdqSzgxem82ejV6THFRenR6dGRrcg.webp

719 ms

L08zbS8tME0zWnJTbS9LakpLU003ai9NYTdqSzgxem9xNm9MNjZvUXNvdHp0ZGty.webp

L08zbS8tME0zWnJTbS9LakpLU003ai9NYTdqSzgxem9xNm9MNjZvUXNvdHp0ZGty.webp

711 ms

L08zbS8tME0zWnJTbS92Uy1NLVptMU0zWnJTMzE5WkpKU24xYU03UzF3MGpqODNodHp0ZGty.webp

L08zbS8tME0zWnJTbS92Uy1NLVptMU0zWnJTMzE5WkpKU24xYU03UzF3MGpqODNodHp0ZGty.webp

510 ms

L08zbS8tME0zWnJTbS80eTQ2eVY0bzFobjdNcmo5RmpyZU52d3R6dGRrcg.webp

L08zbS8tME0zWnJTbS80eTQ2eVY0bzFobjdNcmo5RmpyZU52d3R6dGRrcg.webp

335 ms

L08zbS8tME0zWnJTbS80eTQ2eVY0NDFobjdNcmo5RmpydEl1WkZNVE1LWktaanR6dGRrcg.webp

L08zbS8tME0zWnJTbS80eTQ2eVY0NDFobjdNcmo5RmpydEl1WkZNVE1LWktaanR6dGRrcg.webp

449 ms

L08zbS8tME0zWnJTbS85WkpKU25IdUpNN1hNRFNGTUo4Uy1wSnR6dGRrcg.webp

L08zbS8tME0zWnJTbS85WkpKU25IdUpNN1hNRFNGTUo4Uy1wSnR6dGRrcg.webp

560 ms

L08zbS8tME0zWnJTbS80eTQ2eVY0NDFobjdNcmo5RmpydEl1WkZNVE1LWktaanR6dGRrcg.webp

L08zbS8tME0zWnJTbS80eTQ2eVY0NDFobjdNcmo5RmpydEl1WkZNVE1LWktaanR6dGRrcg.webp

627 ms

L08zbS8tME0zWnJTbS80eTQ2eVY0bzFobjdNcmo5RmpyZU52d3R6dGRrcg.webp

L08zbS8tME0zWnJTbS80eTQ2eVY0bzFobjdNcmo5RmpyZU52d3R6dGRrcg.webp

631 ms

L08zbS8tME0zWnJTbS9sdTBuTUtaZ0N0V2ptU0FNanJqdHp0ZGty.webp

L08zbS8tME0zWnJTbS9sdTBuTUtaZ0N0V2ptU0FNanJqdHp0ZGty.webp

672 ms

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqc3pzNHR6dGtKcg.webp

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqc3pzNHR6dGtKcg.webp

688 ms

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqczRzNHR6dGtKcg.webp

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqczRzNHR6dGtKcg.webp

738 ms

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqc290enRrSnI.webp

L08zbS8tME0zWnJTbS9LakpSU0tNM1NKN2ovRE0tU2ptc0taa1ptL0RNLVNqc290enRrSnI.webp

742 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

20 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

35 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

57 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

56 ms

qFdb35qfgYFjGy5hukqqhw5XeRgdi1qsd5DL.ttf

qFdb35qfgYFjGy5hukqqhw5XeRgdi1qsd5DL.ttf

42 ms

Accessibility Review

yunit.pt accessibility score

86

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

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

yunit.pt 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

yunit.pt SEO score

93

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

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yunit.pt 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 Yunit.pt 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

yunit.pt

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