Tools & Wizards About Us
unasp.br screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

unasp.br

Home - UNASP - Centro Universitário Adventista de São Paulo

Page Load Speed

2.9 sec in total

First Response

79 ms

Resources Loaded

2.4 sec

Page Rendered

443 ms

unasp.br screenshot

About Website

Visit unasp.br now to see the best up-to-date UNASP content for Mozambique and also check out these interesting facts you probably never knew about unasp.br

Aqui no UNASP temos mais de 40 cursos de graduação e mais de 100 cursos de pós-graduação. Venha viver as melhores % pra Vida!

Visit unasp.br

Key Findings

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

Performance Metrics

unasp.br performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value4,380 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

unasp.br

79 ms

unasp.br

319 ms

gtm.js

89 ms

style.css

14 ms

js_composer.min.css

37 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 22% of them (14 requests) were addressed to the original Unasp.br, 17% (11 requests) were made to Fonts.gstatic.com and 11% (7 requests) were made to Cdn1.unasp.br. The less responsive or slowest element that took the longest time to load (929 ms) relates to the external source Cdn1.unasp.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.4 kB (6%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Unasp.br main page is 1.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 782.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 92.3 kB

  • Original 115.1 kB
  • After minification 115.0 kB
  • After compression 22.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 92.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

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

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 561.7 kB
  • After minification 561.7 kB
  • After compression 558.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.8 kB

  • Original 148.7 kB
  • After minification 148.7 kB
  • After compression 144.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. Unasp.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (63%)

Requests Now

51

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

unasp.br

unasp.br

79 ms

unasp.br

unasp.br

319 ms

gtm.js

gtm.js

89 ms

style.css

style.css

14 ms

js_composer.min.css

js_composer.min.css

37 ms

jquery.js

jquery.js

59 ms

css

css

124 ms

main.css

main.css

402 ms

custom_style.css

custom_style.css

21 ms

rdstation-forms.min.js

rdstation-forms.min.js

80 ms

vendor.js

vendor.js

461 ms

index.js

index.js

462 ms

css

css

167 ms

css

css

200 ms

css

css

199 ms

rs6.css

rs6.css

32 ms

rbtools.min.js

rbtools.min.js

53 ms

rs6.min.js

rs6.min.js

73 ms

migrate.js

migrate.js

52 ms

autocomplete.js

autocomplete.js

73 ms

ajax-script.js

ajax-script.js

72 ms

js_composer_front.min.js

js_composer_front.min.js

72 ms

js

js

84 ms

fbevents.js

fbevents.js

191 ms

bat.js

bat.js

237 ms

insight.min.js

insight.min.js

298 ms

collect

collect

598 ms

unasp_logo.png

unasp_logo.png

929 ms

menu-unasp-2.jpg

menu-unasp-2.jpg

130 ms

dummy.png

dummy.png

62 ms

unasp-menu-2.jpg

unasp-menu-2.jpg

119 ms

jovem-mulher-com-fones-de-ouvido-escrevendo-no-notebook-e-trabalhando-no-laptop-no-cafe-1-400x267.jpg

jovem-mulher-com-fones-de-ouvido-escrevendo-no-notebook-e-trabalhando-no-laptop-no-cafe-1-400x267.jpg

123 ms

GECCOM2-400x240.jpg

GECCOM2-400x240.jpg

121 ms

bg-mec-300x197.jpg

bg-mec-300x197.jpg

917 ms

1_motivo.jpg

1_motivo.jpg

147 ms

2motivos.jpg

2motivos.jpg

148 ms

3motivos.jpg

3motivos.jpg

130 ms

4motivo.jpg

4motivo.jpg

145 ms

5motivo.jpg

5motivo.jpg

122 ms

RBTracking.min.js

RBTracking.min.js

909 ms

css2

css2

90 ms

font-awesome.min.css

font-awesome.min.css

152 ms

events.js

events.js

233 ms

d0a952a2-cafd-4f7b-8cdb-c0750634804c-loader.js

d0a952a2-cafd-4f7b-8cdb-c0750634804c-loader.js

295 ms

3Jn5SD_-ynaxmxnEfVHPIG0CduBp0uNz.ttf

3Jn5SD_-ynaxmxnEfVHPIG0CduBp0uNz.ttf

75 ms

3JnkSD_-ynaxmxnEfVHPIGXdUvBE8OtZMn1b.ttf

3JnkSD_-ynaxmxnEfVHPIGXdUvBE8OtZMn1b.ttf

93 ms

3JnkSD_-ynaxmxnEfVHPIGW5U_BE8OtZMn1b.ttf

3JnkSD_-ynaxmxnEfVHPIGW5U_BE8OtZMn1b.ttf

153 ms

L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_7Pq_ROW9AJi8SKQu.ttf

L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_7Pq_ROW9AJi8SKQu.ttf

254 ms

L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_Of2_ROW9AJi8SKQu.ttf

L0xuDF4xlVMF-BfR8bXMIhJHg45mwgGEFl0_Of2_ROW9AJi8SKQu.ttf

190 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

877 ms

97031413.js

97031413.js

42 ms

insight_tag_errors.gif

insight_tag_errors.gif

247 ms

97031413

97031413

344 ms

kJF1BvYX7BgnkSrUwT8OhrdQw4oELdPIeeII9v6oDMzByHX9rA6RzaxHMPdY43zj-jCxv3fzvRNU22ZXGJpEpjC_1n-q_4MrImHCIJIZrDBIG-embd5zrAAu.ttf

kJF1BvYX7BgnkSrUwT8OhrdQw4oELdPIeeII9v6oDMzByHX9rA6RzaxHMPdY43zj-jCxv3fzvRNU22ZXGJpEpjC_1n-q_4MrImHCIJIZrDBIG-embd5zrAAu.ttf

274 ms

main.MTExZjAwMWE5MQ.js

main.MTExZjAwMWE5MQ.js

200 ms

rodape_unasp.png

rodape_unasp.png

137 ms

clarity.js

clarity.js

96 ms

_set_cookie

_set_cookie

352 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

89 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

89 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

217 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

149 ms

249 ms

bundle.js

bundle.js

587 ms

Accessibility Review

unasp.br accessibility score

57

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

ARIA IDs are not unique

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.

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

unasp.br best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

unasp.br SEO score

86

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

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

unasp.br

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