14.1 sec in total
3.5 sec
10.3 sec
351 ms
Click here to check amazing Ii Pr content for Brazil. Otherwise, check out these important facts you probably never knew about ii.pr.gov.br
Atividades Identificação civil Conforme Lei Federal n° 7.116/83, o Instituto de Identificação do Paraná realiza a Identificação Civil e respectiva expedição da Carteira de Identidade para Brasileiro...
Visit ii.pr.gov.brWe analyzed Ii.pr.gov.br page load time and found that the first response time was 3.5 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ii.pr.gov.br performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value9.7 s
0/100
25%
Value15.3 s
1/100
10%
Value190 ms
91/100
30%
Value0.86
4/100
15%
Value12.7 s
13/100
10%
3466 ms
732 ms
937 ms
58 ms
1044 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ii.pr.gov.br, 57% (32 requests) were made to Policiacivil.pr.gov.br and 25% (14 requests) were made to Web.celepar.pr.gov.br. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Policiacivil.pr.gov.br.
Page size can be reduced by 384.2 kB (7%)
5.3 MB
5.0 MB
In fact, the total size of Ii.pr.gov.br main page is 5.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. 50% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 100.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 16.6 kB, which is 13% 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 100.9 kB or 81% of the original size.
Potential reduce by 149.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. Ii Pr images are well optimized though.
Potential reduce by 2.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 131.0 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. Ii.pr.gov.br needs all CSS files to be minified and compressed as it can save up to 131.0 kB or 61% of the original size.
Number of requests can be reduced by 16 (33%)
48
32
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ii Pr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ii.pr.gov.br
3466 ms
732 ms
IIPR
937 ms
js
58 ms
styles.css
1044 ms
css_MSH3okZtl2fOqn1ktTkraSozZCYwGhiFqn30LPB4C_U.css
528 ms
css_nARJieF9IuQh1LLFpV0EAp2DrA9tcvltWYdejtPPw7I.css
401 ms
gerais.css
540 ms
css_BxK_YPFf1iB3cBzF_VS9ZSNvoQf3r67wm_4bY8jrS4s.css
406 ms
inst-bar.min.css
548 ms
vlibras-plugin.js
470 ms
js_ShFTxs5-LEgXxTlfpJR80DQdNegDylxJLrYIN9Dvyfk.js
655 ms
page.js
33 ms
js_kvupmB8c_oJSGhW3pt3G9INsCSdKPn-KCpLNMC3kreY.js
397 ms
iframe_api
48 ms
inst-bar.js
283 ms
js_UKRouNQ7AYTp5ji86ZFq6L4Weju9yIBlIYqNxNNI80A.js
410 ms
vlibras-plugin.js
24 ms
pr-gov-pr-bg-barra.png
270 ms
identificacao_civil_0.jpg
1440 ms
coleta_criminal_0.jpg
1068 ms
necropapiloscopia.jpg
1328 ms
pericia_rg_0.jpg
1849 ms
local_de_crime_0.jpg
2238 ms
pericia_em_laboratorio.jpg
2236 ms
retrato_falado.jpg
2894 ms
ft-michelotto.jpg
1982 ms
ft-fabio-tadeu.jpg
2136 ms
pr-gov-br-logo.png
232 ms
pr-gov-br-redes-sociais.png
232 ms
inst-bar-icon-libras.png
234 ms
logo-pcpr-240x99.png
457 ms
pia_logo_142x47.png
421 ms
pia_logo_142x47_branco.png
423 ms
icon_twitter_x_brnc.svg
551 ms
bg-servicos-destaques-cinza.jpg
671 ms
logo_parana_113x99_texto_branco.png
549 ms
logo_celepar_88x28_branco.png
551 ms
sm.25.html
171 ms
eso.BRQnzO8v.js
172 ms
www-widgetapi.js
170 ms
fa-solid-900.woff
2509 ms
fa-regular-400.woff
2122 ms
glyphicons-halflings-regular.woff
2425 ms
fa-brands-400.woff
2769 ms
identificacao_civil_0.jpg
2930 ms
coleta_criminal_0.jpg
3016 ms
necropapiloscopia.jpg
3172 ms
pericia_rg_0.jpg
3397 ms
local_de_crime_0.jpg
3646 ms
pericia_em_laboratorio.jpg
3668 ms
retrato_falado.jpg
3921 ms
ft-michelotto.jpg
3428 ms
ft-fabio-tadeu.jpg
3621 ms
icons.38.svg.js
39 ms
css_bzYDSkcZ1eaGEaO60QdZho7Qm2o8WgktEQ3Ic9XlZ0o.css
138 ms
ii.pr.gov.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
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
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
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
ii.pr.gov.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ii.pr.gov.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Ii.pr.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 Ii.pr.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.
ii.pr.gov.br
Open Graph data is detected on the main page of Ii Pr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: