Tools & Wizards About Us
dataprev.gov.br screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

dataprev.gov.br

Dataprev | Empresa de Tecnologia e Informações da Previdência

Page Load Speed

4.5 sec in total

First Response

526 ms

Resources Loaded

3.7 sec

Page Rendered

311 ms

dataprev.gov.br screenshot

About Website

Click here to check amazing Dataprev content for Brazil. Otherwise, check out these important facts you probably never knew about dataprev.gov.br

Soluções digitais para governo e cidadão

Visit dataprev.gov.br

Key Findings

We analyzed Dataprev.gov.br page load time and found that the first response time was 526 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

dataprev.gov.br performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

dataprev.gov.br

526 ms

dataprev.gov.br

958 ms

font-awesome.css

281 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

430 ms

css_ofp4IzTomZmezOM1ndPbukhkdsr-Z7NP-w4__X0aPcM.css

572 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Dataprev.gov.br, 8% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ew.dataprev.gov.br. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dataprev.gov.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (33%)

Content Size

3.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dataprev.gov.br main page is 3.8 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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 43.6 kB

  • Original 53.6 kB
  • After minification 48.5 kB
  • After compression 10.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.6 kB or 81% of the original size.

Image Optimization

-32%

Potential reduce by 1.1 MB

  • Original 3.5 MB
  • After minification 2.4 MB

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, Dataprev needs image optimization as it can save up to 1.1 MB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-43%

Potential reduce by 65.0 kB

  • Original 151.4 kB
  • After minification 151.4 kB
  • After compression 86.4 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 65.0 kB or 43% of the original size.

CSS Optimization

-37%

Potential reduce by 31.1 kB

  • Original 83.3 kB
  • After minification 76.9 kB
  • After compression 52.2 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. Dataprev.gov.br needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (30%)

Requests Now

44

After Optimization

31

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dataprev. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dataprev.gov.br

dataprev.gov.br

526 ms

dataprev.gov.br

dataprev.gov.br

958 ms

font-awesome.css

font-awesome.css

281 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

430 ms

css_ofp4IzTomZmezOM1ndPbukhkdsr-Z7NP-w4__X0aPcM.css

css_ofp4IzTomZmezOM1ndPbukhkdsr-Z7NP-w4__X0aPcM.css

572 ms

css_tDKTWIfQsbS6gl2SyQ94QlBhrnPhFE-WG6TI5pZLHNU.css

css_tDKTWIfQsbS6gl2SyQ94QlBhrnPhFE-WG6TI5pZLHNU.css

577 ms

css_EZt1rW4UO4cCFd2kd8BikwcAGLAM_VYpAKkVMDSMMbg.css

css_EZt1rW4UO4cCFd2kd8BikwcAGLAM_VYpAKkVMDSMMbg.css

579 ms

css_lryttRT32k2XKNdZAC_amdZnnL0EuamONchI69sv8xM.css

css_lryttRT32k2XKNdZAC_amdZnnL0EuamONchI69sv8xM.css

739 ms

css_ZB9tWBIkUge5AVipzoa6qi8MVGRbwhnng11PwjVcjes.css

css_ZB9tWBIkUge5AVipzoa6qi8MVGRbwhnng11PwjVcjes.css

579 ms

js_6wB7_RH3hNT_viZwOlvXgQ7bvciK-Mir9CVHAkENV64.js

js_6wB7_RH3hNT_viZwOlvXgQ7bvciK-Mir9CVHAkENV64.js

600 ms

js_Y-NoBrOMYkaPzn-HPy1yuSwjKzH5JvCDWfr0GAxvSbE.js

js_Y-NoBrOMYkaPzn-HPy1yuSwjKzH5JvCDWfr0GAxvSbE.js

732 ms

js_TLbyT18zH5pGOKSqe0BZ-9Y82U_J-e_v58Ih650sUWA.js

js_TLbyT18zH5pGOKSqe0BZ-9Y82U_J-e_v58Ih650sUWA.js

726 ms

js_EYu9K4AQLbJwAwV8VIGv6NFNV6SzjBDag5bfnSR0wAE.js

js_EYu9K4AQLbJwAwV8VIGv6NFNV6SzjBDag5bfnSR0wAE.js

725 ms

js_LDvwfbUvwZW7DnZG2m1INeZlgPLf9L-6w_e0LeeUKls.js

js_LDvwfbUvwZW7DnZG2m1INeZlgPLf9L-6w_e0LeeUKls.js

736 ms

js_MRdvkC2u4oGsp5wVxBG1pGV5NrCPW3mssHxIn6G9tGE.js

js_MRdvkC2u4oGsp5wVxBG1pGV5NrCPW3mssHxIn6G9tGE.js

740 ms

css2

css2

42 ms

btfaleconosco.png

btfaleconosco.png

142 ms

icon-contraste-cor.png

icon-contraste-cor.png

143 ms

icon-vlibras-cor.png

icon-vlibras-cor.png

153 ms

marcadataprev_topo.png

marcadataprev_topo.png

153 ms

microsoftteams-image_330.png

microsoftteams-image_330.png

1524 ms

portal_dc_home.jpg

portal_dc_home.jpg

1107 ms

factsheet_imagem_noc_portal_home.jpg

factsheet_imagem_noc_portal_home.jpg

423 ms

microsoftteams-image_350_0.png

microsoftteams-image_350_0.png

836 ms

portal_meu_inss_nova_0.png

portal_meu_inss_nova_0.png

700 ms

microsoftteams-image_322.png

microsoftteams-image_322.png

1389 ms

icon-home1.png

icon-home1.png

566 ms

icon-home2.png

icon-home2.png

712 ms

icon-home3.png

icon-home3.png

844 ms

icon-home4.png

icon-home4.png

856 ms

dc_tieriii.png

dc_tieriii.png

977 ms

dc_ceeda.png

dc_ceeda.png

984 ms

banner01_premiacoes_0.jpg

banner01_premiacoes_0.jpg

1001 ms

banner02_responsabilidade_0.jpg

banner02_responsabilidade_0.jpg

1123 ms

banner03_ouvidoria_1.jpg

banner03_ouvidoria_1.jpg

1131 ms

grafismo_rodape1.png

grafismo_rodape1.png

1143 ms

marcadataprev_rodape.png

marcadataprev_rodape.png

1246 ms

redes_facebook.png

redes_facebook.png

1263 ms

redes_twitterx.png

redes_twitterx.png

1273 ms

redes_youtube.png

redes_youtube.png

1285 ms

redes_linkedin.png

redes_linkedin.png

1390 ms

redes_instagram.png

redes_instagram.png

1404 ms

acesso_informacao.png

acesso_informacao.png

1414 ms

matomo.js

matomo.js

1014 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_qU7NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_qU7NSg.ttf

21 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_m07NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_m07NSg.ttf

27 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_907NSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_907NSg.ttf

45 ms

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_TknNSg.ttf

LDIbaomQNQcsA88c7O9yZ4KMCoOg4IA6-91aHEjcWuA_TknNSg.ttf

46 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1356 ms

icon-menu-cor.png

icon-menu-cor.png

1447 ms

matomo.php

matomo.php

178 ms

Accessibility Review

dataprev.gov.br accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

dataprev.gov.br best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dataprev.gov.br SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dataprev.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 Dataprev.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.

Social Sharing Optimization

dataprev.gov.br

Open Graph data is detected on the main page of Dataprev. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: