Kalipedia.com

 
Ads by Google

Latency Testing Disabled.

SiteSpeedLab can't measure the latency of the kalipedia.com. While performing tests we do not get responses from the remote server 194.169.201.147.
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 26 2011. Since the first of July 2010 we carried out 22 tests from locations
for the main page of this website, the last of which were made about 3616 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
1.30% of traffic
NY, New York 180 ms 27 % 34.71 Kb/s 12%
Florida, Tampa 256 ms 6 %
 Germany
Frankfurt 206 ms 199 %
 Canada
Montreal 130 ms
 United Kingdom
Gloucester 71 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 (Spain, Madrid), we concluded
overall This website speed rank is 17. That means 17% of the sites from the Madrid 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. Our main test server for this website is located in Usa. It provides a representative sampling of 1.30% (1.30% is share of visitors from country Usa)

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 (194.169.201.147) 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.17s (which is better than 50% of all sites). For more detailed stats look at DNS tests graph and DNS resolve page for Spain, Madrid 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
1.30% of traffic
NY, New York 180 ms 3%
200/206 ms
Florida, Tampa 256 ms 26%
269/213 ms
 Germany
Frankfurt 206 ms 142%
215/89 ms
 Canada
Montreal 130 ms 6%
117/125 ms
 United Kingdom
Gloucester 71 ms 10%
69/77 ms

Fragment of Madrid 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. Iesgrancapitan.org 35 ms Grupo Interdominios S.a
2. E-sam.com 38 ms Colt Telecom Group Limited
3. Todoart.com 40 ms Intelideas
... ... ... ... ...
1208. Ofiline.com 167 ms Ran Networks S.l.
1209. Posicionamientoeficaz.com 167 ms Propelin Consulting S.l.u.
1210. Kalipedia.com 168 ms Prisacom Media Services
1211. Aeat.es 168 ms Telefonica De Espana
1212. Nuevosvecinos.com 168 ms Acens Technologies, S.a
... ... ... ... ...
2481. Sondasespaciales.com 6050 ms Grupo Interdominios 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 34.709Kb/s (which is better than 17% of all sites in this region). For more detailed stats check out report for Madrid 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.

Reduse DNS Resolve

Browsers must resolve site's hosts to display all of the elements of the Kalipedia.com's page. Every domain name resolve requires a time, which precedes the load from a specific domain. You can speed up page loading by reducing the number of hosts, from which elements of the page are loaded.
 Host www.kalipedia.com (52 files)
 Host prisacom.112.2o7.net (1 file)
 Host ads.prisacom.com (1 file)
 Host imagenen1.247realmedia.com (3 files)
 Host www.prisacom.com (2 files)
 Host www.adobe.com (1 file)
 Host www.dixio.com (1 file)

Combine Small Images Into One

To display a page, a browser needs to load a lot of small images. Try to combine images into one and display them via CSS. This technology is called 'CSS Sprites'. It helps you reduce the number of requests to the web server, which in turn also requires time and bandwidth. For more details about this technology read our manual.
 www.kalipedia.com (23 image files)

Enable GZIP Compression

This is a good practice to give the user content in compressed form. We've detected 4 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 1 Kb (saving 3 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in Prisacom Media Services.
http://www.kalipedia.com/geoIp.php?. File size 0.01 Kb and you can save up to 0.01 Kb
http://ads.prisacom.com/RealMedia/ads/adstream_mjx.ads/www.kalipedia.c.... File size 3.57 Kb and you can save up to 2.68 Kb
http://www.kalipedia.com/js/video/video.js. File size 0.3 Kb and you can save up to 0.23 Kb
http://www.kalipedia.com/comunes/js/loadEmbedObject.js. File size 0.12 Kb and you can save up to 0.09 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://www.kalipedia.com/css/kalipedia_comun.css  Content-Encoding: text/css. File size 32.46 Kb.

Avoid 301 & 302 Redirects

Redirect allows you to make website or page available under many URLs. Webmasters use redirects when their sites change domain name, several websites are merged into one, document is moved too a new location, etc. Using a redirect delays content obtaining. Any delay negatively affects on the user experience. We've detected that page has 1 redirects before page components start loading. The following list contains some of these redirects:
http://prisacom.112.2o7.net/b/ss/prisacomkalipedia,prisacomglobal/1/H.... redirects to http://prisacom.112.2o7.net/b/ss/prisacomkalipedia,prisacomglobal/1/H....
Try to reduce the number unnecessary redirects.

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 kalipedia.com page has 1 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:
63.   <img id="imageomni" style="display: none;" height="1" width="1" name="imageomni">
We recommend you use rich img code in that place:
63.   <img id="imageomni" style="display: none;" height="1" width="1" name="imageomni" alt="contenidos">


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 1 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

Reduce the number of requests to your server by avoiding empty image src attributes

Webmasters may left, intentionally or by mistake, src attribute of the img tag blank. This is bad practice. In this case, the browser (Internet Explorer, Safari, Chrome, Firefox 3) makes an unnecessary request to the server. You waste server computing cycles and traffic. And there is the possibility of destroying user data too.
63.   <img id="imageomni" style="display: none;" height="1" width="1" name="imageomni" src="">
We've detected the first image tag with empty src attribute on 63th line of the document. We've also counted the total number of tags with empty src attribute in the document: 1. We recommend specify src attribute of img tag or remove this tag completely.

Using H1 tag

Show main content of the page clearly. One of the most important internal website ranking factors is the H1 tag. It's a title of the document and the most powerful keyword, actually. Our robot did not find the h1 tag on the page.

Content Semantics

We suggest you along with important and well-known tags like Title & H1 use also H2, H3, H4, H5, STRONG tags. Each page can (and should) highlight not only the main topic, but also complement the semantic core of the page and the whole site with the secondary keywords. For example, if the main topic of the page is dedicated servers, there is a probability that page has a blog about managed dedicated servers. If so try to highlight the title of the block by using tag <H2>, and an information that you provide this service in the United Kingdom highlight with H3 tag and so on. Thus try to highlight every important fragment of the information on your page with tags like STRONG, H2, H3, etc. We did not find H2 tags, H3 tags, H4 tags, H5 tags, STRONG tags on the page


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