The Three Principles Of HTML Code Optimization

Written by George Peirson

Just like spring cleaning a house,repparttar html code of your web pages should get periodic cleaning as well. Over time, as changes and updates are made to a web page,repparttar 145892 code can become littered with unnecessary clutter, slowing down page load times and hurtingrepparttar 145893 efficiency of your web page. Cluttered html can also seriously impact your search engine ranking.

This is especially true if you are using a WYSIWYG (What You See Is What You Get) web design package such as FrontPage or Dreamweaver. These programs will speed up your web site creation, but they are not that efficient at writing clean html code.

We will be focusing this discussion onrepparttar 145894 actual html coding, ignoring other programming languages that may be used in a page such as JavaScript. Inrepparttar 145895 code examples I will be using ( and ) characters instead of correct html so thatrepparttar 145896 code examples will display properly in this newsletter.

Up until recently when coding a page in HTML we would be using tags such asrepparttar 145897 (font) tag and (p) paragraph tags. Between these tags would be our page content, text, images and links. Each time a formatting change was made onrepparttar 145898 page new tags were needed with complete formatting forrepparttar 145899 new section. More recently we have gainedrepparttar 145900 ability to use Cascading Style Sheets, allowing us to writerepparttar 145901 formatting once and then refer to that formatting several times within a web page.

In order to speed up page load times we need to have fewer characters onrepparttar 145902 page when viewed in an html editor. Since we really do not want to remove any of our visible content we need to look torepparttar 145903 html code. By cleaning up this code we can remove characters, thereby creating a smaller web page that will load more quickly.

Over time HTML has changed and we now have many different ways to dorepparttar 145904 same thing. An example would berepparttar 145905 code used to show a bold type face. In HTML we have two main choices,repparttar 145906 (strong) tag andrepparttar 145907 (b) tag. As you can seerepparttar 145908 (strong) tag uses 5 more characters thanrepparttar 145909 (b) tag, and if we considerrepparttar 145910 closing tags as well we see that usingrepparttar 145911 (strong)(/strong) tag pair uses 10 more characters thanrepparttar 145912 cleaner (b)(/b) tag pair.

This is our First Principle of clean HTML code: Userepparttar 145913 simplest coding method available.

HTML hasrepparttar 145914 ability of nesting code within other code. For instance we could have a line with three words whererepparttar 145915 middle word was in bold. This could be accomplished by changingrepparttar 145916 formatting completely each timerepparttar 145917 visible formatting changes. Consider this code:

(font face=”times”)This(/font) (font face=”times”)(strong)BOLD(/strong)(/font) (font face=”times”)Word(/font) This takes up 90 characters.

This is very poorly written html and is what you occasionally will get when using a WYSIWYG editor. Sincerepparttar 145918 (font) tags are repeatingrepparttar 145919 same information we can simply nestrepparttar 145920 (strong) tags insiderepparttar 145921 (font) tags, and better yet userepparttar 145922 (b) tag instead ofrepparttar 145923 (strong) tag. This would give us this code (font face=”times)This (b)BOLD(/b) Word(/font), taking up only 46 characters.

VoIP Phone Home?

Written by Jason Canon

VoIP Phone Home?

The movie Extra Terrestrial (ET) coinedrepparttar phrase “phone home” and each year American’s look for more cost effective ways to do just that. The past 10 years have seenrepparttar 145609 development and growing popularity of Voice over Internet Protocol (VoIP) technologies to achieve cost savings overrepparttar 145610 traditional circuit-switched telephone networks. The two dominate technologies used for VoIP are: (1)repparttar 145611 Session Initiation Protocol (SIP) and (2) Peer-2-Peer (P2P). For business and educational institutions SIP VoIP solutions have produced substantial savings. For home voice users, however, SIP VoIP is still value challenged.

A typical circuit-switched landline phone costs about $19.95 per month (plus tax). The good old American landline phone should be graphically depicted besiderepparttar 145612 word “reliable” inrepparttar 145613 dictionary. Not only does it keep working, even when all electrical power fails, but it can even provide you with a light to dial with. At $15 dollars per month SIP VoIP is still value challenged due torepparttar 145614 lack of full support for E9-1-1 emergency services and of courserepparttar 145615 reliability issues inherent with using a real time application over a “best effort” network like today's Internet. Although few VoIP articles still reference Internet Request For Comments (RFC) 3714 “IAB Concerns Regarding Congestion Control,”repparttar 145616 technical challenges associated with VoIP are widely known. Further, even withrepparttar 145617 recent dubious edict byrepparttar 145618 Federal Communications Commission (FCC) that VoIP service providers will provision support for E9-1-1 within 90 days, this still leavesrepparttar 145619 reliability issues unresolved. The use of adaptive rate CODEC’s to prevent congestion collapse is a swell idea if it applies to my neighbor’s service but not my own. Using adaptive rate CODEC’s to elicit voluntary user preemption has no appeal inrepparttar 145620 modern world. Technology is supposed to be getting better and it is clearly not better that users receive disconnects or degraded service quality in order to constrain network bandwidth consumption.

Quality of Service (QoS) has beenrepparttar 145621 four letter word ofrepparttar 145622 Internet for a very long time. Yet, we know that real time applications such as video and voice are a mismatch for “best effort” service models. Cost savings are important, but not if they require users to accept backward technology leaps. After 9/11repparttar 145623 United States should have begun standardization efforts to insure that VoIP QoS levels would be equivalent to circuit-switched networks, especially where emergency E9-1-1 calls are concerned. The recent FCC order only requires that E9-1-1 call center traffic be properly routed. It does nothing to insure QoS ofrepparttar 145624 connection oncerepparttar 145625 call is completed.

Cont'd on page 2 ==> © 2005
Terms of Use