Voz.Gov.Br - Info voz.gov.br

voz.gov.br receives about 5,443 unique visitors and 5,443 (1.00 per visitor) page views per day which should earn about $9.08/day from advertising revenue. Estimated site value is $6,625.60. According to Alexa Traffic Rank voz.gov.br is ranked number 568,339 in the world and 0.00012% of global Internet users visit it. Site is hosted in Brasília, Federal District, 70640, Brazil and links to network IP address 189.9.0.45. This server doesn't support HTTPS and doesn't support HTTP/2.

About - voz.gov.br


Technologies used on Website

Analytics
Google Analytics
Web Servers
Nginx
Reverse proxies
Nginx
Caching
Varnish

voz.gov.br Profile

Title: A Voz do Brasil
Last update was 139 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with voz.gov.br in any way. Only publicly available statistics data are displayed.

How popular is voz.gov.br?

5.4K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
5,443
Monthly Unique Visitors:
130,632
Pages per Visit:
1.00
Daily Pageviews:
5,443
Alexa Rank:
568,339 visit alexa
Alexa Reach:
0.00012%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Brazil 94.2%94.2%22618

Where do visitors go on this site?

Reach%Pageviews%PerUser
voz.gov.br
100.00%100.00%1

Competitive Data

SEMrush
Domain:
  voz.gov.br
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is voz.gov.br?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
voz.gov.br
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
voz.gov.br
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much voz.gov.br can earn?

Daily Revenue:
$9.08
Monthly Revenue:
$272.40
Yearly Revenue:
$3,314.20
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Brazil 5,127$9.08

How much money do voz.gov.br lose due to Adblock?

Daily Revenue Loss:
$0.54
Monthly Revenue Loss:
$16.34
Yearly Revenue Loss:
$198.75
Daily Pageviews Blocked:
308
Monthly Pageviews Blocked:
9,229
Yearly Pageviews Blocked:
112,288
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Brazil 308$0.54

How much is voz.gov.br worth?

Website Value:
$6,625.60

+ Where is voz.gov.br hosted?

Server IP:
189.9.0.45
ASN:
AS10954 
ISP:
SERVICO FEDERAL DE PROCESSAMENTO DE DADOS - SERPRO 
Server Location:
Brasília
Federal District, DF
70640
Brazil, BR
 

Other sites hosted on 189.9.0.45

+ How fast does voz.gov.br load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://vlibras.gov.br/app/vlibras-plugin.js
0 ms299 KB
https://vlibras.gov.br/app/assets/popup.png
0 ms157 KB
https://vlibras.gov.br/app/assets/component-ac.png
0 ms23 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://barra.brasil.gov.br/barra.js
604800000 ms8 KB
http://voz.gov.br/voz.jpg
5184000000 ms308 KB
http://voz.gov.br/bg.jpg
5184000000 ms142 KB
http://voz.gov.br/build/jquery.js
5184000000 ms78 KB
http://voz.gov.br/build/mediaelement-and-player.min.js
5184000000 ms25 KB
http://voz.gov.br/logo-voz.png
5184000000 ms23 KB
http://voz.gov.br/script-twitter.js
5184000000 ms14 KB
http://voz.gov.br/logo-ebc-p.png
5184000000 ms9 KB
http://voz.gov.br/build/mediaelementplayer.min.css
5184000000 ms4 KB
http://voz.gov.br/face.png
5184000000 ms2 KB
http://voz.gov.br/youtube.png
5184000000 ms2 KB
http://voz.gov.br/twitter.png
5184000000 ms2 KB
http://voz.gov.br/estilo-voz.css
5184000000 ms1 KB
http://voz.gov.br/twitter-voz.css
5184000000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
172 ms
6 ms
641 ms
20 ms
748 ms
10 ms
760 ms
6 ms
766 ms
64 ms
839 ms
13 ms
851 ms
24 ms
1408 ms
39 ms
1530 ms
6 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
87 ms4 ms1 ms
Properly size images - Potential savings of 296 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB273 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB23 KB
Avoids enormous network payloads - Total size was 1,136 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://voz.gov.br/voz.jpg
308 KB
https://vlibras.gov.br/app/vlibras-plugin.js
299 KB
https://vlibras.gov.br/app/assets/popup.png
157 KB
http://voz.gov.br/bg.jpg
142 KB
http://voz.gov.br/build/jquery.js
78 KB
http://voz.gov.br/build/mediaelement-and-player.min.js
25 KB
http://voz.gov.br/logo-voz.png
23 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB
http://barra.brasil.gov.br/static/opensans-bold.woff
18 KB
https://www.google-analytics.com/analytics.js
18 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
108 ms
Other
42 ms
Style & Layout
37 ms
Rendering
20 ms
Script Parsing & Compilation
17 ms
Parse HTML & CSS
14 ms
Serve images in next-gen formats - Potential savings of 529 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB254 KB
https://vlibras.gov.br/app/assets/popup.png
157 KB126 KB
http://voz.gov.br/bg.jpg
141 KB121 KB
http://voz.gov.br/logo-voz.png
23 KB17 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB11 KB
Avoids an excessive DOM size - 83 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
83
Maximum DOM Depth
10
Maximum Child Elements
12
Minify JavaScript - Potential savings of 36 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://voz.gov.br/build/jquery.js
78 KB36 KB
Keep request counts low and transfer sizes small - 26 requests • 1,136 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
261136 KB
Image
15667 KB
Script
6443 KB
Font
118 KB
Stylesheet
35 KB
Document
12 KB
Media
00 KB
Other
00 KB
Third-party
12524 KB
Eliminate render-blocking resources - Potential savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://voz.gov.br/estilo-voz.css
1 KB70
http://voz.gov.br/build/jquery.js
78 KB310
http://voz.gov.br/build/mediaelement-and-player.min.js
25 KB230
http://voz.gov.br/build/mediaelementplayer.min.css
4 KB110
http://voz.gov.br/script-twitter.js
14 KB190
http://voz.gov.br/twitter-voz.css
1 KB110
Enable text compression - Potential savings of 236 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://vlibras.gov.br/app/vlibras-plugin.js
298 KB236 KB
Efficiently encode images - Potential savings of 218 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB154 KB
http://voz.gov.br/bg.jpg
141 KB64 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://voz.gov.br/
0 ms147 ms2 KB4 KB200text/htmlDocument
http://voz.gov.br/estilo-voz.css
158 ms305 ms1 KB3 KB200text/cssStylesheet
http://voz.gov.br/build/jquery.js
158 ms608 ms78 KB262 KB200application/x-javascriptScript
http://voz.gov.br/build/mediaelement-and-player.min.js
158 ms721 ms25 KB92 KB200application/x-javascriptScript
http://voz.gov.br/build/mediaelementplayer.min.css
158 ms346 ms4 KB20 KB200text/cssStylesheet
http://voz.gov.br/script-twitter.js
159 ms500 ms14 KB44 KB200application/javascriptScript
http://voz.gov.br/twitter-voz.css
159 ms348 ms1 KB1 KB200text/cssStylesheet
http://barra.brasil.gov.br/barra.js
159 ms178 ms8 KB27 KB200application/javascriptScript
http://voz.gov.br/logo-voz.png
160 ms627 ms23 KB23 KB200image/pngImage
http://voz.gov.br/face.png
160 ms348 ms2 KB1 KB200image/pngImage
http://voz.gov.br/twitter.png
349 ms495 ms2 KB1 KB200image/pngImage
http://voz.gov.br/youtube.png
496 ms644 ms2 KB1 KB200image/pngImage
http://voz.gov.br/voz.jpg
640 ms1496 ms308 KB307 KB200image/jpegImage
http://voz.gov.br/logo-ebc-p.png
645 ms795 ms9 KB8 KB200image/pngImage
http://voz.gov.br/bg.jpg
742 ms1314 ms142 KB141 KB200image/jpegImage
https://vlibras.gov.br/app/vlibras-plugin.js
746 ms1381 ms299 KB298 KB200application/javascriptScript
data:image/gif;base64,R0lGODlhAQABAIAAAAUEBAAAACwAAAAAAQABAAACAkQBADs=
748 ms748 ms0 KB0 KB200image/gifImage
data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20width%3D%2226%22%20
769 ms769 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIyOSIgaGVpZ2
771 ms771 ms0 KB3 KB200image/svg+xmlImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
776 ms776 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
776 ms776 ms0 KB1 KB200image/pngImage
http://barra.brasil.gov.br/static/opensans-bold.woff
778 ms810 ms18 KB18 KB200application/x-font-woffFont
https://www.google-analytics.com/analytics.js
787 ms792 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1593182131&t=pageview&_s=1&dl=http%3A%2F%2Fvoz.gov.br%2F&ul=en-us&de=UTF-8&dt=A%20Voz%20do%20Brasil&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEAB~&jid=2015261007&gjid=1593729263&cid=86133472.1574532746&tid=UA-86641312-1&_gid=29985551.1574532746&_r=1&z=1738186325
852 ms856 ms1 KB0 KB200image/gifImage
https://vlibras.gov.br/app/assets/component-ac.png
1502 ms1757 ms23 KB23 KB200image/pngImage
https://vlibras.gov.br/app/assets/popup.png
1502 ms1634 ms157 KB157 KB200image/pngImage
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 150 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

