Tools & Wizards About Us
facho.br screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

facho.br

FACHO

Page Load Speed

5 sec in total

First Response

862 ms

Resources Loaded

3.6 sec

Page Rendered

512 ms

facho.br screenshot

About Website

Click here to check amazing FACHO content for Brazil. Otherwise, check out these important facts you probably never knew about facho.br

Faculdade de Ciências Humanas de Olinda

Visit facho.br

Key Findings

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

Performance Metrics

facho.br performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

facho.br

862 ms

main.css

251 ms

alert.css

255 ms

bootstrap.min.css

46 ms

nanogallery2.min.css

44 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 54% of them (44 requests) were addressed to the original Facho.br, 23% (19 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Facho.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 604.6 kB (23%)

Content Size

2.6 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Facho.br main page is 2.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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 37.9 kB

  • Original 48.9 kB
  • After minification 38.6 kB
  • After compression 11.0 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 10.3 kB, which is 21% 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 37.9 kB or 78% of the original size.

Image Optimization

-14%

Potential reduce by 291.1 kB

  • Original 2.1 MB
  • After minification 1.8 MB

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, FACHO needs image optimization as it can save up to 291.1 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

-67%

Potential reduce by 218.6 kB

  • Original 328.4 kB
  • After minification 328.4 kB
  • After compression 109.8 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 218.6 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 57.0 kB

  • Original 68.3 kB
  • After minification 51.7 kB
  • After compression 11.4 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. Facho.br needs all CSS files to be minified and compressed as it can save up to 57.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (54%)

Requests Now

79

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

facho.br

facho.br

862 ms

main.css

main.css

251 ms

alert.css

alert.css

255 ms

bootstrap.min.css

bootstrap.min.css

46 ms

nanogallery2.min.css

nanogallery2.min.css

44 ms

nanogallery2.min.css

nanogallery2.min.css

58 ms

jquery-2.2.3.min.js

jquery-2.2.3.min.js

538 ms

instafeed.min.js

instafeed.min.js

278 ms

main.js

main.js

272 ms

jquery-3.5.1.slim.min.js

jquery-3.5.1.slim.min.js

31 ms

popper.min.js

popper.min.js

70 ms

bootstrap.min.js

bootstrap.min.js

62 ms

classNotification.js

classNotification.js

375 ms

owl.carousel.css

owl.carousel.css

379 ms

menuFast.js

menuFast.js

251 ms

html5-jquery.js

html5-jquery.js

598 ms

html5lightbox.js

html5lightbox.js

419 ms

js

js

77 ms

jquery.nanogallery2.min.js

jquery.nanogallery2.min.js

17 ms

owl.carousel.min.js

owl.carousel.min.js

497 ms

reset.css

reset.css

264 ms

principal.css

principal.css

508 ms

www.facho.br

www.facho.br

1364 ms

css

css

34 ms

gtm.js

gtm.js

49 ms

xis.svg

xis.svg

280 ms

logo.png

logo.png

276 ms

qrcode.png

qrcode.png

585 ms

sprite.png

sprite.png

275 ms

setasubMenu.svg

setasubMenu.svg

275 ms

4-Banner_2_SITE_FACHO_1.png

4-Banner_2_SITE_FACHO_1.png

743 ms

5-Banner_2_SITE_FACHO_4.png

5-Banner_2_SITE_FACHO_4.png

678 ms

2-3.png

2-3.png

692 ms

4-Banner_2_SITE_FACHO_3.png

4-Banner_2_SITE_FACHO_3.png

829 ms

2-banner_site_facho_1.jpg

2-banner_site_facho_1.jpg

670 ms

portal%20do%20aluno.svg

portal%20do%20aluno.svg

670 ms

portal%20do%20professor.svg

portal%20do%20professor.svg

734 ms

wppFixo.png

wppFixo.png

800 ms

iconInstagram.png

iconInstagram.png

800 ms

iconFacebook.png

iconFacebook.png

807 ms

iconYoutube.png

iconYoutube.png

882 ms

Chamada01_BIBLIOTECA.png

Chamada01_BIBLIOTECA.png

870 ms

Chamada02_FORUM.png

Chamada02_FORUM.png

938 ms

Chamada03_DIPLOMA.png

Chamada03_DIPLOMA.png

1050 ms

Chamada04_SENHA.png

Chamada04_SENHA.png

1056 ms

Chamada05_EGRESSO.png

Chamada05_EGRESSO.png

1095 ms

Chamada06_ESTAGIO.png

Chamada06_ESTAGIO.png

998 ms

Graduacao.jpg

Graduacao.jpg

1014 ms

3-Colaboradores.jpg

3-Colaboradores.jpg

1073 ms

WhatsApp_Image_20240123_at_10.45.22.jpg

WhatsApp_Image_20240123_at_10.45.22.jpg

1125 ms

FACHO_CARDS_2_5.jpg

FACHO_CARDS_2_5.jpg

1167 ms

instagram.png

instagram.png

1177 ms

page.php

page.php

468 ms

logozaite.png

logozaite.png

1101 ms

font

font

192 ms

fbevents.js

fbevents.js

225 ms

js

js

202 ms

froogaloop2.min.js

froogaloop2.min.js

1107 ms

iframe_api

iframe_api

243 ms

www-widgetapi.js

www-widgetapi.js

4 ms

eOzOzediAge.css

eOzOzediAge.css

22 ms

wZ8DZS0aJQd.css

wZ8DZS0aJQd.css

24 ms

cuPjK18RJ2t.css

cuPjK18RJ2t.css

29 ms

VWDhCULazb5.js

VWDhCULazb5.js

36 ms

DMwA8evzWwy.js

DMwA8evzWwy.js

27 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

35 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

26 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

32 ms

p55HfXW__mM.js

p55HfXW__mM.js

32 ms

k_PjgALRjoR.js

k_PjgALRjoR.js

81 ms

zwTWzAnSRVD.js

zwTWzAnSRVD.js

84 ms

XKFYjgE7mEh.js

XKFYjgE7mEh.js

91 ms

g2XPN2wRGmV.js

g2XPN2wRGmV.js

83 ms

E6qR0C8WEpl.js

E6qR0C8WEpl.js

105 ms

kgAz0TBWoYE.js

kgAz0TBWoYE.js

87 ms

DPxpTcknHiI.js

DPxpTcknHiI.js

87 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

89 ms

326532583_1290464308478549_8581758398776053255_n.png

326532583_1290464308478549_8581758398776053255_n.png

45 ms

326746636_702263381353301_6866359519193641060_n.png

326746636_702263381353301_6866359519193641060_n.png

42 ms

u2HYktv2mdq.js

u2HYktv2mdq.js

23 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

22 ms

Accessibility Review

facho.br accessibility score

76

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.

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

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

SEO Factors

facho.br SEO score

84

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    ISO88591

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facho.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 Facho.br main page’s claimed encoding is iso88591. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

facho.br

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