Dataprev.gov.br

 

Latency Testing Disabled.

SiteSpeedLab can't measure the latency of the dataprev.gov.br. While performing tests we do not get responses from the remote server 200.152.32.178.
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester
Learn more at DNS Testing Profile
Separate test for different locations, time frames
Learn more at PageSpeed Testing Profile

WebSite Speed Profile

Site Speed Success Formula = good website latency + fast DNS lookup + high page load speed.
Site Speed Laboratory offers analysis of DNS Lookup speed & latency tests (ping) & Page Load speed for every website. Our analysis is based on data for May 31 2011. Since the first of July 2010 we carried out 21 tests from locations
for the main page of this website, the last of which were made about 22310 hours ago

Tests Summary

DNS Summary

Page Speed Summary

Site Speed Laboratory Summary for this website

Location Ping Ping,
change
DNS Lookup DNS Resolve,
change
Page Speed Page Speed,
change
 Usa
NY, New York 335 ms 8 % 96.54 Kb/s 2%
Florida, Tampa 247 ms 39 %
 Germany
Frankfurt 249 ms 42 %
 Canada
Montreal 250 ms
 United Kingdom
Gloucester 250 ms

Summary Widget

SiteSpeedLab Overall Website Rating for this website
Based on our speed test results table and considering features of the current webserver location (Brazil), we concluded
overall This website speed rank is 66. That means 66% of the sites from the are slower for visitors than this website.

It is important to understand that you can't evaluate website speed without considering website audience location. You should evaluate the speed of the site considering location of your primary audience (visitors), and not just from abstract tests from various points of the planet. There is a chance that your website is quite slow for visitors from German but pretty quick for Australian users at the same time. Based on a primary audience location data Site Speed Laboratory maintains objective rating.

You should not overestimate the importance of the website speed factor. Google has more than 200 ranking factors and website speed is just one of them.

DNS Lookup Speed

Browser should lookup domain name and get IP address of the server (200.152.32.178) before downloading the page. We test DNS resolve for this domain from 5 locations. That's how we've got the average time of receiving IP: 0.27s (which is better than 46% of all sites). For more detailed stats look at DNS tests graph and DNS resolve page for Brazil, location (Average value on the widget is an average DNS resolve time for websites hosted at the same location).

DNS History Graph

Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss
Compare DNS From Servers
Usa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester
The main purpose of the testing is a measuring the speed and rating the stability of the latency to this IP from around the world in comparison with sites of the region (the city).
The chart will appear within this DIV. This text will be replaced by the chart.
 Usa, NY, New York
 Usa, Florida, Tampa
 Germany, Frankfurt
 Canada, Montreal
 United Kingdom, Gloucester

Graph Legend

  • Maximum latency for current location, mouse over for the details.
  • Mimimal latency for current location, mouse over for the details (date, value, etc.)
  • Milestones indicate the change of IP for the current site
  • Data Loss

Compare DNS Speed

Compare DNS Lookup


vs

Our Servers
Usa
NY, New York
Florida, Tampa
Germany, Frankfurt
Canada, Montreal
United Kingdom, Gloucester

The table below shows the dynamic of the DNS Lookup speed changes for the website from various locations.

Location Last check 7 day change 1 month change 3 month change 6 month change
 Usa
NY, New York 335 ms
Florida, Tampa 247 ms
 Germany
Frankfurt 249 ms
 Canada
Montreal 250 ms
 United Kingdom
Gloucester 250 ms

Fragment of DNS Speed rating table for this website

The table is constructed according to the data from the US datacenters

# Domain Compare DNS Resolve Speed Provider
1. Terraempresas.com.br 78 ms Terra Networks Brasil S.a.
2. Extremaonline.com 80 ms
3. Eventu.biz 88 ms
... ... ... ... ...
1655. Gerconrh.com.br 265 ms Redehost Internet Ltda.
1656. Sitesabc.com.br 265 ms
1657. Dataprev.gov.br 266 ms Dataprev Empresa De Proc. De Dados Da Previdencia
1658. Guiadasemana.com.br 266 ms Embratel
1659. Gsmfans.com.br 266 ms Cyberweb Networks Ltda
... ... ... ... ...
3137. Sortegrande.com.br 5751 ms Universo Online S.a.

Page Speed Test

Content-Type's Weights
 
 
Content-Type's Weights by Hosts
 
 
Downloading page itself is the final stage of the testing. Actually, this is the last stage, after which page is displayed completely for user. The download speed depends on many factors. Main factors are the following: the width of the bandwidth up to the domain, the number of simultaneous download threads, speed of the server, a distance between user and domain web server. Recent measurements have shown the speed of page download for this domain is 96.536Kb/s (which is better than 66% of all sites in this region). For more detailed stats check out report for hosted websites.

 
 
 

Page Speed

Page Speed is a key factor in the website speed estimations (along with DNS lookup speed and website latency). Speed of the page loading, sophisticated subdomains usage for static content (images, css), optimized code (html, js), hosting on fast servers with good latency to its audience leads to good results and, ultimately, to a good website profitability.

