Tools & Wizards About Us
futuro.usp.br screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

futuro.usp.br

INÍCIO | NACE-EF/USP

Page Load Speed

7.5 sec in total

First Response

2.2 sec

Resources Loaded

5.2 sec

Page Rendered

109 ms

futuro.usp.br screenshot

About Website

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

Visit futuro.usp.br

Key Findings

We analyzed Futuro.usp.br page load time and found that the first response time was 2.2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

futuro.usp.br performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value900 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

futuro.usp.br

2178 ms

website.ef;jsessionid=B49EBD98584F4C7E77E964AF9D41A9BC

167 ms

flash.js

162 ms

lib.js

322 ms

ef.css

162 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that all of those requests were addressed to Futuro.usp.br and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Futuro.usp.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.4 kB (22%)

Content Size

433.0 kB

After Optimization

337.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 4.9 kB

  • Original 7.0 kB
  • After minification 6.5 kB
  • After compression 2.1 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 4.9 kB or 70% of the original size.

Image Optimization

-4%

Potential reduce by 14.3 kB

  • Original 332.6 kB
  • After minification 318.3 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. Futuro USP images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 73.9 kB

  • Original 90.5 kB
  • After minification 67.8 kB
  • After compression 16.6 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 73.9 kB or 82% of the original size.

CSS Optimization

-80%

Potential reduce by 2.4 kB

  • Original 3.0 kB
  • After minification 2.5 kB
  • After compression 598 B

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. Futuro.usp.br needs all CSS files to be minified and compressed as it can save up to 2.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

36

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

futuro.usp.br

futuro.usp.br

2178 ms

website.ef;jsessionid=B49EBD98584F4C7E77E964AF9D41A9BC

website.ef;jsessionid=B49EBD98584F4C7E77E964AF9D41A9BC

167 ms

flash.js

flash.js

162 ms

lib.js

lib.js

322 ms

ef.css

ef.css

162 ms

quem_somos_01.jpg

quem_somos_01.jpg

165 ms

proj_pesq_01.jpg

proj_pesq_01.jpg

165 ms

prod_cient_01.jpg

prod_cient_01.jpg

486 ms

parceiros_01.jpg

parceiros_01.jpg

328 ms

noticias_01.jpg

noticias_01.jpg

326 ms

twitter_ico.png

twitter_ico.png

491 ms

ef_home2_09.jpg

ef_home2_09.jpg

331 ms

ef_pesquisa_patio1_07.jpg

ef_pesquisa_patio1_07.jpg

655 ms

como_chegar_01.jpg

como_chegar_01.jpg

488 ms

fale_conosco_01.jpg

fale_conosco_01.jpg

489 ms

trabalhe_conosco_01.jpg

trabalhe_conosco_01.jpg

823 ms

homepage.ef

homepage.ef

650 ms

prototype.js

prototype.js

577 ms

effects.js

effects.js

491 ms

ajax.js

ajax.js

167 ms

ef_home_mask.jpg

ef_home_mask.jpg

342 ms

4C487771E17C3B982D357B88F332F7EC.JPG

4C487771E17C3B982D357B88F332F7EC.JPG

162 ms

EB3D121BE9D7B43897D65786B438CDB5.JPG

EB3D121BE9D7B43897D65786B438CDB5.JPG

164 ms

244ADE3974943D9C31A3F4B6CB8CE765.JPG

244ADE3974943D9C31A3F4B6CB8CE765.JPG

167 ms

0FA48D53CCB398B352188ED06746911A.JPG

0FA48D53CCB398B352188ED06746911A.JPG

512 ms

386EB4F5168F342A7B7E54F48CA245CB.JPG

386EB4F5168F342A7B7E54F48CA245CB.JPG

504 ms

8344AD44FE821E7E5A4836D078F6FEA0.JPG

8344AD44FE821E7E5A4836D078F6FEA0.JPG

486 ms

E37FD6FB837DDB6458A9E3A0F598BEB7.JPG

E37FD6FB837DDB6458A9E3A0F598BEB7.JPG

656 ms

797FED67F765CCA2B4657123511E0C13.JPG

797FED67F765CCA2B4657123511E0C13.JPG

668 ms

8308CF043F6DCC1B602C8D9EBB3DEC03.JPG

8308CF043F6DCC1B602C8D9EBB3DEC03.JPG

508 ms

CF1CE740D689229252360B861DAB6786.JPG

CF1CE740D689229252360B861DAB6786.JPG

655 ms

4866DAD7E8FBE9C30F56C749D426908F.JPG

4866DAD7E8FBE9C30F56C749D426908F.JPG

829 ms

ef_home_bkg_02.jpg

ef_home_bkg_02.jpg

672 ms

ef_home_bkg_03.jpg

ef_home_bkg_03.jpg

673 ms

ef_home_bkg_04.jpg

ef_home_bkg_04.jpg

815 ms

ef_home_bkg_05.jpg

ef_home_bkg_05.jpg

816 ms

ef_home_bkg_06.jpg

ef_home_bkg_06.jpg

834 ms

ef_home_bkg_07.jpg

ef_home_bkg_07.jpg

833 ms

quem_somos_02.jpg

quem_somos_02.jpg

162 ms

Accessibility Review

futuro.usp.br accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

futuro.usp.br 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

Page has valid source maps

SEO Factors

futuro.usp.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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futuro.usp.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Futuro.usp.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

futuro.usp.br

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