82
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Meaningful Paint 2.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 210 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 5.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 4751.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.5 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 26 requests • 1,136 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
261136 KB
Image
15667 KB
Script
6443 KB
Font
118 KB
Stylesheet
35 KB
Document
12 KB
Media
00 KB
Other
00 KB
Third-party
12524 KB
Eliminate render-blocking resources - Potential savings of 1,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://voz.gov.br/estilo-voz.css
1 KB180
http://voz.gov.br/build/jquery.js
78 KB1380
http://voz.gov.br/build/mediaelement-and-player.min.js
25 KB930
http://voz.gov.br/build/mediaelementplayer.min.css
4 KB330
http://voz.gov.br/script-twitter.js
14 KB630
http://voz.gov.br/twitter-voz.css
1 KB330
Efficiently encode images - Potential savings of 218 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB154 KB
http://voz.gov.br/bg.jpg
141 KB64 KB
Enable text compression - Potential savings of 236 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://vlibras.gov.br/app/vlibras-plugin.js
298 KB236 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://voz.gov.br/
0 ms148 ms2 KB4 KB200text/htmlDocument
http://voz.gov.br/estilo-voz.css
161 ms554 ms1 KB3 KB200text/cssStylesheet
http://voz.gov.br/build/jquery.js
161 ms620 ms78 KB262 KB200application/x-javascriptScript
http://voz.gov.br/build/mediaelement-and-player.min.js
162 ms724 ms25 KB92 KB200application/x-javascriptScript
http://voz.gov.br/build/mediaelementplayer.min.css
162 ms489 ms4 KB20 KB200text/cssStylesheet
http://voz.gov.br/script-twitter.js
162 ms457 ms14 KB44 KB200application/javascriptScript
http://voz.gov.br/twitter-voz.css
163 ms317 ms1 KB1 KB200text/cssStylesheet
http://barra.brasil.gov.br/barra.js
163 ms466 ms8 KB27 KB200application/javascriptScript
http://voz.gov.br/logo-voz.png
163 ms722 ms23 KB23 KB200image/pngImage
http://voz.gov.br/face.png
164 ms489 ms2 KB1 KB200image/pngImage
http://voz.gov.br/twitter.png
490 ms637 ms2 KB1 KB200image/pngImage
http://voz.gov.br/youtube.png
655 ms803 ms2 KB1 KB200image/pngImage
http://voz.gov.br/voz.jpg
724 ms1449 ms308 KB307 KB200image/jpegImage
http://voz.gov.br/logo-ebc-p.png
749 ms898 ms9 KB8 KB200image/pngImage
http://voz.gov.br/bg.jpg
749 ms1519 ms142 KB141 KB200image/jpegImage
https://vlibras.gov.br/app/vlibras-plugin.js
753 ms1766 ms299 KB298 KB200application/javascriptScript
data:image/gif;base64,R0lGODlhAQABAIAAAAUEBAAAACwAAAAAAQABAAACAkQBADs=
755 ms755 ms0 KB0 KB200image/gifImage
data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20width%3D%2226%22%20
776 ms776 ms0 KB0 KB200image/svg+xmlImage
data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIyOSIgaGVpZ2
779 ms779 ms0 KB3 KB200image/svg+xmlImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
785 ms785 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
785 ms785 ms0 KB1 KB200image/pngImage
http://barra.brasil.gov.br/static/opensans-bold.woff
787 ms1021 ms18 KB18 KB200application/x-font-woffFont
https://www.google-analytics.com/analytics.js
797 ms802 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=2038374378&t=pageview&_s=1&dl=http%3A%2F%2Fvoz.gov.br%2F&ul=en-us&de=UTF-8&dt=A%20Voz%20do%20Brasil&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAEAB~&jid=623717784&gjid=1179985460&cid=378521078.1574532737&tid=UA-86641312-1&_gid=445074829.1574532737&_r=1&z=965509583
861 ms865 ms1 KB0 KB200image/gifImage
https://vlibras.gov.br/app/assets/component-ac.png
1830 ms2510 ms23 KB23 KB200image/pngImage
https://vlibras.gov.br/app/assets/popup.png
1830 ms1968 ms157 KB157 KB200image/pngImage
Serve static assets with an efficient cache policy - 18 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://vlibras.gov.br/app/vlibras-plugin.js
0 ms299 KB
https://vlibras.gov.br/app/assets/popup.png
0 ms157 KB
https://vlibras.gov.br/app/assets/component-ac.png
0 ms23 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://barra.brasil.gov.br/barra.js
604800000 ms8 KB
http://voz.gov.br/voz.jpg
5184000000 ms308 KB
http://voz.gov.br/bg.jpg
5184000000 ms142 KB
http://voz.gov.br/build/jquery.js
5184000000 ms78 KB
http://voz.gov.br/build/mediaelement-and-player.min.js
5184000000 ms25 KB
http://voz.gov.br/logo-voz.png
5184000000 ms23 KB
http://voz.gov.br/script-twitter.js
5184000000 ms14 KB
http://voz.gov.br/logo-ebc-p.png
5184000000 ms9 KB
http://voz.gov.br/build/mediaelementplayer.min.css
5184000000 ms4 KB
http://voz.gov.br/face.png
5184000000 ms2 KB
http://voz.gov.br/youtube.png
5184000000 ms2 KB
http://voz.gov.br/twitter.png
5184000000 ms2 KB
http://voz.gov.br/estilo-voz.css
5184000000 ms1 KB
http://voz.gov.br/twitter-voz.css
5184000000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 50 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB51 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
177 ms
8 ms
656 ms
23 ms
754 ms
12 ms
768 ms
7 ms
775 ms
70 ms
858 ms
28 ms
1049 ms
6 ms
1797 ms
52 ms
JavaScript execution time - 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
368 ms18 ms4 ms
https://vlibras.gov.br/app/vlibras-plugin.js
197 ms174 ms22 ms
http://voz.gov.br/build/jquery.js
170 ms76 ms27 ms
http://voz.gov.br/
141 ms71 ms2 ms
https://www.google-analytics.com/analytics.js
110 ms104 ms6 ms
Properly size images - Potential savings of 94 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB72 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB22 KB
Avoids enormous network payloads - Total size was 1,136 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://voz.gov.br/voz.jpg
308 KB
https://vlibras.gov.br/app/vlibras-plugin.js
299 KB
https://vlibras.gov.br/app/assets/popup.png
157 KB
http://voz.gov.br/bg.jpg
142 KB
http://voz.gov.br/build/jquery.js
78 KB
http://voz.gov.br/build/mediaelement-and-player.min.js
25 KB
http://voz.gov.br/logo-voz.png
23 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB
http://barra.brasil.gov.br/static/opensans-bold.woff
18 KB
https://www.google-analytics.com/analytics.js
18 KB
Minimizes main-thread work - 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
512 ms
Other
197 ms
Style & Layout
167 ms
Script Parsing & Compilation
81 ms
Rendering
62 ms
Parse HTML & CSS
61 ms
Serve images in next-gen formats - Potential savings of 529 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://voz.gov.br/voz.jpg
307 KB254 KB
https://vlibras.gov.br/app/assets/popup.png
157 KB126 KB
http://voz.gov.br/bg.jpg
141 KB121 KB
http://voz.gov.br/logo-voz.png
23 KB17 KB
https://vlibras.gov.br/app/assets/component-ac.png
23 KB11 KB
Avoids an excessive DOM size - 83 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
83
Maximum DOM Depth
10
Maximum Child Elements
12
Minify JavaScript - Potential savings of 36 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://voz.gov.br/build/jquery.js
78 KB36 KB
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 150 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Avoid chaining critical requests - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use 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 and 4 others render only 5 pixels tall (12 CSS pixels) .
PROGRAMAS ANTERIORES and 1 others render only 7 pixels tall (18 CSS pixels) .
As rádios de t…rário flexível renders only 8 pixels tall (20 CSS pixels) .
A retransmissã…h15 no site da renders only 5 pixels tall (14 CSS pixels) .
Rede Nacional de Rádio renders only 5 pixels tall (14 CSS pixels) .
Video Player renders only 5 pixels tall (13 CSS pixels) .
Download File renders only 5 pixels tall (13 CSS pixels) .

