Krak.dk

 
Ads by Google

Latency Testing Disabled.

SiteSpeedLab can't measure the latency of the krak.dk. While performing tests we do not get responses from the remote server 80.69.234.13.
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 3633 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 — — 1130 ms 148 % 40.23 Kb/s 50%
Florida, Tampa — — 273 ms 75 %
 Germany
 Frankfurt — — 111 ms 11 %
 Canada
 Montreal — — 329 ms —
 United Kingdom
 Gloucester — — 80 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 (Sweden, Bromma), we concluded
overall This website speed rank is 11. That means 11% of the sites from the Bromma 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 (80.69.234.13) 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.38s (which is better than 2% of all sites). For more detailed stats look at DNS tests graph and DNS resolve page for Sweden, Bromma 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 1130 ms — — — 7%
506/547 ms
Florida, Tampa 273 ms — — — 78%
522/293 ms
 Germany
 Frankfurt 111 ms — — — 13%
230/203 ms
 Canada
 Montreal 329 ms — — — 4%
212/221 ms
 United Kingdom
 Gloucester 80 ms — — — 6%
106/100 ms

Fragment of Bromma 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. Eniro.dk 37 ms Scandinavia Online Ab
2. Eniro.se 70 ms Scandinavia Online Ab
3. Eniro.com 74 ms Scandinavia Online Ab
... ... ... ... ...
42. Ticket.se 323 ms Teliasonera Ab
43. Travelbook.dk 343 ms Teliasonera Ab
44. Krak.dk 384 ms Scandinavia Online Ab
45. Sharepointforum.com 662 ms Telecity Plc
... ... ... ... ...
45. Sharepointforum.com 662 ms Telecity Plc

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 40.23Kb/s (which is better than 11% of all sites in this region). For more detailed stats check out report for Bromma 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 Krak.dk'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.krak.dk (19 files)
 Host enirocode.adtlgc.com (3 files)
 Host adtlgc.extserv.krak.dk (1 file)
 Host eas8.emediate.eu (4 files)
 Host eas.statcamp.net (2 files)
 Host eas4.emediate.eu (1 file)
 Host de17a.com (2 files)
 Host gadk.hit.gemius.pl (1 file)
 Host 23dd4b18-3527-490b-9d87-5f9588cb5b9b.statcamp.net (1 file)
 Host ocsp.godaddy.com (1 file)
 Host tracead.com (2 files)

Try to combine JavaScript files into one file.

This will reduce the time for requests for files and reduce the number of requests to the web server.
 enirocode.adtlgc.com (3 javascript files)
 www.krak.dk (4 javascript files)

Enable GZIP Compression

This is a good practice to give the user content in compressed form. We've detected 2.64 Kb of content that could be compressed. By compressing content you can achieve the size of ~ 0.66 Kb (saving 1.98 Kb). This would accelerate the page loading speed and would positively impact the bandwidth savings in Scandinavia Online Ab.
http://de17a.com/b/15/300x250/3.js?z=0.3049047555584107. File size 0.8 Kb and you can save up to 0.6 Kb
http://de17a.com/a/31666.iframe?rf=http%3A%2F%2Feas8.emediate.eu%2Feas.... File size 1.58 Kb and you can save up to 1.18 Kb
https://tracead.com/displayHandler.php?sId=2150&cId=2890&dnaId=1&userD.... File size 0.26 Kb and you can save up to 0.2 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.krak.dk/components/business/common/style/business-min.css?2...  Content-Encoding: text/css. File size 34.39 Kb.
http://www.krak.dk/components/business/common/scripts/business-min.js?...  Content-Encoding: application/x-javascript. File size 60.36 Kb.
http://www.krak.dk/frontpage-content/company/krak/media/krakspot01.swf  Content-Encoding: application/x-shockwave-flash. File size 36.83 Kb.
http://www.krak.dk/components/business/common/limg/sprite.png?201012060403  Content-Encoding: image/png. File size 92.58 Kb.
http://eas.statcamp.net/media.4/149/11252/98350/930x180norwegian_f98db...  Content-Encoding: image/jpeg. File size 42.25 Kb.
https://tracead.com/static/advertiser_files/2001/banner_25087.gif?uniq...  Content-Encoding: image/gif. File size 30.22 Kb.

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 6 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 /frontpage-content/company/krak/media/krak_spot_hvid.jpg dimensions:
375.   <img src="/frontpage-content/company/krak/media/krak_spot_hvid.jpg" alt="Sommerferie" width="IMAGE_WIDTH_HERE" height="IMAGE_HEIGHT_HERE">

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.

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:
353.   <a href="http://www.detHitter.dk"><img src= "/frontpage-content/company/krak/media/banner_dethitter_180x243_top.gif" alt="Det Hitter" style="vertical-align: bottom;"></a>
We suggest you to remake it in this way:
353.   <a href="http://www.detHitter.dk" title="brugte biler"><img src= "/frontpage-content/company/krak/media/banner_dethitter_180x243_top.gif" alt="Det Hitter" style="vertical-align: bottom;"></a>
Of course, you can (and should) use more proper phrase instead of the "brugte biler" that describes the link http://www.detHitter.dk.


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