Tools & Wizards About Us
upf.br screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

upf.br

Portal - UPF | Universidade de Passo Fundo

Page Load Speed

13.5 sec in total

First Response

697 ms

Resources Loaded

12.7 sec

Page Rendered

165 ms

upf.br screenshot

About Website

Welcome to upf.br homepage info - get ready to check UPF best content for Brazil right away, or after learning these important things about upf.br

A UPF, fundada em 1968, tem suas ações norteadas e sustentadas por quatro pilares: ensino, pesquisa, extensão e inovação tecnológica.

Visit upf.br

Key Findings

We analyzed Upf.br page load time and found that the first response time was 697 ms and then it took 12.8 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

upf.br performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.538

14/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

upf.br

697 ms

index.php

1194 ms

template_css.css

625 ms

styles.css

422 ms

skitter.styles.css

844 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 92% of them (56 requests) were addressed to the original Upf.br, 5% (3 requests) were made to Secure.upf.br and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Upf.br.

Page Optimization Overview & Recommendations

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

Content Size

991.2 kB

After Optimization

593.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Upf.br main page is 991.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. 20% of websites need less resources to load. Images take 572.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 28.4 kB

  • Original 33.0 kB
  • After minification 24.9 kB
  • After compression 4.6 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 8.1 kB, which is 25% 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 28.4 kB or 86% of the original size.

Image Optimization

-14%

Potential reduce by 80.7 kB

  • Original 572.8 kB
  • After minification 492.1 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. Obviously, UPF needs image optimization as it can save up to 80.7 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 263.3 kB

  • Original 354.8 kB
  • After minification 290.7 kB
  • After compression 91.5 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 263.3 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 25.0 kB

  • Original 30.5 kB
  • After minification 23.5 kB
  • After compression 5.5 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. Upf.br needs all CSS files to be minified and compressed as it can save up to 25.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (47%)

Requests Now

59

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UPF. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

upf.br

upf.br

697 ms

index.php

index.php

1194 ms

template_css.css

template_css.css

625 ms

styles.css

styles.css

422 ms

skitter.styles.css

skitter.styles.css

844 ms

fontes_padrao.css

fontes_padrao.css

424 ms

jsGeral.js

jsGeral.js

696 ms

jquery-1.6.3.min.js

jquery-1.6.3.min.js

1887 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1049 ms

jquery.animate-colors-min.js

jquery.animate-colors-min.js

1043 ms

jquery.skitter.min.js

jquery.skitter.min.js

1690 ms

jquery.skitter.js

jquery.skitter.js

4246 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

1470 ms

jquery.tipsy.js

jquery.tipsy.js

1460 ms

422 ms

noticiasInicio.php

noticiasInicio.php

481 ms

loginSite.php

loginSite.php

1419 ms

sombra_LadoEsquerdo.png

sombra_LadoEsquerdo.png

420 ms

topo_site.jpg

topo_site.jpg

1469 ms

004.png

004.png

839 ms

002.jpg

002.jpg

2747 ms

006.jpg

006.jpg

1884 ms

001.jpg

001.jpg

2745 ms

colunaMenu_topo.jpg

colunaMenu_topo.jpg

1320 ms

marcadorMenu_main.jpg

marcadorMenu_main.jpg

1253 ms

bg_menuPadrao_link.jpg

bg_menuPadrao_link.jpg

1673 ms

colunaMenu_setaInferior.jpg

colunaMenu_setaInferior.jpg

1737 ms

vestibular.png

vestibular.png

2092 ms

concursos.png

concursos.png

2299 ms

botao-lateral-calendario-formaturas.png

botao-lateral-calendario-formaturas.png

2362 ms

botao-lateral-intensivo-enem.png

botao-lateral-intensivo-enem.png

2513 ms

_menuSuperior.jpg

_menuSuperior.jpg

2722 ms

escolhe_fonte.jpg

escolhe_fonte.jpg

2724 ms

separacao_notEuSou.jpg

separacao_notEuSou.jpg

2780 ms

separacao_euSouBuscaRapida.jpg

separacao_euSouBuscaRapida.jpg

2936 ms

bolsashorizontal_2013.jpg

bolsashorizontal_2013.jpg

3972 ms

banner-horizontal-pagamento-de-mensalidades.jpg

banner-horizontal-pagamento-de-mensalidades.jpg

4393 ms

banner-transferencia-e-reingresso-2016.jpg

banner-transferencia-e-reingresso-2016.jpg

3996 ms

banner-reabertura-de-matriculas-2016.jpg

banner-reabertura-de-matriculas-2016.jpg

3801 ms

sombra_ladoDireito.png

sombra_ladoDireito.png

3205 ms

sombra_baixoLadoEsq.png

sombra_baixoLadoEsq.png

3355 ms

sombra_baixo.png

sombra_baixo.png

3627 ms

sombra_baixoLadoDir.png

sombra_baixoLadoDir.png

4811 ms

banner_conecetese.png

banner_conecetese.png

4048 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

23 ms

sprite-clean.png

sprite-clean.png

4143 ms

ajax-loader.gif

ajax-loader.gif

4310 ms

estilo.css

estilo.css

4002 ms

_espanhol.jpg

_espanhol.jpg

4060 ms

_ingles.jpg

_ingles.jpg

4232 ms

jsGeral.js

jsGeral.js

4344 ms

noticias_new.css

noticias_new.css

4346 ms

prototype.js

prototype.js

1677 ms

fontes_padrao.css

fontes_padrao.css

633 ms

site_upf_barra_superior_r2_c4.jpg

site_upf_barra_superior_r2_c4.jpg

417 ms

bg_lnk.jpg

bg_lnk.jpg

484 ms

mais.jpg

mais.jpg

250 ms

avancar.jpg

avancar.jpg

416 ms

img2.php

img2.php

683 ms

background_titu_noticias.jpg

background_titu_noticias.jpg

424 ms

Accessibility Review

upf.br accessibility score

67

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.

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

Best Practices

upf.br best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

upf.br SEO score

82

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

Links do not have descriptive text

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

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

upf.br

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