While conducting tests we emulate a visit your website using the browser Firefox 3.5.6. Test results of the page loading listed in this table:

Pagespeed Flash Table

Ways to improve website performance

Once the document (website's main page) has been downloaded, we analyze it. It allows us to give webmasters some recommendations on how to optimize page load speed. We analyze the internal and external factors.

Enable GZIP Compression

This is a good practice to give the user content in compressed form. We've detected 12.2 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 3.05 Kb (saving 9.15 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in Dataprev Empresa De Proc. De Dados Da Previdencia.
http://dataprev.gov.br/. File size 0.18 Kb and you can save up to 0.14 Kb
http://portal.dataprev.gov.br/wp-content/plugins/podpress/players/1pix.... File size 12.02 Kb and you can save up to 9.02 Kb

Keep Components under 25K

Users often visit web site using a mobile phone. Even the most modern and advanced gadgets have some limitations. For example an iPhone browser do not cache page components bigger than 25K. So you should strive to ensure that scripts, CSS-styles, etc. are less than 25K.
http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/m...  Content-Encoding: application/javascript. File size 46.86 Kb.
http://portal.dataprev.gov.br/wp-content/uploads/2010/05/acessibilidade.png  Content-Encoding: image/png. File size 64.84 Kb.
http://portal.dataprev.gov.br/wp-content/gallery/11-fisl/fisl3.jpg  Content-Encoding: image/jpeg. File size 221.49 Kb.
http://portal.dataprev.gov.br/wp-content/uploads/2009/09/banner_previd...  Content-Encoding: image/gif. File size 41.31 Kb.
http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/m...  Content-Encoding: image/png. File size 29.63 Kb.

Alternate text for the images.

As you may already know, search engine that indexes your pages, do not have eyes. And all content you are trying to display on your site is just HTML & CSS code, images, Flash, etc for the robots. It is It's extremely important to describe each of the objects more datailed using ALT, TITLE and other tags.

Our robot has determined that the dataprev.gov.br page has 5 images, which has no tag ALT. Tag ALT is a text field, that specifies an alternate text for an image. But not only. Search engines consider this tag as a supplemental result for assessing the content of your page entirely. Do not ignore it!

For example your page has this code:
473.   <img src="http://portal.dataprev.gov.br/wp-content/gallery/11-fisl/fisl3.jpg">
We recommend you use rich img code in that place:
473.   <img src="http://portal.dataprev.gov.br/wp-content/gallery/11-fisl/fisl3.jpg" alt="software livre">


P.S. We used keyword for this image that seemed to us most important for your page. But you can go ahead and give to each of 5 images an ALT text. This problem requires responsible approach. No need to put the same text at alt tag of the all images. Imagine that the pictures do not show and try to make sure that users understand what is shown on the picture based on the alt tag

Specify image dimensions

The browser needs to know the actual dimensions of image (width and height) to quickly render webpage.

We have detected that the 28 images has no width and height.

If you do not specify the width and/or height, then in order to correctly display the image browser needs to download it and only then put on the screen. Otherwise, there is a chance browser will display elements under the picture inappropriately as well as the possible presence of "jumping" effect of the page content (until the page load is finished).

We provide below example of how to define the image http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/media/images/creative_commons.png dimensions:
574.   <img src="http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/media/images/creative_commons.p..." id="logo_cc" alt="Logo da Licença Creative Commons" title="Logo da Licença Creative Commons" width="IMAGE_WIDTH_HERE" height="IMAGE_HEIGHT_HERE">

Using H1 tag

Avoid frequent use of the <Н1> tag. Our robot has found 4 <Н1> tags in the document's body. We recommend you use one <Н1> tag per page only.

Use the TITLE for A tag

As we have already mentioned, search engine bots can not see the site like a people do it. They more focused on the descriptions of certain page elements. That's why we strongly recommend use TITLE operator in the "A" tag. This operator not only describes the page referenced by the page more detailed, but also takes part in the page describing. For example, you have the link on your website:
228.   <a href="http://portal.dataprev.gov.br"><img alt="Logo Dataprev" id="logodtp" src= "http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/media/images/logo_dataprev.png"></a>
We suggest you to remake it in this way:
228.   <a href="http://portal.dataprev.gov.br" title="ministério da previdência"><img alt="Logo Dataprev" id="logodtp" src= "http://portal.dataprev.gov.br/wp-content/themes/sitedataprev/library/media/images/logo_dataprev.png"></a>
Of course, you can (and should) use more proper phrase instead of the "ministério da previdência" that describes the link http://portal.dataprev.gov.br.

Number of links on the page

Try to avoid a large number of links on the page. Our robot have found 113 links on this page. Google recommends to keep the number of links fewer than 100. More information about this topic you can find in Google Webmaster Guidelines and in the post "How many links per page?" by Matt Cutts (head of Google’s Webspam team)


Our Mailbox © 2009 — 2013 SiteSpeedLab & SiteSpeedLab.com
Be Quick or Be Dead