6.6 sec in total
828 ms
5.2 sec
622 ms
Click here to check amazing Drei Smpe content for Brazil. Otherwise, check out these important facts you probably never knew about drei.smpe.gov.br
Visit drei.smpe.gov.brWe analyzed Drei.smpe.gov.br page load time and found that the first response time was 828 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
drei.smpe.gov.br performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value13.6 s
0/100
25%
Value14.3 s
1/100
10%
Value530 ms
55/100
30%
Value0.002
100/100
15%
Value22.0 s
1/100
10%
828 ms
94 ms
54 ms
293 ms
582 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 62% of them (39 requests) were addressed to the original Drei.smpe.gov.br, 13% (8 requests) were made to Apis.google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Drei.smpe.gov.br.
Page size can be reduced by 83.6 kB (18%)
469.0 kB
385.4 kB
In fact, the total size of Drei.smpe.gov.br main page is 469.0 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. 60% of websites need less resources to load. Images take 369.5 kB which makes up the majority of the site volume.
Potential reduce by 44.9 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 11.1 kB, which is 20% 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 44.9 kB or 80% of the original size.
Potential reduce by 10.4 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. Drei Smpe images are well optimized though.
Potential reduce by 19.2 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 19.2 kB or 59% of the original size.
Potential reduce by 9.1 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. Drei.smpe.gov.br needs all CSS files to be minified and compressed as it can save up to 9.1 kB or 85% of the original size.
Number of requests can be reduced by 34 (59%)
58
24
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drei Smpe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
drei.smpe.gov.br
828 ms
all.js
94 ms
plusone.js
54 ms
reset-cachekey-50edeb4af5fcc5a872c02d673bb9d225.css
293 ms
base-cachekey-ab41b4b0043b1ac71fe37027c9936f3e.css
582 ms
resourceplone.app.jquerytools.dateinput-cachekey-58abc32cdc8b2aefb158f9f1dac89c02.css
359 ms
resourceplone.formwidget.querystring.querywidget-cachekey-82e2dfbb94af06924ad8908cbbce9f50.css
360 ms
embedder-cachekey-251e51a07c24e4d10b3fb583ef1e5ce9.css
449 ms
ploneCustom-cachekey-5c84103893a67ee8f8a1f62cdc613030.css
476 ms
resourcebrasil.gov.tilestiles-cachekey-86c9d172c659ccbd046d8080176a2ed0.css
1129 ms
resourcebrasil.gov.barracssmain-cachekey-cbe1f3338d45dd41805de8d85c3f5994.css
597 ms
resourcebrasil.gov.agendaagenda-cachekey-4940672a3b92e3c9d9dfca74f9a24e0d.css
597 ms
resourceplone.app.jquery-cachekey-11b5f846f615b0ceaf5979cc402a9cc2.js
1674 ms
collective.js.jqueryui.custom.min-cachekey-9709337e1f18c371eac6d51f9ced3a2b.js
1778 ms
resourceplone.formwidget.contenttreecontenttree-cachekey-3a81a7d172a640ec08a78ee0a8a3b545.js
2202 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-1e7906ab452b2e3104b090db31aff070.js
1058 ms
resourcecollective.nitfnitf_fixes-cachekey-526bdfef69aa428bf436f20292426c1d.js
1079 ms
resourcecollective.pollsjspolls-cachekey-19b506638e9fab42085c9aef9f244cb0.js
1336 ms
resourcejquery.cookie-cachekey-777f4e1ca6de1ca42c8d46e9bb4f7fef.js
2201 ms
style.css
1391 ms
cb=gapi.loaded_0
83 ms
resourceplone.formwidget.autocompletejquery.autocomplete-cachekey-e579b170dd809eaed7b8ea8ed931199a.css
1422 ms
jquery.autocomplete-cachekey-7f18a95ef73971305e255417c1d26f44.css
1489 ms
resourceProducts.Doormat.stylesheetsdoormat-cachekey-ec607d452bc228a721f3d0e699e6c608.css
1814 ms
resourcecollective.nitfcharcount-cachekey-302174c705b3ce37b0f604104148cbe5.css
1816 ms
resourcecollective.uploadcssbootstrap.min-cachekey-87162c37c93f501527fb7904e096245b.css
2177 ms
resourcecalendar_stylescalendar-cachekey-2b656dd57d39dbb2f3d354d3af87d4fa.css
1915 ms
164 ms
opensans-400-webfont.woff
483 ms
sprite.png
599 ms
smpe-e-jcacre
1061 ms
90d8faa3-e988-4f50-be4c-e27ea18b8d9d.png
808 ms
241355d1-8cac-4825-b50a-0e49510e88ef.jpeg
595 ms
550a5c9c-9a9a-4adf-b6ad-2303f3fb1a12.png
691 ms
acesso-a-infornacao.png
692 ms
brasil.png
806 ms
widgets.js
111 ms
seta_verde.png
650 ms
voltar-topo.png
782 ms
opensans-800-webfont.woff
916 ms
opensans-700-webfont.woff
1058 ms
piwik.js
942 ms
xd_arbiter.php
382 ms
xd_arbiter.php
453 ms
destaques
614 ms
cb=gapi.loaded_1
133 ms
fastbutton
139 ms
spinner.gif
525 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
171 ms
cb=gapi.loaded_0
83 ms
cb=gapi.loaded_1
83 ms
postmessageRelay
81 ms
like.php
96 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
129 ms
3193398744-postmessagerelay.js
101 ms
rpc:shindig_random.js
60 ms
tweet_button.64a917b4a230f163048902c783e1530f.pt.html
71 ms
IwXbtdSywuX.js
180 ms
LVx-xkvaJ0b.png
215 ms
cb=gapi.loaded_0
12 ms
jot
125 ms
b637c1c3-5818-49df-b9aa-48ca7d0e0019.jpeg
607 ms
piwik.php
619 ms
drei.smpe.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
Links do not have a discernible name
drei.smpe.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
drei.smpe.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
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 Drei.smpe.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 Drei.smpe.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.
drei.smpe.gov.br
Open Graph description is not detected on the main page of Drei Smpe. 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: