11.9 sec in total
2 sec
9.2 sec
683 ms
Welcome to auniao.pb.gov.br homepage info - get ready to check Auniao Pb best content for Brazil right away, or after learning these important things about auniao.pb.gov.br
Visit auniao.pb.gov.brWe analyzed Auniao.pb.gov.br page load time and found that the first response time was 2 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
auniao.pb.gov.br performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value14.8 s
0/100
25%
Value10.0 s
9/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value18.9 s
3/100
10%
1979 ms
171 ms
49 ms
244 ms
679 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 68% of them (86 requests) were addressed to the original Auniao.pb.gov.br, 12% (15 requests) were made to Scontent.xx.fbcdn.net and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Auniao.pb.gov.br.
Page size can be reduced by 667.8 kB (22%)
3.1 MB
2.4 MB
In fact, the total size of Auniao.pb.gov.br main page is 3.1 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. 40% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 58.3 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 21.4 kB, which is 30% 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 58.3 kB or 82% of the original size.
Potential reduce by 267.2 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. Obviously, Auniao Pb needs image optimization as it can save up to 267.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 139.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 139.6 kB or 66% of the original size.
Potential reduce by 202.7 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. Auniao.pb.gov.br needs all CSS files to be minified and compressed as it can save up to 202.7 kB or 83% of the original size.
Number of requests can be reduced by 59 (48%)
123
64
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Auniao Pb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
auniao.pb.gov.br
1979 ms
all.js
171 ms
plusone.js
49 ms
reset-cachekey-45dd21eab3e3de806bab1de4e8979b4f.css
244 ms
base-cachekey-b27217965ccad01fbe7bf7b761e38392.css
679 ms
resourceplone.app.jquerytools.overlays-cachekey-dbb7095687b9375838a47379cf9e7a41.css
333 ms
resourceplone.formwidget.contenttreecontenttree-cachekey-6f50fd0ce588e3ac3afe7164e12a108f.css
318 ms
resourcecollection-cachekey-9962a2eab6de475e1fdbabf00a257da3.css
374 ms
resourcecalendar_stylescalendar-cachekey-bbb0ef4b4f29388e50487a58ba2cd047.css
489 ms
resourcebrasil.gov.agendaagenda-cachekey-03ae624c8c97966caa6e11fe1571d7e1.css
638 ms
jquery.autocomplete-cachekey-2a57c5afffee9f60919e5839d2d8298a.css
629 ms
resourceProducts.Doormat.stylesheetsdoormat-cachekey-42e7f609523aa536f011b3fac7980bb9.css
646 ms
embedder-cachekey-6f3b9dbd06b1a49e9a25464d62c8ddda.css
789 ms
resourcecollective.nitfcharcount-cachekey-c9076cc6c3186335bf91f4acfccfc285.css
807 ms
ploneCustom-cachekey-cb53fdff2a79618c5e71b548784b00e0.css
1097 ms
resourcecollective.uploadcssbootstrap.min-cachekey-39508616579b105e0738e56776d64d72.css
1090 ms
resourcecollective.covercontentchooser-cachekey-daf649aaf76cac203fdec06832cefed8.css
1026 ms
resourceplone.app.jquery-cachekey-770440bb5e9b6e9f03f288c5961ae88f.js
1790 ms
resourceplone.formwidget.querystring.querywidget-cachekey-c75cf196363e78169bb110b57e9c3544.js
1835 ms
resourceplone.formwidget.contenttreecontenttree-cachekey-37aae37b6ed2f475fe6e4a189d952cea.js
1864 ms
resourcecollective.pollsjspolls-cachekey-8b013b86b8ae43374aaa26210bd5e3a1.js
1940 ms
resourcejquery.cookie-cachekey-ed8aac2ca23d1bee65c8b597cb1b74b2.js
1393 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-59072b701933c040d6f62e8f289c449e.js
1637 ms
banner_rotativo.js
1969 ms
resetPlone.css
2029 ms
resetBootstrap.css
2157 ms
bootstrap.css
2673 ms
bootstrap-responsive.css
2361 ms
base.css
2257 ms
ploneContent.css
2312 ms
uniao.css
2381 ms
font-awesome.min.css
2642 ms
noticias.css
2517 ms
contraste.css
2704 ms
summaryView.css
2662 ms
galeriaDeAlbuns.css
2687 ms
resultadoDeBusca.css
2783 ms
servicospb.css
2903 ms
cb=gapi.loaded_0
79 ms
134 ms
barra_verde.css
2804 ms
colunas.css
2715 ms
navbar.css
2709 ms
header.css
2743 ms
styles_collective_cover.css
2831 ms
collective_cover.css
2925 ms
resetPublic.css
2705 ms
panel_bootstrap.css
2696 ms
listgroup_bootstrap.css
2754 ms
calendario.css
2763 ms
portalsitemap.css
2726 ms
n4nZjPOwZVI
108 ms
logo_topo.png
2190 ms
topo_azul.png
2023 ms
foto_capa1.jpg
2557 ms
barra_nav_pb.png
1762 ms
9743d55e-3777-41d3-a9b2-39dbebf73911.jpeg
2003 ms
061c83ad-e626-41a6-9c6f-e2ab8c34a785.jpeg
2175 ms
e6ad0858-98bf-4d56-9ac0-16fa8753a12e.jpeg
2386 ms
282b5d4b-403b-41ce-877e-dea883c137e3.jpeg
2301 ms
cc5358b5-83f9-4f26-bfa7-acfee0383498.jpeg
2340 ms
2097d732-53a3-4bf0-8c14-cbf80a4d6864.jpeg
2510 ms
bfdc8926-939a-4c4d-bc56-71c95bb4c192.jpeg
2520 ms
www-embed-player-vfl8xM8me.css
62 ms
www-embed-player.js
84 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
44 ms
ad_status.js
36 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
59 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
62 ms
glyphicons-halflings-white.png
1054 ms
bullet-banner-rotativo.gif
1099 ms
shadow-50.png
1214 ms
logo-uniao-123-anos.jpg
1578 ms
memoria.jpg
1764 ms
faca-sua-assinatura.jpg
2075 ms
reserve-seu-anuncio.jpg
2155 ms
arquivos-digitais.jpg
2012 ms
diariooficial.jpg
2193 ms
ilustracoes.jpg
2281 ms
graficos.jpg
2969 ms
parque.jpg
2782 ms
livros.jpg
3023 ms
bannereditoraok.gif
3081 ms
03-colunista-02.png
2751 ms
03-colunista-03.png
2935 ms
03-colunista-04.png
3194 ms
03-colunista-05.png
3421 ms
03-colunista-06.png
3417 ms
facebook.png
3292 ms
instagram.png
3350 ms
twitter.png
3488 ms
you_tube.png
3452 ms
play.png
3781 ms
xd_arbiter.php
124 ms
xd_arbiter.php
256 ms
logo_topo_black.png
3777 ms
like_box.php
157 ms
logo_governo_branco.png
3594 ms
410ucuAGgaJ.css
173 ms
pERLJfhzcxv.css
215 ms
q68gy-v_YMF.js
297 ms
VvsfEObxnnn.js
358 ms
0wM5s1Khldu.js
293 ms
1bNoFZUdlYZ.js
295 ms
logo%20codata-branca.png
3554 ms
spinner.gif
3304 ms
primeira.jpg
1311 ms
11150402_889130641134097_5089858043134818307_n.jpg
278 ms
12027530_955822961131531_4928386035444130239_n.png
358 ms
12509458_516967551840778_2395178419013651243_n.jpg
388 ms
12800112_564132627094746_3605614992292483724_n.jpg
394 ms
1915281_984311168316084_4562829467248842083_n.jpg
452 ms
12670857_934341696660662_5293497253860607921_n.jpg
396 ms
12802980_1686126235002417_2060285977719772304_n.jpg
395 ms
10943107_10202240594496394_6208443477439627747_n.jpg
428 ms
10384343_669123516520005_1518934565918944842_n.jpg
522 ms
527971_362061170538386_876727793_n.jpg
441 ms
12670081_927232584064993_5123039232876109699_n.jpg
475 ms
423597_236635003082277_181838718_n.jpg
483 ms
12821509_571319209697577_9077894464184741064_n.jpg
468 ms
12294781_1425930777421808_2120366263024712142_n.jpg
926 ms
10599120_1674985026097053_8479399723464810368_n.jpg
491 ms
wL6VQj7Ab77.png
52 ms
s7jcwEQH7Sx.png
51 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
81 ms
auniao.pb.gov.br accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
auniao.pb.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
auniao.pb.gov.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Auniao.pb.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 Auniao.pb.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.
auniao.pb.gov.br
Open Graph description is not detected on the main page of Auniao Pb. 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: