ipeadata.gov.br Website Information

Daily Unique Visits: 3,544

Daily Page Views: 14,176

Income Per Day: $40

Estimated Value: $21,600

This website is located in Brazil and is using following IP address 177.15.131.189. See the complete list of popular websites hosted in Brazil.

ipeadata.gov.br is registered under .BR top-level domain. Please check other sites in .BR zone.

Website ipeadata.gov.br is using the following name servers:

ns1.ipea.gov.br
ns2.ipea.gov.br

and is probably hosted by Associacao GigaCandanga, BR. See the full list of other websites hosted by Associacao GigaCandanga, BR.

The highest website ipeadata.gov.br position in Alexa rank database was 13317 and the lowest rank position was 997195. Current position of ipeadata.gov.br in Alexa rank database is 354144.

Desktop speed score of ipeadata.gov.br (69/100) is better than the results of 49.24% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of ipeadata.gov.br (60/100) is better than the results of 3.95% of other sites and means that the page is not mobile-friendly.

Mobile speed score of ipeadata.gov.br (56/100) is better than the results of 45.93% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

ipeadata.gov.br Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

ipeadata.gov.br whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the Use and Privacy Policy at https://registro.br/upp ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2024-10-18T21:30:29-03:00 - IP: 167.99.102.248

% Permission denied. For more information, contact abuse@registro.br

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to cert@cert.br
% and mail-abuse@cert.br
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, CIDR block, IP and ASN.

ipeadata.gov.br server information

Servers Location

ipeadata.gov.br desktop page speed rank

Last tested: 2018-01-29

Desktop Speed Medium

69/100

ipeadata.gov.br Desktop Speed Test Quick Summary

priority - 18Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://ipeadata.gov.br/barragov/barra.js (expiration not specified)
http://ipeadata.gov.br/css/estilos.css (expiration not specified)
http://ipeadata.gov.br/img/arrow.gif (expiration not specified)
http://ipeadata.gov.br/img/bgBtnOperacoes.png (expiration not specified)
http://ipeadata.gov.br/img/ico_contato.gif (expiration not specified)
http://ipeadata.gov.br/img/ico_desmarcar.png (expiration not specified)
http://ipeadata.gov.br/img/ico_exibir.png (expiration not specified)
http://ipeadata.gov.br/img/ico_exportar.png (expiration not specified)
http://ipeadata.gov.br/img/ico_exportarcsving.png (expiration not specified)
http://ipeadata.gov.br/img/ico_exportarcsvport.png (expiration not specified)
http://ipeadata.gov.br/img/ico_exportarzip.png (expiration not specified)
http://ipeadata.gov.br/img/ico_home.gif (expiration not specified)
http://ipeadata.gov.br/img/ico_imprimir.png (expiration not specified)
http://ipeadata.gov.br/img/ico_inglaterra.jpg (expiration not specified)
http://ipeadata.gov.br/img/ico_mapa.gif (expiration not specified)
http://ipeadata.gov.br/img/ico_operar.png (expiration not specified)
http://ipeadata.gov.br/img/ico_pesquisar.gif (expiration not specified)
http://ipeadata.gov.br/img/loading.gif (expiration not specified)
http://ipeadata.gov.br/img/logo.gif (expiration not specified)
http://ipeadata.gov.br/img/logo_ipea.gif (expiration not specified)
http://ipeadata.gov.br/img/mnu_ipeadata.gif (expiration not specified)
http://ipeadata.gov.br/img/mnu_macroeconomico.gif (expiration not specified)
http://ipeadata.gov.br/img/mnu_regional.gif (expiration not specified)
http://ipeadata.gov.br/img/mnu_social.gif (expiration not specified)
http://ipeadata.gov.br/img/sep_pontilhado.gif (expiration not specified)
http://ipeadata.gov.br/img/thumb_macroeconomico_h.gif (expiration not specified)
http://ipeadata.gov.br/img/thumb_regional_h.gif (expiration not specified)
http://ipeadata.gov.br/img/thumb_social_h.gif (expiration not specified)
http://ipeadata.gov.br/img/tit_macroeconomico_h.gif (expiration not specified)
http://ipeadata.gov.br/img/tit_regional_h.gif (expiration not specified)
http://ipeadata.gov.br/img/tit_social_h.gif (expiration not specified)
http://ipeadata.gov.br/jscripts/ipeanet.js (expiration not specified)
http://ipeadata.gov.br/jscripts/menu.js (expiration not specified)
http://ipeadata.gov.br/jscripts/milonic_src.js (expiration not specified)
http://ipeadata.gov.br/jscripts/mmenudom.js (expiration not specified)

priority - 14Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 136.6KiB (78% reduction).

Compressing http://ipeadata.gov.br/Default.aspx could save 57.2KiB (83% reduction).
Compressing http://ipeadata.gov.br/jscripts/menu.js could save 28.1KiB (85% reduction).
Compressing http://ipeadata.gov.br/jscripts/mmenudom.js could save 18.4KiB (64% reduction).
Compressing http://ipeadata.gov.br/css/estilos.css could save 13.9KiB (86% reduction).
Compressing http://ipeadata.gov.br/jscripts/ipeanet.js could save 12KiB (80% reduction).
Compressing http://ipeadata.gov.br/jscripts/milonic_src.js could save 2.5KiB (54% reduction).
Compressing http://ipeadata.gov.br/Princ_i.aspx could save 2.4KiB (71% reduction).
Compressing http://ipeadata.gov.br/barragov/barra.js could save 2KiB (45% reduction).

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://ipeadata.gov.br/jscripts/ipeanet.js
http://ipeadata.gov.br/jscripts/milonic_src.js
http://ipeadata.gov.br/jscripts/menu.js
http://ipeadata.gov.br/jscripts/mmenudom.js
http://ipeadata.gov.br/barragov/barra.js

Optimize CSS Delivery of the following:

http://ipeadata.gov.br/css/estilos.css

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

68.7KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 1 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 45% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 13KiB (28% reduction).

Minifying http://ipeadata.gov.br/jscripts/menu.js could save 9.1KiB (28% reduction).
Minifying http://ipeadata.gov.br/jscripts/ipeanet.js could save 3.9KiB (27% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 8.5KiB (12% reduction).

Minifying http://ipeadata.gov.br/Default.aspx could save 7.6KiB (12% reduction).
Minifying http://ipeadata.gov.br/Princ_i.aspx could save 1,016B (30% reduction).

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5KiB (26% reduction).

Compressing http://ipeadata.gov.br/img/ico_exportarzip.png could save 858B (44% reduction).
Compressing http://ipeadata.gov.br/img/ico_exibir.png could save 725B (37% reduction).
Compressing http://ipeadata.gov.br/img/ico_exportarcsving.png could save 693B (36% reduction).
Compressing http://ipeadata.gov.br/img/ico_exportar.png could save 602B (27% reduction).
Compressing http://ipeadata.gov.br/img/ico_imprimir.png could save 391B (18% reduction).
Compressing http://ipeadata.gov.br/img/ico_pesquisar.gif could save 375B (31% reduction).
Compressing http://ipeadata.gov.br/img/thumb_social_h.gif could save 355B (17% reduction).
Compressing http://ipeadata.gov.br/img/thumb_regional_h.gif could save 300B (16% reduction).
Compressing http://ipeadata.gov.br/img/ico_operar.png could save 270B (14% reduction).
Compressing http://ipeadata.gov.br/img/ico_inglaterra.jpg could save 181B (22% reduction).
Compressing http://ipeadata.gov.br/img/bgBtnOperacoes.png could save 178B (62% reduction).
Compressing http://ipeadata.gov.br/img/ico_exportarcsvport.png could save 142B (11% reduction).

priority - 0Reduce server response time

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.5KiB (28% reduction).

Minifying http://ipeadata.gov.br/css/estilos.css could save 4.5KiB (28% reduction).

ipeadata.gov.br Desktop Resource Breakdown

Total Resources	39
Number of Hosts	1
Static Resources	35
JavaScript Resources	5
CSS Resources	1

ipeadata.gov.br mobile page speed rank

Last tested: 2018-01-19

Mobile Speed Bad

56/100

ipeadata.gov.br Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

http://ipeadata.gov.br/css/estilos.css

priority - 26Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 14Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 136.6KiB (78% reduction).

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

68.7KiB of the HTML response was required to render the above-the-fold content. This requires 3 network round-trips. However, if the HTML response were compressed, then the HTML required to render the above-the-fold content could be delivered in just 1 network round-trips. Enable compression for the HTML response in order to prioritize the visible content for this page.

Only about 66% of the final above-the-fold content could be rendered with the HTML delivered within 2 round-trips.

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 13KiB (28% reduction).

Minifying http://ipeadata.gov.br/jscripts/menu.js could save 9.1KiB (28% reduction).
Minifying http://ipeadata.gov.br/jscripts/ipeanet.js could save 3.9KiB (27% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 8.5KiB (12% reduction).

Minifying http://ipeadata.gov.br/Default.aspx could save 7.6KiB (12% reduction).
Minifying http://ipeadata.gov.br/Princ_i.aspx could save 1,016B (30% reduction).

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5KiB (26% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.5KiB (28% reduction).

Minifying http://ipeadata.gov.br/css/estilos.css could save 4.5KiB (28% reduction).

priority - 0Reduce server response time

ipeadata.gov.br Mobile Resource Breakdown

Total Resources	39
Number of Hosts	1
Static Resources	35
JavaScript Resources	5
CSS Resources	1

ipeadata.gov.br mobile page usability

Last tested: 2018-01-19

Mobile Usability Bad

60/100

ipeadata.gov.br Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

BRASIL renders only 5 pixels tall (12 CSS pixels).

Acesso à informação renders only 5 pixels tall (12 CSS pixels).

Legislação and 3 others render only 5 pixels tall (12 CSS pixels).

Base de dados: and 1 others render only 3 pixels tall (9 CSS pixels).

Macroeconômico and 2 others render only 3 pixels tall (9 CSS pixels).

Dados econômic…s brasileiras. and 2 others render only 4 pixels tall (11 CSS pixels).

Os dados dispo…ibliográficas. renders only 4 pixels tall (11 CSS pixels).

- and 4 others render only 4 pixels tall (11 CSS pixels).

página inicial and 3 others render only 4 pixels tall (11 CSS pixels).

0.187 - renders only 4 pixels tall (11 CSS pixels).

Equipe responsável and 6 others render only 4 pixels tall (11 CSS pixels).

priority - 18Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://brasil.gov.br" class="link-barra">Brasil</a> is close to 1 other tap targets.

The tap target <a href="http://brasil.…sso-informacao" class="link-barra">Acesso à informação</a> is close to 2 other tap targets.

The tap target <a href="http://brasil.…arra#participe" class="link-barra">Participe</a> and 2 others are close to other tap targets.

The tap target <a href="javascript:IrP…inc_i.aspx")')" class="home_p"></a> is close to 1 other tap targets.

The tap target <a href="javascript:IrP…inc_i.aspx")')" class="home_p"></a> and 4 others are close to other tap targets.

The tap target <input id="busca" type="text" name="busca" class="home_busca"> is close to 1 other tap targets.

The tap target <img src="img/ico_pesquisar.gif"> is close to 2 other tap targets.

The tap target <input id="pMacro" type="radio" name="tBusca"> and 2 others are close to other tap targets.

The tap target <a href="http://www.ipea.gov.br" class="home_p"></a> is close to 1 other tap targets.

The tap target <a id="mmlink0" href="#"> and 3 others are close to other tap targets.

The tap target <div id="lnk4">O que é</div> and 6 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 981 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="menu_bar_title"> falls outside the viewport.

ipeadata.gov.br HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 6
"...<html> <meta..."

Bad value “0;url=Default.aspx” for attribute “content” on element “meta”: Expected a space character, but saw “u” instead.

Line: 2 Column: 7 - 56
"...<html> <meta http-equiv="refresh" content="0;url=Default.aspx"> </htm..."

Element “head” is missing a required instance of child element “title”.

Line: 3 Column: 1 - 7
"...lt.aspx"> </html> ..."

ipeadata.gov.br similar domains

Similar domains:

