7.5 sec in total
1.3 sec
5.8 sec
396 ms
Welcome to servidor.gov.br homepage info - get ready to check Servidor best content for Brazil right away, or after learning these important things about servidor.gov.br
Visit servidor.gov.brWe analyzed Servidor.gov.br page load time and found that the first response time was 1.3 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
servidor.gov.br performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value19.1 s
0/100
25%
Value16.2 s
0/100
10%
Value640 ms
46/100
30%
Value0.187
65/100
15%
Value15.9 s
6/100
10%
1300 ms
585 ms
745 ms
289 ms
444 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Servidor.gov.br, 81% (54 requests) were made to Www.gov.br and 6% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Www.gov.br.
Page size can be reduced by 212.6 kB (16%)
1.3 MB
1.1 MB
In fact, the total size of Servidor.gov.br main page is 1.3 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. 75% 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 620.4 kB which makes up the majority of the site volume.
Potential reduce by 208.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. This page needs HTML code to be minified as it can gain 69.5 kB, which is 29% 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 208.7 kB or 88% of the original size.
Potential reduce by 0 B
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. Servidor images are well optimized though.
Potential reduce by 133 B
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.
Potential reduce by 3.8 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. Servidor.gov.br has all CSS files already compressed.
Number of requests can be reduced by 43 (84%)
51
8
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Servidor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
servidor.gov.br
1300 ms
servidor.gov.br
585 ms
pt-br
745 ms
resourcejquery-cachekey-e4a84c1d8445b2035fc29b5c7c5b34c3.css
289 ms
reset-cachekey-a24b577d22ec799028e98d99440bc79d.css
444 ms
base-cachekey-c2b1437d2abd08d1b27a2dded14e829d.css
437 ms
resourceplone.app.jquerytools.dateinput-cachekey-2c4ab2ed213500324e1d088e7009b9c8.css
445 ms
resourceplone.formwidget.datetimestyles-cachekey-004575324e8adc61e5921b50dd410711.css
447 ms
jquery.autocomplete-cachekey-a7e065c730e0e8efd610c2e1e13320b8.css
445 ms
embedder-cachekey-2e8b328e1db4991e84036ce901b5117a.css
446 ms
resourcecollective.pollscsscollective.polls-cachekey-0b4c1bf3fccc042ad923c4036d69f18d.css
581 ms
ploneCustom-cachekey-f1d2800fea53228d97b04f5a96446610.css
584 ms
resourcebrasil.gov.newfieldcomplementbootstrap_table-cachekey-46e5c084289734eaab7ab0fa78063e3b.css
582 ms
resourcepas.plugins.loginunicologinunico-cachekey-09e02052a4c4a64d652dbcff96734cb3.css
583 ms
swiper.min.css
44 ms
resourcelgpd.plugindsgov.min-cachekey-662e91f0a07125fb72bcb29c73c20923.css
880 ms
resourcegovbr.policycanais-cachekey-6131574caa55394a17988f822044bb37.css
584 ms
govbr.recom.9e3eea160cd9e43452ac.js
730 ms
resourceplone.app.jquery-cachekey-fe6d5f0e034e41e521ab3b0fcd294524.js
875 ms
resourcegovbr.policyfolder_contents-cachekey-0c1fc23624381cbead5d2b1bf7908622.js
726 ms
resourcegovbr.policycookiebar_1_3_55-cachekey-7c2cddd6e04ed661fd6b97b01e32e716.js
727 ms
resourcegovbr.policyapplication_cookiebar_1_3_55-cachekey-cfdf8534b9236ce408620c9e7ade2d50.js
728 ms
collective.js.jqueryui.custom.min-cachekey-315596613c00eac653be80e82d7d3f53.js
1311 ms
resourceplone.formwidget.recurrencejquery.tmpl-beta1-cachekey-4041a0aa49ac9597b5ba093e2881d23e.js
1021 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-01b0907d73e95bf6f8dc238c7a0cbd34.js
873 ms
resourcecollective.coverjsmain-cachekey-c3f3e343fd387cbdba1a3d27f258352d.js
876 ms
resourcebrasil.gov.tilesvendorjquery.jplayer.min-cachekey-025f7a4d9088ffde8252de5ed2e38b8b.js
1167 ms
resourcedropdown-menu-cachekey-977a45f14cffa773bae09e88f54440c3.js
1172 ms
resourcebrasil.gov.newfieldcomplementnewfieldcomplement-cachekey-0c6a075ce3a4659725c075fc435b0bdb.js
1023 ms
swiper.min.js
33 ms
resourcelgpd.pluginchangeCookieImage-cachekey-d6fec540b1353dd1da924e50a00ef928.js
1023 ms
resourcelgpd.pluginblock_cookies-cachekey-b31e5ed2a20b5b92db7a6f4c2d636437.js
1164 ms
resourcegovbr.policyclipboard.min-cachekey-b6dd7443028982e82d0bdb2110f5130d.js
1167 ms
themegovbr.institucionaljslistar_autoridades_eagenda-cachekey-9900a047f04c12d3ada1b419c2c261a1.js
1166 ms
brasilgovagenda-720c34e.css
1404 ms
brasilgovagenda-720c34e.js
1462 ms
brasilgovportal-ee510e4.css
1407 ms
brasilgovportal-ee510e4.js
1407 ms
brasilgovtiles-7d5753d.css
1409 ms
brasilgovtiles-7d5753d.js
1460 ms
all.css
40 ms
vlibras-plugin.js
468 ms
govbrtheme-71a7413.css
1905 ms
sso-status-bar.js
1183 ms
lgpd_cookie_handling_1_3_87.js
1029 ms
govbrtheme-71a7413.js
1324 ms
vlibras-plugin.js
48 ms
govbr-logo-large.png
430 ms
d36ae4e3-e628-4e08-825a-513c23051f09.png
1171 ms
1b2f3366-54a6-403a-be79-59b44c0e0387.jpeg
475 ms
rawline-400.woff
437 ms
rawline-500.woff
436 ms
rawline-300.woff
632 ms
rawline-200.woff
563 ms
rawline-100.woff
717 ms
rawline-600.woff
883 ms
rawline-700.woff
883 ms
rawline-800.woff
1001 ms
rawline-900.woff
884 ms
fa-solid-900.ttf
102 ms
fa-regular-400.ttf
103 ms
govbr.png
822 ms
fa-brands-400.ttf
285 ms
update.min.js
70 ms
spinner.gif
614 ms
update.show.min.js
18 ms
f.png
349 ms
servidor.gov.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
servidor.gov.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
servidor.gov.br SEO score
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
Document uses legible font sizes
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Servidor.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 Servidor.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.
servidor.gov.br
Open Graph description is not detected on the main page of Servidor. 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: