I just wanted to do a little shout out to any developers, to say that the early bird ticket deadline is fast approaching for this years PHPNW conference.

Tickets have been on sale for a while now at £58 (ex VAT) but this will go up on the 12th August to £75 so if your thinking of going, now’s the time to get your ticket.

For more information or to book your ticket goto http://conference.phpnw.org.uk/phpnw10/.

I mentioned last week on Twitter that I had been using the Fx4.0 alpha at home in preparation for the Fx4.0 Test Day (last Friday) and how impressed I was with it. Apart from the extra space saved from removing the title/menu bar the browser felt obviously faster and more stable than previous alpha and even beta releases.

Yesterday Mozilla announced the build has reached BETA and is ready for the more cautious developer to start playing with it. Firefox 4.0 comes with lots of new bells and whistles, you can find a full feature list here, most notable the new UI design and enhancements in <hmtl5> and CSS3. There are also lots of new developer api’s for us to play with including websockets and local indexeddb’s.

If your already surfing the beta channel wave, you should be able to just “upgrade now” although my work machine didn’t find it so had to install it manually. Those of you running a stable realease or want to install manually can do so via the usual beta release channel.

For more information on please read the Mozilla Announcement on their blog.

Google last night announced they have completed their migration to their new web indexing system known as ‘Caffeine’.

This new system basically allows them to push anything Googlebot finds into the main index in seconds rather than weeks.

Previously Googlebot would crawl the web, find a site, then submit its content to another system for processing. This other system would then sort and process the content and work out what its all about. It would then pass it to another system for inclusion in the index. This was a time consuming process and was also done in batches, which means your site would have to wait for all the other sites in the same batch to be processed before being submitted to the index.

The new system is different, rather than doing things in large batches, it will work on smaller portions, more portions at the same time and submit them all to the index straight away, allowing users of the search engine to see information much much quicker, and this is just the start!

Image copyright of Google

There are several rumours floating around about what lies in store next for Google users and their shot of caffeine.  But for now we will have to wait and just enjoy our new “real-time” search results.

You can real the full article on the Google Webmaster Blog

Google made a post the other day about “Me and site performance, sitting in a tree…” so I thought before we get to the “…k, i, s, s, i, n, g!” I should give her a run for her money, check she is good enough for me.

First thing the post suggest is to check out Site Performance in Webmaster tools, so off I went. When this first appeared in the Labs section of webmaster tools it was updating pretty regularly and was quite useful and as the graph shows helped me tweak a few things and improve the load time of the server. But it hasn’t been updated in a while now so isn’t very relevant or useful to me.

Next thing it suggests is to install Page Speed for Firebug and test my site. So thats what I did and I got Page Speed Score: 93/100! which is pretty impressive. So I thought next, 7% to go, what can I do to get to 100/100. Nothing it seems… All the suggestions the tool gave me were unsolvable and prevent anyone from getting top marks.

The first suggestion is to Leverage browser caching,
the file it advises me need to do this too is “http://www.google-analytics.com/ga.js” which I cant do anything about.

The next suggestion is to Defer loading of JavaScript, “66.4% of the JavaScript loaded by this page had not been invoked by the time the onload handler completed” is smugly informs me.
- http://gavtaylor.co.uk  24 functions uncalled of 25 total functions
- http://www.google-analytics.com/ga.js 154 functions uncalled of 243 total functions.

On closer examination the functions it reports on my site are actually from Firebug, which must be open for the test to run? catch 22 there!
And the analytic code again is from Google and I cant do anything about that.

The final suggestion is to Use efficient CSS selectors,
http://gavtaylor.co.uk/core/styles/styles.css has 12 very inefficient rules, 27 inefficient rules, and 0 potentially inefficient uses of :hover out of 101 total rules.

This I can do something about and when I get a moment I will be re-coding my CSS file. But this wont improve my results more than 1 or 2 points.

So this unreachable target of 100/100 appears to be impossible. I could remove the Google code from my site which would resolve the Google plug-in issue but I cant run the test without having Firebug open so there will always be 24 out of 25 uncalled functions reported keeping me away from that 100/100 score.

So… will I be sitting in that tree, doing things I should not be?… No, not until they fix the issues with their testing tools anyway…

Microsoft’s IE development team have announced their first developer preview for the latest version of Internet Explorer.

IE9 is rumoured to include several <html5> and CSS3 elements, making it a real contender in the new range of “modern browsers”.

You can read more about the release on the IE Blog, or jump straight over to the resources and “test drive” the new release.

I will update this post with my thoughts on the preview, once I’ve had a play with it.