11.9 sec in total
710 ms
10.8 sec
390 ms
Welcome to mprj.mp.br homepage info - get ready to check MPRJ Mp best content for Brazil right away, or after learning these important things about mprj.mp.br
Portal do Ministério Público do Estado do Rio de Janeiro.
Visit mprj.mp.brWe analyzed Mprj.mp.br page load time and found that the first response time was 710 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mprj.mp.br performance score
710 ms
1744 ms
135 ms
406 ms
419 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 93% of them (157 requests) were addressed to the original Mprj.mp.br, 2% (4 requests) were made to Google.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Mprj.mp.br.
Page size can be reduced by 685.6 kB (61%)
1.1 MB
435.9 kB
In fact, the total size of Mprj.mp.br main page is 1.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. Javascripts take 502.6 kB which makes up the majority of the site volume.
Potential reduce by 88.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 23.4 kB, which is 22% 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 88.3 kB or 85% of the original size.
Potential reduce by 30.5 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, MPRJ Mp needs image optimization as it can save up to 30.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 347.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 347.6 kB or 69% of the original size.
Potential reduce by 219.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. Mprj.mp.br needs all CSS files to be minified and compressed as it can save up to 219.3 kB or 80% of the original size.
Number of requests can be reduced by 116 (74%)
157
41
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MPRJ Mp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 97 to 1 for CSS and as a result speed up the page load time.
mprj.mp.br
710 ms
www.mprj.mp.br
1744 ms
css
135 ms
main.css
406 ms
visualizacao-internet.css
419 ms
main.css
423 ms
barebone.jsp
1238 ms
main.css
1061 ms
aui.css
359 ms
aui_rtl.css
187 ms
portal_1.css
202 ms
portal_2.css
370 ms
taglib_1.css
394 ms
taglib_2.css
552 ms
openid.css
553 ms
accessibility.css
595 ms
generic_portal.css
491 ms
add_content.css
533 ms
flyout.css
537 ms
panel_component.css
584 ms
panel_pagination.css
642 ms
position_helper.css
674 ms
auto_row.css
712 ms
undo_manager.css
717 ms
panel_page.css
779 ms
javascript_template.css
812 ms
portlet_item.css
827 ms
portlet_css_editor.css
856 ms
portlet_toolbar.css
890 ms
toolbar.css
894 ms
tree.css
1004 ms
uploader.css
1059 ms
page_settings.css
1418 ms
notifications.css
1297 ms
asset_category_selector.css
933 ms
asset_column.css
941 ms
tag_selector.css
1029 ms
generic_portlet.css
1089 ms
forms.css
1112 ms
header_row.css
1118 ms
preview.css
1207 ms
rich_editor.css
1276 ms
search_combobox.css
1282 ms
separator.css
1286 ms
top_links.css
1392 ms
translation_manager.css
1449 ms
asset_categories_summary.css
1346 ms
asset_links.css
1318 ms
calendar.css
1295 ms
captcha.css
1398 ms
categorization_filter.css
1349 ms
diff.css
1374 ms
diff_html.css
1328 ms
discussion.css
1325 ms
flags.css
1316 ms
form_navigator.css
1379 ms
header.css
1369 ms
icon.css
1386 ms
icon_help.css
1348 ms
icon_list.css
1351 ms
icon_menu.css
1318 ms
input_localized.css
1391 ms
input_move_boxes.css
1385 ms
input_repeat.css
1378 ms
language.css
1344 ms
logo_selector.css
1358 ms
preview.css
1287 ms
ratings.css
1320 ms
search_iterator.css
1299 ms
search_toggle.css
1308 ms
social_activities.css
1220 ms
social_bookmarks.css
1182 ms
tags_summary.css
1211 ms
user_display.css
1287 ms
webdav.css
1213 ms
workflow_status.css
1151 ms
main.js
1347 ms
ga.js
131 ms
base.css
230 ms
application.css
222 ms
layout.css
187 ms
dockbar.css
233 ms
navigation.css
230 ms
portlet.css
205 ms
forms.css
375 ms
extras.css
383 ms
custom.css
395 ms
cadeado.png
405 ms
__utm.gif
72 ms
bt_facebook.png
229 ms
bt_twitter.png
231 ms
bt_youtube.png
378 ms
bt_flickr.png
387 ms
icon.png
409 ms
image_gallery
3327 ms
image_gallery
646 ms
image_gallery
858 ms
image_gallery
2058 ms
image_gallery
806 ms
image_gallery
858 ms
journal_content.png
854 ms
banner_concurso.png
1043 ms
banner_consulta.png
1067 ms
banner_recad.png
1080 ms
banner_revista.png
1080 ms
banner_biblioteca.png
1659 ms
banner_valid.png
1319 ms
banner_XXXIV_Concurso_versao2.png
1537 ms
article
2857 ms
article
1665 ms
article
1865 ms
article
1965 ms
article
2193 ms
article
2229 ms
banner_home_plid.jpg
2200 ms
banner_home_consumidor_vencedor.jpg
3078 ms
image3.png
2415 ms
banner_home_mediacao.jpg
3411 ms
image.png
2473 ms
banner_home_msm_0.jpg
2631 ms
banner_home_nome_do_pai.jpg
2686 ms
collect
264 ms
joao_cidadao.png
2703 ms
camp_corrup.png
2750 ms
custom_common.css
2845 ms
custom_dock.css
2873 ms
custom_dockbar.css
2947 ms
custom_navigation.css
3039 ms
custom_navegvertical.css
2915 ms
custom_layout_tpl.css
3300 ms
custom_webcontent.css
2957 ms
custom_journal.css
2820 ms
custom_breadcrumb.css
2672 ms
comum.css
2666 ms
padrao.css
2708 ms
destaques.css
2780 ms
camp_viol.png
2816 ms
camp_comp.png
2977 ms
link_cnmp.png
2700 ms
link_cnpg.png
2720 ms
link_femperj.png
2524 ms
link_amperj.png
2544 ms
link_conamp.png
2342 ms
link_coomperj.png
2354 ms
link_pj.png
2193 ms
link_assemperj.png
2109 ms
link_camperj.png
2256 ms
footer-facebook.png
2104 ms
footer-twitter.png
2117 ms
footer-youtube.png
2109 ms
footer-flickr.png
2278 ms
cse.js
163 ms
dock_bg.png
982 ms
logo_mp.png
1898 ms
topo_bg.png
1016 ms
menu.png
826 ms
article
1131 ms
bullet.png
1011 ms
divisoria-areas.png
1147 ms
prev.png
1169 ms
next.png
1169 ms
widget-base.css
1152 ms
jsapi
81 ms
default+pt_PT.css
56 ms
default.css
112 ms
default+pt_PT.I.js
527 ms
default.css
346 ms
1 ms
mprj.mp.br SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mprj.mp.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 Mprj.mp.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.
mprj.mp.br
Open Graph description is not detected on the main page of MPRJ Mp. 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: