Internet Explorer 7 (IE7) came out approximately 6 years after Internet Explorer 6 (IE6), a very long time between any two versions of software, but especially on the Internet. During this time, Internet Explorer 6 was the most common browser, and Microsoft took that for granted, and other, better browsers, came out.

IE7 was Microsoft’s response to Firefox, Safari, and Opera. With 6 years to develop the next generation of browser, you would expect the new version to have any and every feature under the sun. So let’s look at what it got right vs. what is got wrong during this time.

What IE7 got right

• IE7 includes an decent RSS reader.  IE6 didn’t support RSS at all, and Firefox’s and Safari’s built in readers are adequate for those who only check a few feeds.  IE7 actually has a useful RSS reader that remembers what you have seen.
• Tabs – every other browser had them, and now IE does as well.
• Improved security – built in security features help you determine, and protect you, if a site is potentially unsafe or might try to steal your information.  The protections tend to fall into three separate categories:
  • unsafe JavaScript and active X controls.  By limiting the ability for these to run, it protects you from both bad & nefarious programmers.
  • phishing sites – these are sites which try to steal your information, usually by masquerading as another site (eBay, your bank, PayPal, etc)
  • checking for security certificates – while this isn’t new, they present the danger of a site which has a bad or out of date security certificate more prominently, to increase the chance of you noticing this error
• Improved compliance with web standards.
• Support for PNG – now transparencies work.  This is a huge improvement which can allow smaller, yet better looking, images to be displayed on web sites.

What IE7 missed

• The interface. How you use your software is important, and IE7 changed/moved many of the menus and buttons.  This makes if difficult to use until you get used to it.  After using IE7 for over 9 months, I can honestly say, I’m still not that used to it. And while some elements were moved to take up less space, the over all feel for the browser is that the buttons are larger, and have large soft rounded edges, which ends up taking up more space.
• Tabs – While IE7 has them, they seem to be thrown in as an after thought.  Launching a new tab takes longer in IE7 than any other browser.
• Compliance with web standards – IE7 is the second least compliant of the major browsers when it comes to web standards, only after IE6. While it made great strides forward, it still has a ways to go. This main affects web developers and web site owners as they have to craft work arounds to make a site work correctly in all the browsers, but this does lead to larger sites that take longer to download, and sites which are harder to maintain over time. The fact that IE6 and IE7 are not standards compliant, leads many websites to not fully utilize the web as they could.
• Tight Integration with Windows – the part which Microsoft argued about bundling IE6 with Windows, still exist.  This tight integration, makes it a little faster (supposedly), however, it also puts you at higher risk of being affected by malicious code.
• Their security model – IE security in many ways has two modes, off and on. These limitations cause major issues if something needs to run, but is blocked.  Unblocking that one site can often open the door for many more sites and/or operations.  The same features which make IE easy to integrate with back office applications, also allow your system to be hacked, and without an easy way to block sites and/or operations, users get limited to either not being able to run all of the features of a site, or risking getting hacked.
• Lack of performance – many performance test show IE to be one of the slowest browsers on the market.

Related articles by Zemanta

• IE December Security Update Now Available
• Dump Internet Explorer. You are Vulnerable.
• IE8 Beta goes public – and what are those new features?
• Where to Find the IE Patch (KB960714)

Popularity: unranked [?]

Image via Wikipedia

I’ve recently been talking about Google’s new browser, Chrome, looking at why you might want to and not want to use it. So I thought I’d recap other browsers as well.

One which can’t be ignored is Internet Explorer 6 (IE6).

IE6 is probably the longest surviving web browser of all time, and is both loved and hated.

Ye old Browser

It came out in August of 2001, over 7 years ago at this point of this writing, which in Internet years means it might as well be over 700 years old.

While IE6 was highly touted as the most advanced browser when it was released, 7 years makes those features “old hat” . Newer browsers and versions have been released with even newer and better features since IE6′s initial release.

Why Upgrade

So why should you upgrade to a newer browser? Glad you asked:

1. Newer browsers have built in support to protect you from phishing attacks. These include displaying prominent messages when dealing with a potentially dangerous site.
2. Reduced chance of being hacked. IE6′s security model lends it self to being easy to hack your computer.
3. Improved support of web standards. – IE6 is the bane of web developers because of incompatibilities with current web standards, which provide an inconsistent experience compared to other browsers. Modern browsers tend to support standards more consistently.  This means that what you see on the screen is more likely to be correct, and web applications are more likely to work correctly.
4. Improved stability. IE6 is known to be a bit flaky, and crash when dealing with intense websites.
5. Improved User Interface. Most modern browsers have improved the user experience, including things like easier ways to organize your bookmarks/favorites, built in search box, etc.

Popularity: unranked [?]

Recently I downloaded the Firefox 3 web browser as part of the download day. I’ve been using Firefox since version 1, and have always like it. I find it is generally faster and more consistent than Internet Explorer, and also has fewer security holes.

This screen shot came up the day after I installed it. A link that I had followed from a trusted site took me to a site which apparently had been compromised.

Just another reason I enjoy using Firefox.

Popularity: 19% [?]

It’s one thing to look at your reports, its another to start to draw conclusions from your data. Different people will look at the data in different ways. Most often, the reports are looked at by the marketing department/person to see how to better market the site, what Search Engine optimization needs to occur, and measure the effectiveness of their pay-per-click ads. All of these are important uses of the web analytics, but they are not the only uses.

I want to look at a specific example of how I, as a web developer, recently went about making a site faster based upon the results of some analytics reports.

The 80/20 rule of the web

We’ve all heard of the 80/20 rule. On the web it would 80% of people only use 20% of your web site. In reality however, depending upon your site, it could be more like 90/10. A novice web developer will try to optimize all of the pages. An experienced web developer doesn’t bother with those pages that receive only the smallest amount of visitors.

On an Intranet web site I maintain, which tracks the employees’ internal education process, I was looking at the internal search feature. The search results are loaded into the same page. When you count the results from the searches, this page accounted for 24% of all of the page views, making it the second most visited page on the site. (The #1 page is mostly static text, so no real improvements could come from there.)

This means for every 2 people to visit the site, approximately 3 searches were performed in addition to the normal page load. So almost 1 out of every 4 page views was to this internal search engine, and some people were searching multiple times.

This became an area to consider improving. As a little improvement here, would have more effect than a large improvement on a page that is only viewed 1% or less of the time.

Too combat this, I decided to load the results in with AJAX instead of reloading the whole page. This process would improve search response in 3 ways.

Network Connections

Each time a file is downloaded over the Internet, the web browser checks to see if there is a newer version on the server, or if it can use a local file it has already downloaded (cached). Each time it checks to use a local version or downloads a new copy, the server is using up resources, and your end-user has to wait for the files to finish checking/downloading. Because the number of network connections has been reduced, other people can be accessing the site at a faster rate, and the end-user appears to be faster as they don’t have to have their computer do as much work.

The search page referenced 15 external files, plus itself. Of those 12 wouldn’t have to be called anymore. So I was able to reduce the number network connections by 80% for the search results. This was our biggest savings. The number of network connections on a web server is limited by both number and bandwidth speed, therefore the more connections, the slower each connection appears.

Processing of Files

Knowing in advance that it was going to be a popular page, I had tried to make the page as efficient as possible initially. However, with some of the features, like remembering the previous search criteria, because you never left the page, no longer needed, I was able to simplify the page.

The initial page load took about the same amount of time, however when the search results displayed, it appeared to be less than 1 hundredth of a second faster to process the file, about 4.45% faster. While individually it does not yield much savings, when applied as many times as it is with the popularity of the page, the savings adds up, especially during peak times.

Size of Results File Download

I knew I would save a lot in this area. The search interface, consisting of 6 controls, and a variety of other HTML sections, would no longer have to be duplicated in loading the results. This would mean faster downloads, and improved “perception” of the speed of the web page/server. Based on the same sample set of data, there was an 11K reduction in the overhead of the search results, or approximately 14% smaller download. This was for a search with over 100 results. However, many times fewer results (20-50) are returned. So the savings in bandwidth, while still approximately 11K, would be a much higher percentage (30-75%).

Final Thoughts

Because I could determine from our analytics package which files were being processed more, I was able to get the most bang for my buck. This update will take some load off the server, and allow all the pages to benefit from this enhancement. Likewise, almost every visitor will notice a performance improvement in the site because of how often this page is viewed.

This is how a web developer can effectively use web analytics to improve the performance of the web site.

Popularity: 23% [?]