Tools & Wizards About Us
fvj.br screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fvj.br

UniJaguaribe – Formar líderes é a nossa missão!

Page Load Speed

16 sec in total

First Response

248 ms

Resources Loaded

15 sec

Page Rendered

724 ms

fvj.br screenshot

About Website

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

Visit fvj.br

Key Findings

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

fvj.br performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value23.8 s

0/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

fvj.br

248 ms

unijaguaribe.edu.br

8498 ms

js

65 ms

wc-blocks-vendors-style.css

34 ms

wc-blocks-style.css

27 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fvj.br, 76% (81 requests) were made to Unijaguaribe.edu.br and 16% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.5 sec) relates to the external source Unijaguaribe.edu.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (25%)

Content Size

9.7 MB

After Optimization

7.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fvj.br main page is 9.7 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. Only a small number of websites need less resources to load. Images take 8.6 MB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 381.2 kB

  • Original 613.9 kB
  • After minification 606.4 kB
  • After compression 232.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 381.2 kB or 62% of the original size.

Image Optimization

-24%

Potential reduce by 2.1 MB

  • Original 8.6 MB
  • After minification 6.5 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, Fvj needs image optimization as it can save up to 2.1 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 616 B

  • Original 323.5 kB
  • After minification 323.5 kB
  • After compression 322.9 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

-0%

Potential reduce by 809 B

  • Original 186.4 kB
  • After minification 186.4 kB
  • After compression 185.6 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. Fvj.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 70 (84%)

Requests Now

83

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fvj.br

fvj.br

248 ms

unijaguaribe.edu.br

unijaguaribe.edu.br

8498 ms

js

js

65 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

34 ms

wc-blocks-style.css

wc-blocks-style.css

27 ms

frontend.css

frontend.css

33 ms

woocommerce-layout.css

woocommerce-layout.css

21 ms

woocommerce.css

woocommerce.css

22 ms

frontend.css

frontend.css

37 ms

style.min.css

style.min.css

35 ms

theme.min.css

theme.min.css

36 ms

jet-elements.css

jet-elements.css

42 ms

jet-elements-skin.css

jet-elements-skin.css

37 ms

elementor-icons.min.css

elementor-icons.min.css

54 ms

frontend-legacy.min.css

frontend-legacy.min.css

38 ms

frontend.min.css

frontend.min.css

49 ms

frontend.min.css

frontend.min.css

28 ms

all.min.css

all.min.css

18 ms

v4-shims.min.css

v4-shims.min.css

21 ms

chosen.min.css

chosen.min.css

16 ms

jet-search.css

jet-search.css

14 ms

css

css

38 ms

fontawesome.min.css

fontawesome.min.css

24 ms

solid.min.css

solid.min.css

37 ms

brands.min.css

brands.min.css

37 ms

jquery.min.js

jquery.min.js

44 ms

jquery-migrate.min.js

jquery-migrate.min.js

43 ms

imagesloaded.min.js

imagesloaded.min.js

42 ms

js.cookie.min.js

js.cookie.min.js

42 ms

v4-shims.min.js

v4-shims.min.js

42 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

56 ms

public.js

public.js

57 ms

unijauaribe-horizontal.png

unijauaribe-horizontal.png

49 ms

1.png

1.png

51 ms

2.png

2.png

49 ms

3.png

3.png

50 ms

IPHONE-PARTE-LIGA-FTP.png

IPHONE-PARTE-LIGA-FTP.png

51 ms

7255945.png

7255945.png

136 ms

CARTELA-SITE.png

CARTELA-SITE.png

129 ms

PREMIO-VIDA.png

PREMIO-VIDA.png

92 ms

FUNDO-scaled.webp

FUNDO-scaled.webp

93 ms

animations.min.css

animations.min.css

36 ms

font-awesome.min.css

font-awesome.min.css

32 ms

public.css

public.css

37 ms

underscore.min.js

underscore.min.js

35 ms

wp-util.min.js

wp-util.min.js

36 ms

chosen.jquery.min.js

chosen.jquery.min.js

35 ms

jet-search.js

jet-search.js

65 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

64 ms

add-to-cart.min.js

add-to-cart.min.js

64 ms

woocommerce.min.js

woocommerce.min.js

65 ms

cart-fragments.min.js

cart-fragments.min.js

66 ms

jquery.ddslick.min.js

jquery.ddslick.min.js

65 ms

frontend.js

frontend.js

68 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

91 ms

slick.min.js

slick.min.js

91 ms

frontend.js

frontend.js

68 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

90 ms

webpack.runtime.min.js

webpack.runtime.min.js

124 ms

frontend-modules.min.js

frontend-modules.min.js

125 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

124 ms

wp-polyfill.min.js

wp-polyfill.min.js

154 ms

hooks.min.js

hooks.min.js

148 ms

i18n.min.js

i18n.min.js

151 ms

frontend.min.js

frontend.min.js

149 ms

waypoints.min.js

waypoints.min.js

148 ms

core.min.js

core.min.js

152 ms

swiper.min.js

swiper.min.js

201 ms

share-link.min.js

share-link.min.js

159 ms

dialog.min.js

dialog.min.js

200 ms

frontend.min.js

frontend.min.js

200 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

207 ms

jet-elements.min.js

jet-elements.min.js

207 ms

preloaded-modules.min.js

preloaded-modules.min.js

209 ms

jquery.sticky.min.js

jquery.sticky.min.js

209 ms

datepicker.min.js

datepicker.min.js

210 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

61 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

84 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

120 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

140 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

139 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

141 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

140 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

142 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

140 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

143 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

143 ms

public.js

public.js

209 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

145 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

144 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

146 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

151 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

151 ms

4be96cd6-4192-49c5-97e0-177cddf48b2b-loader.js

4be96cd6-4192-49c5-97e0-177cddf48b2b-loader.js

534 ms

fa-solid-900.woff

fa-solid-900.woff

203 ms

fa-regular-400.woff

fa-regular-400.woff

203 ms

fa-brands-400.woff

fa-brands-400.woff

202 ms

unijauaribe-horizontal-1024x250.png

unijauaribe-horizontal-1024x250.png

200 ms

QR-CODE-E-MEC-1.png

QR-CODE-E-MEC-1.png

180 ms

unijaguaribe.edu.br

unijaguaribe.edu.br

4702 ms

lead-tracking.min.js

lead-tracking.min.js

2 ms

traffic-source-cookie.min.js

traffic-source-cookie.min.js

3 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

6 ms

rdstation-popup.min.js

rdstation-popup.min.js

5 ms

rd-js-integration.min.js

rd-js-integration.min.js

3 ms

Accessibility Review

fvj.br accessibility score

87

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.

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

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

High

Links do not have a discernible name

Best Practices

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

SEO Factors

fvj.br SEO score

89

Search Engine Optimization Advices

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

fvj.br

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