Home Organic
Growth
Master
Planning
SEOMike™
Portfolio
Professional
Background
Personal
Background
SEOMike™
Blog
SEO
Services
 

Archive for April, 2010

Using Subdomains to Speed Your Site

Tuesday, April 27th, 2010

Effectively using subodomains on your website will decrease your page load time.  If your site is image-heavy your pages probably load slowly.  Web browsers load all elements of a page from one TCP connection stream and each TCP stream only gets so much bandwidth.  For example, if a page has seventy images to load (including your logo, nav items, etc), HTML content, java scripts, and flash elements, a web browser could have 100+ simultaneous TCP connections to a single URL.  One major benefit of using multiple subdomains to call specific elements it that it allows content to load out of sequence.  You might have seen sites that stall until a flash piece is loaded before displaying the rest of the page content.  If the site would have called the flash piece from a subdomain, it would be loaded separately from the HTML and it wouldn’t stall the page load.

A good way to set this up is to write your pages to call items from subdomains.  Subdomains count as separate hostnames in browsers and are treated as such.  Upon the initial load of the website, a DNS query is made to get the IP address of each hostname and then it’s cached.  If your homepage loads elements from multiple hostnames, all of those IPs are cached and no further DNS queries need to be made.  If page load time is an issue for your site you could setup a subdomain for all javascript, images, flash, etc.  In this example queries for HTML are loaded from the main URL, javascript from js.example.com, images from i.example.com, flash from f.example.com.  If your site requires 100 TCP connections from one hostname, the server handles those sequentially.  The first set is loaded and as an element is completed, the next item in line fills the slot.  Splitting up the calls between hostnames divides the number of connections in the queue.  In this case you might have 12 connections to js.example.com, 5 connections to example.com (for content), 70 connections to i.example.com, and 2 connections to f.example.com.  Each set of connections is loaded simultaneously thus letting each connection take as long as needed without delaying loading of the elements farther down the list.  This is a bit complex so I’ve created an image to illustrate the point.

single-urlmulti-sd

I have setup sites in this manner before to help overcome slow page-load times and saw a great increase.  The site was and ecommerce site with lots of thumbnails, featured products, logos, etc. and it was nice to be able to call them from a separate hostname so loading the images didn’t slow down the site.  Modern browsers will open 24 – 32 threads per hostname.  You should take advantage of as many as possible.

Too Many Webmasters Are Webamateurs!

Thursday, April 22nd, 2010
It’s happened to all of us.  We’ve been to a website that we expected to work correctly, but of course, it didn’t.  Who should we blame for these functionality problems?  The webmaster.  A webmaster is defined as “A technician who designs or maintains a website.”  Notice in that definition the mention of “designs.”  Almost all web designers forget about an extremely important part of their job: browser ubiquity testing.  I discussed this topic before, but I see so many silly mistakes on the web that the topic is always at the front of my mind.
A great example of a major web faux paux can be seen below.  Can you believe that Merrill Lynch calls Google Chrome an “incompatible browser?”  They say their compatible browsers are IE 5+, Netscape 7+ and Firefox 0.8+!  How long has it been since their webmaster actually thought about their site’s compatibility?  The Netscape browser isn’t available anymore, IE 5 is history, and Firefox has been through ELEVEN version updates since this message was implemented.  Where is the webmaster?!

It’s happened to all of us.  We’ve been to a website that we expected to work correctly, but of course, it didn’t.  Who should we blame for these functionality problems?  The webmaster.  A webmaster is defined as “A technician who designs or maintains a website.”  Notice in that definition the mention of “designs.”  Almost all web designers forget about an extremely important part of their job: browser ubiquity testing.  I discussed this topic before, but I see so many silly mistakes on the web that the topic is always at the front of my mind.

A great example of a major web faux pas can be seen below.  Can you believe that Merrill Lynch calls Google Chrome an “incompatible browser?”  They say their compatible browsers are IE 5+, Netscape 7+ and Firefox 0.8+!  How long has it been since their webmaster actually thought about their site’s compatibility?  The Netscape browser isn’t available anymore, IE 5 is history, and Firefox has been through ELEVEN version updates since this message was implemented.  Where is the webmaster?!

Merrill Lynch has a webamateur!

Merrill Lynch has a webamateur!

This is just one example of a lazy or inept webmaster.  I’d estimate that 80% or more of the websites on the internet have some browser compatibility issues.  Website troubles are not limited to the small-budget businesses that throw together sites, as you can see in the example.  I wonder how much money Merrill Lynch spent on their website.  I wonder if they know their site still does browser detection for browsers that were released in early 2004 – SIX years ago.

Google’s April Fool’s Fun

Thursday, April 1st, 2010
April Fools!
Google’s April Fool’s day joke this year was pretty amusing to this Kansan.
Last month the city of Topeka, the capitol of Kansas, officially changed it’s name to Google for a month in an effort to attract attention and win the bid to be the first city where Google tests their ultra-high speed internet service.  In an April Fool’s Day response, Google changed their name to Topeka.
x; width: 1px; height: 1px; overflow-x: hidden; overflow-y: hidden;”>Google Employees lined the street in front of the Mountain View CA headquarters.  Check out the screenshots I took with streetview:
Another amusing aspect of Google’s April Fool’s Day shanagans, is the fact that all of their search response times have been changed to other units of measure like (2.00 shakes of a lamb’s tail).  Here’s a list of the response times I recorded:
60.35 jiffies (interesting because this appears to be calibrated correctly.  A jiffy about 1 millisecond, and Google’s usual response times are 6-8 milliseconds.  So, the response time of 60.35 jiffies is equal  to about  6 milliseconds.  Nice Google)
0.74 times the velocity of a unladen swallow
0.23 centons
0.07 nanocenturies
1.22e-15 epochs
23.00 skidoo
0.22 microfortnights
0.19 centibeats
0.26 microweeks
2.00 shakes of a lamb’s tail
0.32e+43 Planck times (interestingly a jiffy used to mean Planck time)
at 5.21 hertz
1.21 gigawatts
11.90 parsecs
0.02 femtogalactic years
Another funny thing Google did on April Fool’s 2010 is post a promo saying that you can store anything on Google Documents, even your car keys.  ”Ever wish you could CTRL+F your keys?”  (Link)
Other Google April Fool’s pranks that get an honorable mention:
Google Maps in 3D
Google Books in 3D
Google standard voicemail: http://www.google.com/googlevoice/standard_voicemail.html
Google Translate for Animals (offered on google.co.uk)

Last month the city of Topeka, the capitol of Kansas, officially changed it’s name to Google for a month in an effort to attract attention and win the bid to be the first city where Google tests their ultra-high speed internet service.  In an April Fool’s Day response, Google changed their name to Topeka.

The April Fool’s idea that made me smile most was that the Google Employees lined the street in front of the Mountain View CA headquarters.  Check out the screenshots I took with streetview:

I also spotted a guy in the crowd with a marriage proposal sign:

Another amusing aspect of Google’s April Fool’s Day shanagans, is the fact that all of their search response times have been changed to other units of measure like (2.00 shakes of a lamb’s tail).  Here’s a list of the response times I recorded:

  • 60.35 jiffies (interesting because this appears to be calibrated correctly.  A jiffy about 1 millisecond, and Google’s usual response times are 6-8 milliseconds.  So, the response time of 60.35 jiffies is equal  to about  6 milliseconds.  Nice Google)
  • 0.74 times the velocity of a unladen swallow
  • 0.23 centons
  • 0.07 nanocenturies
  • 1.22e-15 epochs
  • 23.00 skidoo
  • 0.22 microfortnights
  • 0.19 centibeats
  • 0.26 microweeks
  • 2.00 shakes of a lamb’s tail
  • 0.32e+43 Planck times (interestingly a jiffy used to mean Planck time)
  • at 5.21 hertz
  • 1.21 gigawatts
  • 11.90 parsecs
  • 0.02 femtogalactic years

Another funny thing Google did on April Fool’s 2010 is post a promo saying that you can store anything on Google Documents, even your car keys.  “Ever wish you could CTRL+F your keys?”

Other Google April Fool’s pranks that get an honorable mention:


newsletter software