Tools & Wizards About Us
uniao.edu.br screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

uniao.edu.br

Universidade Unopar | Inicie a graduação com a nota do Enem

Page Load Speed

2.6 sec in total

First Response

150 ms

Resources Loaded

2 sec

Page Rendered

416 ms

uniao.edu.br screenshot

About Website

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

Inscreva-se no vestibular 2024 e dê o primeiro passo para a conquista do seu diploma! Conheça os cursos de graduação da Unopar e matricule-se já!

Visit uniao.edu.br

Key Findings

We analyzed Uniao.edu.br page load time and found that the first response time was 150 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

uniao.edu.br performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value3,910 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.443

21/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

www.unopar.com.br

150 ms

events.js

493 ms

gtm.js

167 ms

gtm.js

276 ms

maze-universal-loader.js

44 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Uniao.edu.br, 7% (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 (808 ms) relates to the external source Pim-anhanguera.s3.sa-east-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 527.9 kB (53%)

Content Size

991.2 kB

After Optimization

463.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Uniao.edu.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. Only a small number of websites need less resources to load. HTML takes 404.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 336.9 kB

  • Original 404.6 kB
  • After minification 404.5 kB
  • After compression 67.7 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 336.9 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 8.9 kB

  • Original 293.8 kB
  • After minification 284.9 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. Uniao images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 182.0 kB

  • Original 292.7 kB
  • After minification 292.7 kB
  • After compression 110.7 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 182.0 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 53 (83%)

Requests Now

64

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.unopar.com.br

www.unopar.com.br

150 ms

events.js

events.js

493 ms

gtm.js

gtm.js

167 ms

gtm.js

gtm.js

276 ms

maze-universal-loader.js

maze-universal-loader.js

44 ms

css2

css2

70 ms

10043434-10049184.js

10043434-10049184.js

61 ms

1777c15200e578a5.css

1777c15200e578a5.css

33 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

59 ms

5675-c4433d1a74ef4011.js

5675-c4433d1a74ef4011.js

42 ms

3582-59d1dd1e50be46cb.js

3582-59d1dd1e50be46cb.js

53 ms

2791.d3f9530ab5e329d4.js

2791.d3f9530ab5e329d4.js

58 ms

8486-d9c1d3af386f4da3.js

8486-d9c1d3af386f4da3.js

57 ms

8141.5d8e907d2e2390d0.js

8141.5d8e907d2e2390d0.js

165 ms

5937.5535e677b591c68a.js

5937.5535e677b591c68a.js

56 ms

5010.dd08364a4e2050a6.js

5010.dd08364a4e2050a6.js

156 ms

7189.350d85e3472605bb.js

7189.350d85e3472605bb.js

152 ms

3914-1356cab77a4e5a01.js

3914-1356cab77a4e5a01.js

61 ms

1104.d6062b634c6eeb1e.js

1104.d6062b634c6eeb1e.js

66 ms

1303.95a5b4d6e86d075c.js

1303.95a5b4d6e86d075c.js

156 ms

1099.bd2e7202129f9359.js

1099.bd2e7202129f9359.js

153 ms

348.152ca3dae663a056.js

348.152ca3dae663a056.js

153 ms

webpack-449809139904b537.js

webpack-449809139904b537.js

153 ms

framework-eae1dab60e375b5f.js

framework-eae1dab60e375b5f.js

155 ms

main-e67536794039951d.js

main-e67536794039951d.js

158 ms

_app-0a7c34ba90e35fd1.js

_app-0a7c34ba90e35fd1.js

261 ms

1bfc9850-9894e9e4d30100be.js

1bfc9850-9894e9e4d30100be.js

263 ms

4076-eba82b7aaf3fccb3.js

4076-eba82b7aaf3fccb3.js

263 ms

4755-97e1e04d65ca84cb.js

4755-97e1e04d65ca84cb.js

206 ms

4181-cf3562f550d9806c.js

4181-cf3562f550d9806c.js

268 ms

6066-e32a6d832da11d9d.js

6066-e32a6d832da11d9d.js

265 ms

5697-f75c5129b53aa334.js

5697-f75c5129b53aa334.js

265 ms

5112-a3ad112249b394fb.js

5112-a3ad112249b394fb.js

412 ms

3496-88ef6663855d303c.js

3496-88ef6663855d303c.js

412 ms

6578-554e4ac4ea2b5487.js

6578-554e4ac4ea2b5487.js

412 ms

2288-9348790f161e290d.js

2288-9348790f161e290d.js

284 ms

6182-3602efce07fc1fa9.js

6182-3602efce07fc1fa9.js

414 ms

5297-86ec3b92ba2f39b4.js

5297-86ec3b92ba2f39b4.js

416 ms

%5B...slug%5D-fa119dcad97c436f.js

%5B...slug%5D-fa119dcad97c436f.js

415 ms

_buildManifest.js

_buildManifest.js

416 ms

_ssgManifest.js

_ssgManifest.js

480 ms

T4SAN-XXJDB-425MW-YM3N9-3LLCJ

T4SAN-XXJDB-425MW-YM3N9-3LLCJ

336 ms

brandlogo-anhanguera.png

brandlogo-anhanguera.png

759 ms

brandlogo-anhanguera-icone.png

brandlogo-anhanguera-icone.png

808 ms

273 ms

274 ms

272 ms

273 ms

index.js

index.js

217 ms

ins.js

ins.js

327 ms

application.js

application.js

381 ms

js

js

195 ms

fbevents.js

fbevents.js

311 ms

bat.js

bat.js

350 ms

events.js

events.js

359 ms

tagtag.min.js

tagtag.min.js

412 ms

lbwzqr9o8s

lbwzqr9o8s

357 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-Y3tco5q6.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-Y3tco5q6.ttf

350 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-Y3tco5q6.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-Y3tco5q6.ttf

397 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-Y3tco5q6.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-Y3tco5q6.ttf

458 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-Y3tco5q6.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-Y3tco5q6.ttf

462 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-Y3tco5q6.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-Y3tco5q6.ttf

588 ms

config.json

config.json

389 ms

332336615422668

332336615422668

263 ms

139001368.js

139001368.js

60 ms

clarity.js

clarity.js

111 ms

main.MTc2ZTRjM2Y4MA.js

main.MTc2ZTRjM2Y4MA.js

115 ms

139001368

139001368

154 ms

tracking.min.js

tracking.min.js

147 ms

crossdevice.min.js

crossdevice.min.js

148 ms

collect

collect

59 ms

c.gif

c.gif

7 ms

Accessibility Review

uniao.edu.br accessibility score

75

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

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

Heading elements are not in a sequentially-descending order

Best Practices

uniao.edu.br best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

SEO Factors

uniao.edu.br SEO score

75

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

uniao.edu.br

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