Title: 10 Realistic Steps to a Faster Web Site
Author: Alex Kirk
Published: February 2, 2006
Last modified: August 17, 2007

---

# 10 Realistic Steps to a Faster Web Site

February 2, 2006

I complained [before](https://alex.kirk.at/2006/01/03/49/) about [bad guides to improve the performance](https://alex.kirk.at/2006/01/03/49/)
of your website.

[digg it](http://digg.com/programming/10_Realistic_Steps_to_a_Faster_Web_Site), 
[add to delicious](http://del.icio.us/post?v=2&url=http%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F&title=10%20Realistic%20Steps%20to%20a%20Faster%20Web%20Site)

I’d like to give you a more realistic guide on how to achieve the goal. I have written
my [master thesis in computer sciences](https://alex.kirk.at/papers/caching-strategies/diploma_thesis.html)
on this topic and will refer to it throughout the guide.

**1. Determine the bottleneck**
 When you want to improve the speed of your website,
you feel that it’s somehow slow. There are various points that can affect the performance
of your page. Here are the most common ones.

Before we move on, you should always remember that you answer each question with
your target audience in mind.

**1.1. File Size**
 How much data is the user required to load before (s)he can 
use the page.

It is a frequent question, how much data your web page is allowed to have. You cannot
answer this unless you know your target audience.

In the early years of the internet one would suggest a size of 30k max for the whole
page (including images, etc.). Now that many people have a broadband connection,
I think we can push the level to a value between 60k and 100k. Although, you should
consider lowering the size if you also target modem users.

Still, the less data you require to download, the faster your page will appear.

**1.2. Latency**
 The time it takes between your request to the server and when 
the data reaches your PC.

This time adds together from twice the network latency (which depends on the uplink
of the hosting provider, the geographical distance between server and user, and 
some other factors) and the time it takes until the server produces the output.

Network latency can hardly be optimized without moving the server, so this guide
will not cover this.
 The processing time of the server combines complex time factors
and contains most often much room for improvement.

**2. Reducing the file size**
 First, you need to know how large your page really
is. There are some useful tools out there. I picked [Web Page Analyzer](http://www.websiteoptimization.com/services/analyze/index.html)
which does a nice job at this.

I suggest not spending too much time on this, unless your page size is larger than
100kb. So skip to step 3.

Large page sizes are nowadays often caused by large JavaScript libraries. Often 
you only need a small part of their functionality, so you could use a cut-down version
of it. For example when using prototype.js just for Ajax, you could use [pt.ajax.js](https://alex.kirk.at/2005/10/05/prototypejs-just-for-ajax/)(
also see [moo.ajax](http://www.mad4milk.net/entry/moo.ajax)), or the [moo.fx](http://moofx.mad4milk.net/)
as a script.aculo.us replacement.

[Digg](http://digg.com/) for example used to have [about 290kb](http://project-2501.net/?view=document&id=525),
they now have reduced the size to [160kb](http://www.websiteoptimization.com/services/analyze/wso.php?url=digg.com)
by leaving out unnecessary libraries.

Also large images can cause large file sizes, this is often caused by the wrong 
image format. A rule of thumb: JPG for photos, PNG for most other aspects, especially
if plain colors are involved. Also: use PNG for screen shots, JPGs are not only 
larger but also look ugly. You can also use GIF instead of PNG when the image has
only few colors and/or you want to create an animation.

Also often large images are scaled via the HTML `width` and `height` attributes.
You should do this in your graphical editor and scale it there. This will also reduce
the size.

Old HTML style can also cause large file size. There is no need for thousands of
tags anymore. Use [XHTML](http://www.w3.org/TR/xhtml11/) and [CSS](http://www.w3.org/Style/CSS/)!

A further important step to smaller size is on-the-fly compressing of your content.
Almost all browsers already support [gzip compression](http://en.wikipedia.org/wiki/Gzip).
For an Apache 2 web server, for example, there is the [mod_deflate](http://httpd.apache.org/docs/2.0/mod/mod_deflate.html)
module can do this transparently for you.

If you don’t have access to your server’s configuration, you can use the [zlib](http://php.net/zlib)
for PHP or for Django (Python) there is [GZipMiddleware](http://www.djangoproject.com/documentation/middleware/#django-middleware-gzip-gzipmiddleware),
Ruby on Rails has a [gzip plugin](http://wiki.rubyonrails.org/rails/pages/Output+Compression+Plugin),
too.

Beware of compressing JavaScript, there are [quite](http://support.microsoft.com/kb/312496)
[some](http://support.microsoft.com/kb/871205) bugs with Internet Explorer.

And for heaven’s sake, you can also strip the white space after you’ve completed
the previous steps.

**3. Check what’s causing a high latency**
 As mentioned, the latency can be caused
by two large factors.

**3.1. Is it the network latency?**
 To determine whether the network latency is
the blocking factor you can ping your server. This can be done from the command 
line via the command `ping servername.com`

If your server admin has disabled the pinging function you can also use a traceroute
which uses another method to determine the time `tracert servername.com` (Windows)
or `traceroute servername.com` (Unix).

If you address an audience that is geographically not very close to you, you can
also use a service such as [Just Ping](http://www.just-ping.com/) which pings the
given address from 12 different locations in the world.

**3.2. Does it take too long to generate the page?**
 If the ping times are ok, 
it might take too long to generate the page. Note that this applies to dynamic pages,
for example written in a scripting language such as PHP. Static pages are usually
served very quickly.

You can measure the time it takes to generate the page quite easily. You just need
to save an time stamp at the beginning of the page and subtract it from the time
stamp when the page has been generated. For example in PHP you do it like this (
due to technical restrictions a space is inserted before the question mark):

`< ?php // Start of the Page $start_time = explode(' ', microtime()); $start_time
= $start_time[1] + $start_time[0]; ?>`

and at the end of the page:

`< ?php $end_time = explode(' ', microtime()); $total_time = $end_time[0] + $end_time[
1] - $start_time; printf('Page loaded in %.3f seconds.', $total_time); ?>`

The time needed to generate the page is now displayed at the bottom of it.

You can also compare the time between loading a static page (often a file ending
in .html) and a dynamic one. I’d advise to use the first method because you are 
going to need that method to go on optimizing the page.

You can also use a [Profiler](http://en.wikipedia.org/wiki/Profiler_(computer_science))
which usually offers even more information on the generation process.

For PHP you can, as a first easy step, enable [Output Buffering](http://php.net/ob_start)
and restart the test.

Also you should consider testing your page with a benchmarking program such as [ApacheBench (ab)](https://alex.kirk.at/papers/caching-strategies/diploma_thesisch4.html#x8-510004.8).
This will stress the server via requesting several copies at once.

It is difficult to say what time suffices for generating a web page. It depends 
on your own requirements. You should try to keep the generation time under 1 second,
as this is a delay which users usually can cope with.

**3.3. Is it the rendering performance?**
 This plays only a minor role in my guide,
but still this can be a reason why your page takes long to load.

If you use a complex table structure (which can render slowly), you most probably
are using old style HTML, try to switch to XHTML and CSS.

Don’t use overly complex JavaScript, like slow scripts in combination with `onmousemove`
events make a page real sluggish. If your JavaScript makes the page load slowly (
you can use a similar technique as the PHP time measuring, using the `(new Date()).
getMilliseconds()`), you are doing something wrong. Rethink your concept.

**4. Determine the lagging component(s)**
 As your page usually consists of more
than one component (such as header, login window, navigation, footer, etc.) you 
should next check which one needs tuning. You can do this by integrating a few of
the measuring fragments to the page which will show you several split times throughout
the page.

The following steps can now be applied to the slowest parts of the page.

**5. Enable a Compiler Cache**
 Scripting languages recompile their script upon 
each request. As there are far more requests to the unchanged script, it makes no
sense to compile the script over and over (especially when core development has 
finished).

For PHP there is amongst others [APC](http://pecl.php.net/apc) (which will probably
be integrated with [PHP 6](http://www.php.net/~derick/meeting-notes.html#add-an-opcode-cache-to-the-distribution-apc)),
Python stores a [compiled version](http://www.python.org/doc/2.2.3/tut/node8.html#SECTION008120000000000000000)
by itself.

**6. Look at the DB Queries**
 At university most complex queries with lots of JOINs
and GROUPs are taught, but in real life it can often be useful to avoid JOINs between(
especially large) tables. Instead you do multiple selects which can be cached by
the SQL server. This is especially true if you don’t need the joined data for every
row. It really depends on your application, but trying without a JOIN is often worth
it.

Ensure that you use query folding (also called query cache; such as the [MySQL Query Cache](https://alex.kirk.at/papers/caching-strategies/diploma_thesisch4.html#x8-350004.3.2)).
Because in a web environment the same SELECT statements are executed over and over.
This almost screams for a cache (and explains why avoiding JOINs can be much faster).

**7. Send the correct Modification Data**
 Dynamic Web pages often make one big 
mistake: They don’t have their date of last modification set. This means that the
browser always has to load the whole page from the server and cannot use its cache.

In HTTP there are various headers important for caching: for 1.0 there is the `Last-
Modified` header which plays together with the browser-sent `If-Modified-Since` (
see [specification](http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.1)).
HTTP 1.1 uses the `ETag` (so called [Entity Tag](http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.2))
which allows different last modification dates for the same page (e.g. for different
languages). Other relevant headers are `Cache-Control` and `Expires`.

Read on about [how to set the headers correctly and respond to them (1.0)](https://alex.kirk.at/papers/caching-strategies/diploma_thesisch6.html#x17-720006.1.1)
and [1.1](http://simon.incutio.com/archive/2003/04/23/conditionalGet).

**8. Consider Component Caching** (advanced)
 If optimizing the database does not
improve your generation time enough, you are most likely doing something complex;)
So for public pages it’s very likely that you will present two users with the same
content (at least for a specific component). So instead of doing complex database
queries, you can store a pre-rendered copy and use that when needed, to save time.

This is a rather complex topic but can be the ultimate solution to your performance
problems. You need to make sure that you don’t deliver a stale copy to the client,
you need think about how to organize your cache files so you can invalidate them
quickly.

Most web frameworks give you a hand when doing component caching: for PHP there 
is [Smarty’s template caching](https://alex.kirk.at/papers/caching-strategies/diploma_thesisch9.html#x25-1040009),
Perl has [Mason’s Data Caching](http://www.masonhq.com/docs/manual/Devel.html#data_caching),
Ruby’s Rails has [Page Caching](http://api.rubyonrails.com/classes/ActionController/Caching/Pages.html),
Django [supports it as well](http://www.djangoproject.com/documentation/cache/).

This technique can eventually lead to a result when loading your page does not need
any request to the data base. This can be a favorable result as a connection to 
the database is often the most obvious bottleneck.

If your page is not that complex you could also consider just caching the whole 
page. This is easier but makes the page usually feel less up-to-date.

One more thing: If you have enough RAM you should also consider storing the cache
files in a RAM drive. As the data is discardable (as it can be re-generated at any
time) a loss when rebooting would not matter. Keeping disk I/O low can boost the
speed once again.

**9. Reducing the Server Load**
 Consider that your page loads quickly and everything
looks alright, but when too many users access the page, it suddenly becomes slow.

This is most likely due to a lack of resources on the server. You cannot add an 
indefinite amount of CPU power or RAM into the server but you can handle what you’ve
got more carefully.

**9.1. Use a Reverse Proxy** (needs access to the server)
 Whenever a request needs
to be handled, a whole copy (or child process) of the web server executable needs
to be held in memory. Not only for the time of generating the page but also until
the page has been transferred to the client. Slow clients can cost performance. 
When you have many users connecting, you can be sure that quite a few slow ones 
will block the line for somebody else just for transferring back the data.

So there is a solution for this. The well known Squid proxy has a [HTTP Acceleration](https://alex.kirk.at/2005/11/29/squids-http-acceleration-mode/)
mode which handles communication with the client. It’s like a secretary that handles
all communication.

It waits patiently until the client has filed his request. Asks the web server to
respond, quickly receives the response (while the web server can move on to the 
next request) and then will patiently return the file to the client.

Also the Squid server is small, lightweight, and specialized for that task. Therefore
you need less RAM for more clients which allows a higher throughput (regarding served
clients per time unit).

**9.2. Take a lightweight HTTP Server** (needs access to the server)
 Often people
also say that Apache is quite huge and does not do it’s work quickly enough. Personally
I am satisfied with its performance, but when it comes to dealing with scripting
languages that handle their web server communication via the (fast)CGI interface,
Apache is easily trumped by a lightweight alternative.

It’s called [LightTPD](http://www.lighttpd.net/) (pronounced “lighty”) and does 
a good job at doing that special task very quickly. You can already see from a [configuration file](http://www.lighttpd.net/documentation/configuration.html)
that it keeps things simple.

I suggest testing both scenarios if you gain from using LightTPD or if you should
stay with your old web server. The Apache Web Server is stable and is built on long
lasting experience in the web server business, but LightTPD is taking it’s chance.

**10. Server Scaling** (extreme technique)
 Once you have gone through all steps
and your page still does not load fast enough (most obvious because of too many 
concurrent users), you can now duplicate your hardware. Because of the previous 
steps there isn’t too much work left.

The Reverse Proxy can act as a load balancer by sending its requests to one of the
web servers, either quite-randomly ([Round Robin](http://en.wikipedia.org/wiki/Round-robin))
or server load driven.

**Conclusion**
 All in all you can say that the main strategy for a large page is
a combination of caching and intelligent handling of the resources helps you reach
the goal. While the first 7 steps apply to any page, the last 3 points are usually
only useful (and needed) at sites with many concurrent users.

The guide shows that you don’t need a special server to withstand [slashdotting](http://slashdot.org/)
or [digging](http://digg.com/).

**Further Reading**
 For more detail on each step I recommend taking a look at my
[diploma thesis](https://alex.kirk.at/papers/caching-strategies/diploma_thesis.html).

MySQL tuning is nicely described in [Jeremy Zawodny’s](http://jeremy.zawodny.com/blog/)
[High Performance MySQL](http://highperformancemysql.com/). A presentation about
how [Yahoo tunes its Apache Servers](http://public.yahoo.com/~radwin/talks/yapache-apachecon2005.htm).
Some tips for [Websites running on Java](http://www.javaperformancetuning.com/tips/j2ee_srvlt.shtml).
[George Schlossnagle](http://www.schlossnagle.org/~george/blog/) gives some good
tips for caching in his [Advanced PHP Programming](http://www.samspublishing.com/bookstore/product.asp?isbn=0672325616&rl=1).
His tips are not restricted to PHP as a scripting language.

[digg it](http://digg.com/programming/10_Realistic_Steps_to_a_Faster_Web_Site), 
[add to delicious](http://del.icio.us/post?v=2&url=http%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F&title=10%20Realistic%20Steps%20to%20a%20Faster%20Web%20Site)

performance, tuning, website

[Code](https://alex.kirk.at/category/code/), [Web](https://alex.kirk.at/category/web/)

Read this next

[Blummy: Major Update](https://alex.kirk.at/2006/01/23/blummy-major-update/)

## 53 responses to “10 Realistic Steps to a Faster Web Site”

 1.   [Ajaxian](http://ajaxian.com/?p=815)
 2.   [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-136)
 3.   **Keeping your page load fast**
 4.    Alexander Kirk (of Blummy and Wizlite fame) posted 10 Realistic Steps to a Faster
      Web Site. Alex did his thesis on this subject, so he should know a thing or two
      about it. This is not strictly Ajax related, but its very easy to create a slow,
      unplea…
 5.   [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 6.   [Ajaxian » Keeping your page load fast](http://ajaxian.com/archives/keeping-your-page-load-fast)
 7.   [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-137)
 8.   […] Alexander Kirk (of Blummy and Wizlite fame) posted 10 Realistic Steps to 
      a Faster Web Site. Alex did his thesis on this subject, so he should know a thing
      or two about it. This is not strictly Ajax related, but its very easy to create
      a slow, unpleasant Ajax app if you don’t keep certain things in mind while developing.[…]
 9.   [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 10.  [La brujula verde » Acelera la carga de tu web](http://www.labrujulaverde.com/2006/02/02/acelera-la-carga-de-tu-web/)
 11.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-138)
 12.  […] Alex Kirk nos enseña 10 pasos para acelerar la carga de nuestra web. [Vía
      Ajaxian] […]
 13.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 14.  ![Justin Laing Avatar](https://secure.gravatar.com/avatar/61542b6ddd5a04b66cafc1d786da8ef4a77c5283820e14c60eab83dcf7e2b185?
      s=48&d=mm&r=g)
 15.  [Justin Laing](http://www.justinlaing.com)
 16.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-139)
 17.  Awesome guide, very practical and well thought out. Thanks!
 18.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 19.  ![GeeksAreSexy Avatar](https://secure.gravatar.com/avatar/fb0dfaf713ec060742c7974c22f410110a97bb92abd784b8d0c7c0b28a79418d?
      s=48&d=mm&r=g)
 20.  [GeeksAreSexy](http://geeksaresexy.blogspot.com)
 21.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-143)
 22.  WOOT, comments are working now! :)
 23.  Kiltak
       [[Geeks Are Sexy] Tech. News](http://geeksaresexy.blogspot.com)
 24.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 25.  [ktolis’ weblog » alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site](http://iridium.csd.auth.gr/~ktolis/blog/?p=45)
 26.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-146)
 27.  […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site[…]
 28.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 29.  [TheMadAdmin » Blog Archive » Make your site faster—Finding the bottlen neck!!!](http://themadadmin.com/wp/?p=502)
 30.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-147)
 31.  […] Article about finding out why your page loads slow and what to do about it.[…]
 32.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 33.  [go phly a kite » 10 Realistic Steps to a Faster Web Site](http://www.phly.org/wordpress/1.5.2/htdocs/?p=40)
 34.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-148)
 35.  […] read more | digg story […]
 36.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 37.  ![Julio Nobrega Avatar](https://secure.gravatar.com/avatar/db07bc4de11b5db7d38ef5f5a63df4af294ae3966139c803a4a975a3b1719df1?
      s=48&d=mm&r=g)
 38.  [Julio Nobrega](http://www.inerciasensorial.com.br)
 39.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-149)
 40.  I would like to add one little tip if you’re really, really concerned with file
      sizes, that I saw when looking at Google’s homepage source code.
 41.  Don’t use the quotes around the HTML attributes when you can. Most browsers will
      parse cellpadding=4 and cellpadding=”4″ the same way.
 42.  I know that ommiting quotes is “wrong”, but then again, these little ” and ‘ 
      probably save Google a few thousand dollars in bandwidth costs a month.
 43.  Taking the digg.com homepage for example, which has 48.013 bytes when I save 
      to my computer, ended with 45.582 bytes after removing every quote. I know not
      every quote can be removed, but I bet digg owners would be very happy to save
      1Kb per page in bandwidth costs. Even compressed, these files have a 300 bytes
      difference. *If* Alexa.com is somewhat close on its pageviews counting, which
      shows digg.com with 120 Million, we’re talking about major dollars here :)
 44.  But I guess that much necessity of savings are only for a few websites…
 45.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 46.  [Musounderings » Blog Archive » 10 Steps to a Faster Website](http://blog.brandags.com/10-steps-to-a-faster-website.html)
 47.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-150)
 48.  […] On his blog, Austrian application programmer Alexander Kirk posts 10 Realistic
      Steps to a Faster Website. I found it a very good read. […]
 49.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 50.  ![Son Nguyen Avatar](https://secure.gravatar.com/avatar/d0b2d3a5fe30c33c1b9fd3318c18f8eb3e1d3d722ae24a137159e091762d45f2?
      s=48&d=mm&r=g)
 51.  [Son Nguyen](http://blog.trungson.com/)
 52.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-151)
 53.  Very nice. Short, to the point = Easy to remember.
 54.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 55.  ![Alexander Kirk Avatar](https://alex.kirk.at/wp-content/uploads/sites/2/2025/
      06/cropped-2025.Alex-512x512-1-48x48.jpg)
 56.  [Alexander Kirk](http://alex.kirk.at/)
 57.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-153)
 58.  Mandy,
       You could also use wget with the -r -l 1 flag (small L). Other parameters
      work with HTTP auth.
 59.  Josh,
       You got me wrong. I don’t want to tell people not to use the width and
      height attributes, but rather prevent them from using them to scale their images.
      Like if they take a 1024×768 picture and resize it to 640×480 by specifying the
      dimensions via width&height.
 60.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 61.  ![miscblogger Avatar](https://secure.gravatar.com/avatar/d4112c967ddf268d7dd9df8631e6804d8685fe444f5ee8ba013b1f4f500f4248?
      s=48&d=mm&r=g)
 62.  [miscblogger](http://www.freewarereview.info)
 63.  [February 2, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-154)
 64.  i love your 3.2 point. i’m going to try it on my websites!
 65.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 66.  [Geekier Geek » Keeping your page load fast – Because the others just aren’t geeky enough — blogging empire!](http://www.geekiergeek.info/syn/2006/02/02/keeping-your-page-load-fast/)
 67.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-158)
 68.  […] Alexander Kirk (of Blummy and Wizlite fame) posted 10 Realistic Steps to 
      a Faster Web Site. Alex did his thesis on this subject, so he should know a thing
      or two about it. This is not strictly Ajax related, but its very easy to create
      a slow, unpleasant Ajax app if you don’t keep certain things in mind while developing.[…]
 69.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 70.  ![kene Avatar](https://secure.gravatar.com/avatar/29f63b8a2a9da9a57986ab30ab097be85dd5079ab3b6b661f4f58f45830a1faf?
      s=48&d=mm&r=g)
 71.  [kene](http://www.justken.net)
 72.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-161)
 73.  a comment on the “quoting” issue from Julio Nobrega.
       Googles pages don’t conform
      to any standard. sure Googles pages work well, but they use a tiny subset of 
      html for each page, there’s nothing “fancy” about googles output. For a website
      that hope to be supported on a wider range of devices and browsers, while utilizing
      more features of css, javascript and html, not following the w3c’s recommendations
      is dangerous.
 74.  Alex suggests following the XHTML guidelines, and this in itself can speed up
      page rendering because an xhtml browser doesn’t need to respond to such a wide
      range of formats and styles, it knows that a tagname is all lowercase, all attributes
      are quoted and all tags are explicitly closed and properly nested. Just to name
      a few of the xhtml rules. This also means that a wider range of applications 
      like cellphones and other wap devices will be able render pages with smaller 
      parser engines because they don’t need to have fancy functions like strtolower
      or trying to figure out when a attribute value ends that’s not quoted.
 75.  If google used external css, they would save more bandwidth and speed up page
      rending far more than their omission of quotes, especially if their css was delivered
      with the proper caching and length headers. As it would be cached on the client’s
      computer the first time it was loaded, and subsequent requests would only require
      checking the headers.
       further, they could probably have reduced their need for
      attributes with better use of css. For example: all their tables contain information
      that could have been removed in favor of css alternatives, and they use font 
      tags (which are deprecated) extensively.
 76.  standards have been developed for a reason, and if the browser developers held
      rigid to standards, pages would render significantly faster, the browser’s themselves
      would be smaller and faster. However pages like google, and many others would
      all fail to display. Encouraging poor coding practice is a shortsighted plecibo
      for a much bigger problem.
 77.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 78.  [greencrab capsules » links for 2006-02-03](http://greencrab.wordpress.com/2006/02/02/links-for-2006-02-03/)
 79.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-162)
 80.  […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site(
      tags: web) […]
 81.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 82.  [Look What I Found » links for 2006-02-03](http://www.tartaglia.net/blog/archives/183)
 83.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-163)
 84.  […] 10 Realistic Steps to a Faster Web Site Some simple steps to improve web 
      speed. (tags: webdev) […]
 85.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 86.  [Labnotes » Blog Archive » links for 2006-02-03](http://blog.labnotes.org/2006/02/02/links-for-2006-02-03/)
 87.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-164)
 88.  […] 10 Realistic Steps to a Faster Web Site Simple rules that make all the difference.(
      tags: performance) […]
 89.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 90.  [somewhere in… blog » 10 steps for faster website](http://www.somewherein.net/blog/?p=245)
 91.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-165)
 92.  […] [http://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/](http://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/)[…]
 93.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 94.  [StickBlog » Blog Archive » Tips for optimising your web pages](http://the-stickman.com/web-development/tips-for-optimising-your-web-pages/)
 95.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-169)
 96.  […] I found this article on optimising web pages to be a very interesting read.
      In a previous working life, I spent all day worrying about this sort of thing
      but I’ve become lazy over the last few years. I need to buck my ideas up! […]
 97.  [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 98.  [Dunhill52 s’emballe » Blog Archive » ePress du jour n°3](http://blog.izalco.net/2006/02/epress-du-jour-nc2b03/)
 99.  [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-170)
 100. […] 10 Realistic Steps to a Faster Web Site […]
 101. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 102. ![Ivan Minic Avatar](https://secure.gravatar.com/avatar/979304108fdc93e7c9c3d1582d0dd3f9529bd3f6649912d81c57181918ab0c78?
      s=48&d=mm&r=g)
 103. [Ivan Minic](http://www.burek.co.yu)
 104. [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-171)
 105. Those are very nice tips ;) Thank you.
 106. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 107. ![Jesper Rønn-Jensen Avatar](https://secure.gravatar.com/avatar/8cad42a473ae8cb4dd80661516abcbcf43b4b31d17af6976742da7bffb438e58?
      s=48&d=mm&r=g)
 108. [Jesper Rønn-Jensen](http://justaddwater.dk/2006/01/14/ajax-performance-stats-roi-and-business-value/)
 109. [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-172)
 110. Very interesting read. Thanks for posting.
       Recently, I wrote about a system 
      that handled up to 4,000 requests per second using LightTPD. After reading your
      post, I wondered what’s the fastest: LightTPD or Apache+Squid ?
 111. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 112. [davidbisset.com » 10 Realistic Steps to a Faster Web Site](http://www.davidbisset.com/?p=3190)
 113. [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-174)
 114. […] Alexander Kirk’s steps go beyond surface changes and probably a read for 
      those who have a dedicated server. […]
 115. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 116. [10 Realistic Steps to a Faster Web Site at benwann.com](http://benwann.com/2006/02/03/10-realistic-steps-to-a-faster-web-site/)
 117. [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-175)
 118. […] Thanks Alexander! alexander kirk » Blog Archive » 10 Realistic Steps to
      a Faster Web Site 10 Realistic Steps to a Faster Web Site Thursday, February 
      2nd, 2006 at 11:56 0100 (CET) by Alexander Kirk I complained before about bad
      guides to improve the performance of your website. digg it, add to delicious 
      I’d like to give you a more realistic guide on how to achieve the goal. I have
      written my master thesis in computer sciences on this topic and will refer to
      it throughout the guide. […]
 119. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 120. ![m3nt0r Avatar](https://secure.gravatar.com/avatar/0e427da132285862fd8c5efc3e2d4aa53964cb3717305ea3cba95484b552f6d5?
      s=48&d=mm&r=g)
 121. [m3nt0r](http://www.m3nt0r.de)
 122. [February 3, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-176)
 123. Really nice article. Thanks.
 124. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 125. ![Cheyne Avatar](https://secure.gravatar.com/avatar/5a8d654b6c5ee99ca7977dd0fcce0c7794b1fda064220642f41339f647341897?
      s=48&d=mm&r=g)
 126. [Cheyne](http://www.thewebdesignblog.com)
 127. [February 5, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-180)
 128. Very helpful and thorough article.
 129. You have been blogged on [http://www.thewebdesignblog.com](http://www.thewebdesignblog.com)
 130. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 131. [The Web Design Blog](http://www.thewebdesignblog.com/2006/02/05/ten-realistic-steps-to-a-faster-web-site/)
 132. [February 5, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-181)
 133. […] This a fantastic article on what you can do to reduce your website’s loading
      time. It’s obviously an important one, and would be a whole lot easier if initiated
      in the design stage. The article explains in detail each thing you can do make
      your page that little bit faster. « Partial opacity for text over images   […]
 134. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 135. [links for 2006-02-04 at bluno.org](http://www.bluno.org/2006/02/03/links-for-2006-02-04/)
 136. [February 5, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-186)
 137. […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site(
      tags: web design) […]
 138. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 139. ![Break News Avatar](https://secure.gravatar.com/avatar/e2cc460a84108e6e7979464bb2182c8179b7deb23881f809862b7c959acd2044?
      s=48&d=mm&r=g)
 140. [Break News](http://celebrity-news.net)
 141. [February 6, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-187)
 142. Good article, very detailed and arguable
 143. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 144. [Donghai Ma » links for 2006-02-04](http://donghaima.wordpress.com/2006/02/04/links-for-2006-02-04/)
 145. [February 7, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-188)
 146. […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site(
      tags: tips reference web programming software) […]
 147. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 148. [IT-AFFIN » Webseitendownloadzeit optimieren](http://www.it-affin.de/2006/02/10/webseitendownloadzeit-optimieren/)
 149. [February 10, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-190)
 150. […] 10 Realistic Steps to a Faster Web Site ist eine ausgezeichnete Anleitung,
      wie man Webseiten optimieren kann. Ziel: Der User soll die Seite schneller anschauen
      können. Sehr, sehr gut! […]
 151. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 152. ![WebtrafficJunkie Avatar](https://secure.gravatar.com/avatar/e1d052a4257815ad956bc199cc373ab6dd5519eed46ed84d0faad4b3b66b4063?
      s=48&d=mm&r=g)
 153. [WebtrafficJunkie](http://www.websitetrafficandconversion.com)
 154. [February 13, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-194)
 155. This is an awesome article. I learned a lot of great tips and pointers. Thanks
      for the information!!
 156. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 157. [XOOPS CHINA – WordPress](http://xoops.org.cn/modules/wordpress/?p=276)
 158. [February 14, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-196)
 159. […] Alexander Kirk published an article 10 Realistic Steps to a Faster Web Site
      based on his master thesis in computer sciences. […]
 160. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 161. [沙發上的聯想 » Blog Archive » 10 Realistic Steps to a Faster Web Site](http://61.64.252.168:8080/knowledgebase/?p=22)
 162. [February 17, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-203)
 163. […] article:[http://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/](http://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/)[…]
 164. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 165. [Blog of Leonid Mamchenkov » Daily del.icio.us bookmarks](http://mamchenkov.net/wordpress/?p=9938)
 166. [February 28, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-224)
 167. […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site
      Tagged as: development lists optimization performance programming tips top10 
      tuning web […]
 168. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 169. ![penis enlargement Avatar](https://secure.gravatar.com/avatar/6a7c8e35dc26fbbc7c7ff9040123ae27ba3ccdbef6f44a472cd665e57a793036?
      s=48&d=mm&r=g)
 170. [penis enlargement](http://www.oksextoys.com)
 171. [March 14, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-258)
 172. I agree with you the way you view the issue. I remember Jack London once said
      everything positive has a negative side; everything negative has positive side.
      It is also interesting to see different viewpoints & learn useful things in the
      discussion. For example : do [penis enlargement pills](http://www.oksextoys.com)
      work for you ?
 173. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 174. ![smith Avatar](https://secure.gravatar.com/avatar/8c59d92f67290b7ae6157618bfbdf3ab44908c5dfbe5a9980527520b93baee43?
      s=48&d=mm&r=g)
 175. [smith](http://www.fastestinternetguide.com)
 176. [March 21, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-276)
 177. criticle site u have launched with prity link
 178. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 179. [otro blog más » Unos cuantos de desarrollo web (LXXXIII)](http://obm.corcoles.net/20060401/unos-cuantos-de-desarrollo-web-lxxxiii/)
 180. [April 1, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-481)
 181. […] La velocidad (y el tamaño, por tanto…) sí importa: 10 pasos realistas hacia
      un sitio web más rápido. […]
 182. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 183. ![Micah Z Avatar](https://secure.gravatar.com/avatar/a158cbb2d70cb82455569e76d8e8dcf6eef7e771e1fe8e433885638d477a3e44?
      s=48&d=mm&r=g)
 184. [Micah Z](http://zenomi.com)
 185. [April 6, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-506)
 186. Wow, this was an awesome article. Thanks a bunch for taking the time to publish
      it. I’m currently in the process of launching a new personal site and I’m building
      the backend from the ground up, so this was quite helpful. Plus, being on a limited
      budget I don’t want to have to spend extra for more bandwidth, so this is really
      helpful on more than one level.
 187. Thanks again.
 188. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 189. [The Unkaizened Life » Blog Archive » links for 2006-02-03](http://www.theunkaizenedlife.net/2006/02/03/links-for-2006-02-03/)
 190. [April 9, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-528)
 191. […] 10 Realistic Steps to a Faster Web Site (tags: 2do fast) […]
 192. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 193. [Breyten’s Dev Blog » Blog Archive » links for 2006-02-04](http://breyten.wordpress.com/2006/02/04/links-for-2006-02-04/)
 194. [April 9, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-529)
 195. […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site“
      I’d like to give you a more realistic guide on how to achieve the goal. I have
      written my master thesis in computer sciences on this topic and will refer to
      it throughout the guide.” (tags: web development webdesign performance webdev
      tips) […]
 196. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 197. [Frederic de Villamil .com » Blog Archive » 10 méthodes pour optimiser la rapidité d’un site Internet](http://fredericdevillamil.com/10-methodes-pour-optimiser-la-rapidite-dun-site-internet/)
 198. [April 18, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-590)
 199. […] Alexander Kirk propose un excellent document envisageant 10 pistes réalistes
      pour optimiser la rapidité d’un site Internet, et plus encore d’une application
      Web dont les besoins en réactivité égalent les applications en client lourd.[…]
 200. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 201. [Airabove | Online portfolio of swedish web designer and graphical artist Robert Arnesson](http://www.airabove.com/index.php/67)
 202. [April 19, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-599)
 203. […] Go to top No Comments so far Leave a comment RSS feed for comments on this
      post. TrackBack URI Leave a comment Line and paragraph breaks automatic, e-mail
      address never displayed, HTMLallowed: <a href="" title=""> <abbr title=""> <acronym
      title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> Name […]
 204. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 205. [100 Top links for Article : Top Links : eConsultant](http://www.econsultant.com/top-links/top-popular-article-sites.html)
 206. [July 29, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-4034)
 207. […] alexander kirk » Blog Archive » 10 Realistic Steps to a Faster Web Site[…]
 208. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 209. ![web design Avatar](https://secure.gravatar.com/avatar/54b31442d471573c35e1c123ffde9ced379d7c497689e8c0b1052cb00ba8e07d?
      s=48&d=mm&r=g)
 210. [web design](http://www.miraclestudios.in)
 211. [August 8, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-4249)
 212. Great reasource
 213. Quite commendable work
 214. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 215. [Programming » 10 Realistic Steps to a Faster Web Site](http://www.programmingnews.org/programmers/10-realistic-steps-to-a-faster-web-site/)
 216. [August 23, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-4628)
 217. […] Not the usual guide suggesting to strip all white space. This guide speaks
      about generation time of sites and how to optimize it.read more | digg story […]
 218. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 219. ![Web Programmer India Avatar](https://secure.gravatar.com/avatar/c614f1ee6b508b38e942870e83b73f1fb6a7b367ef9cff140b55dde1006f83e7?
      s=48&d=mm&r=g)
 220. [Web Programmer India](http://www.dassnagar.com)
 221. [September 10, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-5164)
 222. Ajax has made things simple and we can now remove java scripts which was troblesome
      in search engines.
 223. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 224. [The Life and Times of Shibz » Web Development Tutorials](http://shibz.com/2006/11/15/web-development-tutorials/)
 225. [November 15, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-12120)
 226. […] 10 Realistic Steps to a Faster Web Site by Alexander Kirk […]
 227. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)
 228. [DLife » AJAX资料大全](http://my.donews.com/dlife/2006/11/24/ajax-tutorials/)
 229. [November 24, 2006](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/#comment-14085)
 230. […] 10 Realistic Steps to a Faster Web Site by Alexander Kirk […]
 231. [Log in to Reply](https://alex.kirk.at/wp-login.php?redirect_to=https%3A%2F%2Falex.kirk.at%2F2006%2F02%2F02%2F10-steps-to-a-faster-web-site%2F)

 [Newer Comments](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/#comments)

### Leave a Reply 󠀁[Cancel reply](https://alex.kirk.at/2006/02/02/10-steps-to-a-faster-web-site/comment-page-1/?output_format=md#respond)󠁿

Only people in [my network](https://alex.kirk.at/friends/) can comment.

This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/)