Tools & Wizards About Us
processual.trf1.gov.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

processual.trf1.gov.br

TRF1 - Consulta Processual

Page Load Speed

3.6 sec in total

First Response

1.2 sec

Resources Loaded

2.3 sec

Page Rendered

106 ms

processual.trf1.gov.br screenshot

About Website

Welcome to processual.trf1.gov.br homepage info - get ready to check Processual TRF1 best content for Brazil right away, or after learning these important things about processual.trf1.gov.br

Visit processual.trf1.gov.br

Key Findings

We analyzed Processual.trf1.gov.br page load time and found that the first response time was 1.2 sec and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

processual.trf1.gov.br performance score

0

Network Requests Diagram

processual.trf1.gov.br

1197 ms

screen.css

173 ms

template_css.css

358 ms

index.css

345 ms

jquery-1.6.1.min.js

543 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 89% of them (17 requests) were addressed to the original Processual.trf1.gov.br, 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Processual.trf1.gov.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.6 kB (69%)

Content Size

444.7 kB

After Optimization

137.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Processual.trf1.gov.br main page is 444.7 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. 20% of websites need less resources to load. Javascripts take 346.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 15.2 kB

  • Original 18.3 kB
  • After minification 11.1 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 39% 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 15.2 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 1.1 kB

  • Original 17.9 kB
  • After minification 16.8 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. Processual TRF1 images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 240.7 kB

  • Original 346.6 kB
  • After minification 326.4 kB
  • After compression 105.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 240.7 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 50.7 kB

  • Original 62.0 kB
  • After minification 50.7 kB
  • After compression 11.3 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. Processual.trf1.gov.br needs all CSS files to be minified and compressed as it can save up to 50.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (56%)

Requests Now

18

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

processual.trf1.gov.br

processual.trf1.gov.br

1197 ms

screen.css

screen.css

173 ms

template_css.css

template_css.css

358 ms

index.css

index.css

345 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

543 ms

jquery-ui-1.8.13.custom.css

jquery-ui-1.8.13.custom.css

355 ms

jquery-ui-1.8.13.custom.min.js

jquery-ui-1.8.13.custom.min.js

718 ms

jquery.crypt.js

jquery.crypt.js

348 ms

Cookie.js

Cookie.js

512 ms

jquery.fontResize.js

jquery.fontResize.js

514 ms

index.js

index.js

519 ms

__afundo.jpg

__afundo.jpg

167 ms

logo.jpg

logo.jpg

169 ms

path-arrow.png

path-arrow.png

163 ms

sombrarodape.jpg

sombrarodape.jpg

172 ms

ajax-loader_1.gif

ajax-loader_1.gif

167 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

13 ms

print.css

print.css

171 ms

SEO Factors

processual.trf1.gov.br SEO score

0

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 Processual.trf1.gov.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 Processual.trf1.gov.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

processual.trf1.gov.br

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