I've done quite a bit of research into web analytics lately, and I have found a couple of things. Google analytics Is a great tool, but it cannot be the only tool an organization relies on. Because it is a purely JavaScript based, it is unable to catch browsers that do not have JavaScript enabled, this includes the search engine robots, some hand held devices, as well as a percent of users that manually turn this off. That being said we need a tool to parse the log files from the server and to give us information about these users, as well as providing us with "on demand" stats where as Google's stats are next day. The server logs also contain a wealth of other information that we are collecting automatically, so we might as well take advantage of it.

I have come to the conclusion that we need to use Google Analytics but we also need a tool that reads the server logs. There are quite a variety of tools that would fill this need. Google recently purchased Urchin who's web analysis product runs Google analytics, costs about $3k and will work with the Google Mini, Urchin also gives the ability to read logs from server software other than IIS (like apache, the software used for open source applications) .

Urchin will be releasing another version shortly, and this will be the first release since the Google buyout. Another option is WebTrends Analytics it costs about $4k. It Like Urchin will read both IIS and Apache logs, and has a web interface for users. The last product is NetTracker, it runs about $4k for the software, and another grand for support. it was recently bought out by Unica. The administration of netTracker is not the smoothest, and the support seems to have declined on quality since the buy out.

Like a lot of web developers, I'm not always that disciplined when it comes to the file naming convention I use and I sometimes end up with a situation whereby I have some files that are in lowercase, some that begin with a capital, and some that are a bit of a mixture.

One web site I maintain contains about 2000 web pages and has about 20,000 hyperlinks. As you can imagine, I had one of those sinking feelings when I was told that in order to migrate the web site to a new content management system, all the file names and hyperlinks would need to be changed to lowercase.

Whenever I am presented with a problem like this, my instinct is always to write a Perl script using one or more regular expressions to solve the problem. This particular situation was no exception.

Change a string to lowercase

The following regular expression changes all the characters in a string to lowercase. The first part of the regular expression finds a hyperlink, and the second part converts the string. (Just in case this article is not displayed correctly, there should be a single backslash in front of the 'L$1').

Change a filename to lowercase

Likewise, changing a filename itself is very simple. The following two lines perform the task quite nicely:

(Again, there should be a single backslash in front of the 'L$name'.)

If you need more information on how to incorporate the above code snippets into a complete script, feel free to contact me directly.

Did you know that your css code could be slowing down your website? Did you also know that there is a free solution out there that can help you optimize or reformat your css code for speed and readability? This article is going to explain the benefits of optimizing your css code and the reasons why all web designers should be doing it. First we need to take into account the 2 reasons why you would want to reformat your css: readability and optimization.

Readability

Having nicely formatted css that easily readable is very helpful when you are developing a site. Most of us (me included) can get pretty sloppy when in a hurry to develop code, and a formatter can really help out to make it more readable.

On development teams where both Macs and PCs are used, sometimes line breaks are not read correctly across platforms and your css can end up all on one line. A formatter can help get your code looking pretty again.

Optimization

The opposite of readability is optimization. One problem with CSS is that it can get pretty file-size heavy when designing with it - especially on complex layouts. Optimizing your CSS will strip out all unnecessary characters and leave your CSS lean and mean.

Optimizing css is great to do once you've finished your site and don't plan to work on the design very much anymore.

The css formatter is a great tool because it can do both! You can format for readability while you are designing, optimize when you go live, and reformat it for readability if you ever need to work on it again. It's really a 'win win' thing to do.