www.ipeadata.com
www.ipeadata.net
www.ipeadata.org
www.ipeadata.info
www.ipeadata.biz
www.ipeadata.us
www.ipeadata.mobi
www.peadata.gov.br
www.ipeadata.gov.br
www.upeadata.gov.br
www.iupeadata.gov.br
www.uipeadata.gov.br
www.jpeadata.gov.br
www.ijpeadata.gov.br
www.jipeadata.gov.br
www.kpeadata.gov.br
www.ikpeadata.gov.br
www.kipeadata.gov.br
www.opeadata.gov.br
www.iopeadata.gov.br
www.oipeadata.gov.br
www.ieadata.gov.br
www.ioeadata.gov.br
www.ipoeadata.gov.br
www.ileadata.gov.br
www.ipleadata.gov.br
www.ilpeadata.gov.br
www.ipadata.gov.br
www.ipwadata.gov.br
www.ipewadata.gov.br
www.ipweadata.gov.br
www.ipsadata.gov.br
www.ipesadata.gov.br
www.ipseadata.gov.br
www.ipdadata.gov.br
www.ipedadata.gov.br
www.ipdeadata.gov.br
www.ipradata.gov.br
www.iperadata.gov.br
www.ipreadata.gov.br
www.ipedata.gov.br
www.ipeqdata.gov.br
www.ipeaqdata.gov.br
www.ipeqadata.gov.br
www.ipewdata.gov.br
www.ipeawdata.gov.br
www.ipesdata.gov.br
www.ipeasdata.gov.br
www.ipezdata.gov.br
www.ipeazdata.gov.br
www.ipezadata.gov.br
www.ipeaata.gov.br
www.ipeaxata.gov.br
www.ipeadxata.gov.br
www.ipeaxdata.gov.br
www.ipeasata.gov.br
www.ipeadsata.gov.br
www.ipeaeata.gov.br
www.ipeadeata.gov.br
www.ipeaedata.gov.br
www.ipearata.gov.br
www.ipeadrata.gov.br
www.ipeardata.gov.br
www.ipeafata.gov.br
www.ipeadfata.gov.br
www.ipeafdata.gov.br
www.ipeacata.gov.br
www.ipeadcata.gov.br
www.ipeacdata.gov.br
www.ipeadta.gov.br
www.ipeadqta.gov.br
www.ipeadaqta.gov.br
www.ipeadqata.gov.br
www.ipeadwta.gov.br
www.ipeadawta.gov.br
www.ipeadwata.gov.br
www.ipeadsta.gov.br
www.ipeadasta.gov.br
www.ipeadzta.gov.br
www.ipeadazta.gov.br
www.ipeadzata.gov.br
www.ipeadaa.gov.br
www.ipeadara.gov.br
www.ipeadatra.gov.br
www.ipeadarta.gov.br
www.ipeadafa.gov.br
www.ipeadatfa.gov.br
www.ipeadafta.gov.br
www.ipeadaga.gov.br
www.ipeadatga.gov.br
www.ipeadagta.gov.br
www.ipeadaya.gov.br
www.ipeadatya.gov.br
www.ipeadayta.gov.br
www.ipeadat.gov.br
www.ipeadatq.gov.br
www.ipeadataq.gov.br
www.ipeadatqa.gov.br
www.ipeadatw.gov.br
www.ipeadataw.gov.br
www.ipeadatwa.gov.br
www.ipeadats.gov.br
www.ipeadatas.gov.br
www.ipeadatsa.gov.br
www.ipeadatz.gov.br
www.ipeadataz.gov.br
www.ipeadatza.gov.br

ipeadata.gov.br Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

ipeadata.gov.br TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

IPEADATA.GOV.BR Website Information

ipeadata.gov.br Website Information

Advertisement

ipeadata.gov.br Alexa Rank

ipeadata.gov.br whois

ipeadata.gov.br server information

Servers Location

ipeadata.gov.br desktop page speed rank

ipeadata.gov.br Desktop Speed Test Quick Summary

priority - 18Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 14Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 136.6KiB (78% reduction).

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 2Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 13KiB (28% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 8.5KiB (12% reduction).

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5KiB (26% reduction).

priority - 0Reduce server response time

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.5KiB (28% reduction).

ipeadata.gov.br Desktop Resource Breakdown

ipeadata.gov.br mobile page speed rank

ipeadata.gov.br Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 26Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 14Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 136.6KiB (78% reduction).

priority - 8Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 13KiB (28% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 8.5KiB (12% reduction).

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5KiB (26% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.5KiB (28% reduction).

priority - 0Reduce server response time

ipeadata.gov.br Mobile Resource Breakdown

ipeadata.gov.br mobile page usability

ipeadata.gov.br Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 18Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 981 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

ipeadata.gov.br HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Bad value “0;url=Default.aspx” for attribute “content” on element “meta”: Expected a space character, but saw “u” instead.