Optimize images

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

Optimize the following images to reduce their size by 298.5KiB (61% reduction).

Compressing http://voz.gov.br/voz.jpg could save 198.5KiB (64% reduction).
Compressing http://voz.gov.br/bg.jpg could save 93KiB (65% reduction).
Compressing http://voz.gov.br/logo-voz.png could save 3.5KiB (16% reduction).
Compressing http://voz.gov.br/twitter.png could save 913B (78% reduction).
Compressing http://voz.gov.br/youtube.png could save 909B (76% reduction).
Compressing http://voz.gov.br/face.png could save 904B (75% reduction).
Compressing http://voz.gov.br/logo-ebc-p.png could save 851B (11% reduction).

Enable 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 236.5KiB (79% reduction).

Compressing https://vlibras.gov.br/app/vlibras-plugin.js could save 236.5KiB (79% reduction).

Configure 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.

Configure a viewport for this page.

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

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

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

http://voz.gov.br/estilo-voz.css

Minify JavaScript

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

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

Minifying http://voz.gov.br/build/jquery.js could save 37.8KiB (49% reduction) after compression.

Size 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 990 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <p>A retransmissã…ional de Rádio</p> falls outside the viewport.

Size 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="https://gov.br…cutivo-federal" class="link-barra">Canais</a> is close to 1 other tap targets .
The tap target <a id="logovlibras" href="#" class="logo-vlibras"> is close to 1 other tap targets .
The tap target <a href="https://www.fa…obrasiloficial"></a> and 2 others are close to other tap targets .

Leverage 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:

https://vlibras.gov.br/app/vlibras-plugin.js (expiration not specified)
https://www.google-***ytics.com/***ytics.js (2 hours)

Minify CSS

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

Minify CSS for the following resources to reduce their size by 105B (12% reduction).

Minifying http://voz.gov.br/estilo-voz.css could save 105B (12% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does voz.gov.br use compression?

voz.gov.br use gzip compression.
Original size: 3.73 KB
Compressed size: 1.66 KB
File reduced by: 2.07 KB (55%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

voz.gov.br does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

voz.gov.br does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Sat, 23 Nov 2019 18:11:13 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
X-Varnish: 442314485 442314473
Age: 36
Via: 1.1 varnish
X-Cache: HIT
X-Varnish-Cache: HIT
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
TXT 3600
MX smtp1.nbr.gov.br 3600
SOA 3600
Mname ns1.radiobras.gov.br
Rname root.radiobras.gov.br.voz.gov.br
Serial Number 2016103102
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 0
A 189.9.0.45 3573
NS ns1.radiobras.gov.br 3573
NS ns2.radiobras.gov.br 3573

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.registro.br...

Last update was 139 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with voz.gov.br in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

veljanoski.com
25 secs
stilnajena.bg
1 min
tvplus.mk
1 min
mp4upload.com
1 min
ts.mk
2 mins
sarcasm.co
2 mins
stena.ee
2 mins
nymag.com
2 mins
trikoteks-komerc.mk
3 mins
uncut-news.ch
3 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
voz.gov.br widget