Designing Effective ESL/EFL Web Pages
Some Guidelines to Consider When Putting Together Pages
This page is designed for people who already have a web page or are in the process of developing a web site.
If you have never made a web page before, then perhaps you'd like to read How to Make a Successful ESL/EFL Teacher's Web Page
first.
You may not agree with all of these guidelines, but you should at least take
them into consideration when writing web pages. If you would like to suggest other considerations to be included on this page, then please send them in.
Make your page as fast as possible.
- You should always weigh "great-looking" vs. "fast-loading." Having an "acceptably good-looking" page is better than having a "great-looking" page that causes many visitors to hit the stop button before viewing the page.
Slow-loading pages also cause potential repeat visitors to stay away because they take too long to download.
- It's not only the download time you need to consider, but how fast your page appears on the visitor's screen.
- Traditional, straight-forward formatting allows visitors to read the top of the page as the rest of the page is downloading.
- Full-page table formatting and frames cause visitors to wait.
- Even with a fast server, factors such as distance and heavy Internet traffic can make your page load into a visitor's computer very slowly.
Consider your audience.
- Most of the advice here assumes that you are aiming your pages at a world-wide audience. Since many EFL students live in countries with slow and/or expensive Internet connections, speed is an important consideration.
- However, if you are writing your pages only for your own students and all of them will be accessing the pages with the same browser and using the same model of computer, many of these considerations are unnecessary.
- On the other hand, with just a little extra effort on your part, you may find that your pages have a world-wide appeal, even though your primary aim was only to write for your own students accessing the pages from your school's computer lab.
Be careful with font colors & backgrounds.
- Don't use backgrounds which make reading the page difficult.
- If you don't like the colors on your page, check out Good Color Combinations.
- Don't choose font colors that can't be read using the default background.
- Using the standard blue for clickable links is best.
Be careful with using Java, animated GIFs, image maps, etc. Avoid them if possible.
- Don't design a page that requires java or javascript.
- Disable java and javascript and test your page before uploading.
- This doesn't mean you can't use it, just don't require it.
- One exception to this rule would be pages offering interactive quizzes which cannot be done any other way.
- Many visitors may find animated GIFs irritating.
This is especially true if you use more than one.
- If you use an image map, don't forget to also include text links for those not downloading images.
Be careful with table formatting. Avoid it if possible.
- Tables look nice, but they slow your page down with added code.
If you can get what you want without a table, it's better.
- If you use tables, be careful not to use a long table. Remember that the whole table must load in before it displays on the screen.
Break long tables up into multiple small tables.
- A polite, maximum width would be about 460 pixels. Many people, even with large screens, prefer to keep their browser's window at "word processor" width.
- Try using WIDTH="100%" instead of hard-coding the number of pixels. This allows your table to be read in any size window.
- Don't make the common mistake of using tables to form multiple long columns. This could make your page one of those irritating pages that cause you to scroll down to read one column, then cause you to scroll back up and down to read the next column.
Don't use full-page, multi-column table formatting.
- Though some page writers do this to put navigation buttons on the side of the page, it is not recommended.
- Since many web surfers have learned how to avoid (the less-than-popular) frames,
this is a way web page writers can force this type of interface on their visitors.
- It would be better to put a line of text-only links just under the title of the page or at the bottom of the page.
- This formatting gives a "cramped-looking" page to visitors using smaller screens and to visitors who prefer not to use the full screen to view web pages.
- This formatting adds a lot of HTML code to the page, resulting in a larger filesize, thus a slower-to-download page.
- Your page will seem to stall, since the whole table must load in before it displays on the screen.
- This means that some visitors will get tired of waiting and click the stop button before viewing any of your page.
- However, if you do not do this type of formatting, your visitors can be reading the top of your page as the rest of the page downloads which gives the feeling of a fast-loading page since visitors do not need to wait.
- Complex table formatting takes a long time to layout onto the screen after downloading, especially for less powerful computers.
Be careful with frames.
- Not only are they slow, but often they squeeze the page into a much smaller
space making the page less effective. Overuse of frames can also cause 'out of
memory' errors on some computers.
- If you use a frame, it is more polite to make it the option and not the default.
(See an example: http://www.aitech.ac.jp/~iteslj/Articles/Kelly-MakePage/) This way those with slow connections (or small screens) can enjoy your page and those with fast connections can easily choose to use the frame.
- Frames make it difficult for visitors to bookmark a sub-page they want to return to, thus requiring them to enter through your "front door" on a return visit. This is inconsiderate.
- If you decide that you need to use a frame, don't forget to use TARGET="_top" for any external link you have.
If you have many external links then a <BASE TARGET="_top"> within the <HEAD></HEAD> of your page will help keep the filesize smaller since you won't need to put the TARGET="_top" in every link."
Include your e-mail address at the bottom of the page.
- Use the mailto: code. It's easy and fast.
- It's best to show the email address since some browsers don't support mailto:.
- If you only have an email image, then those who don't download images will not find your email address.
- Warning You may want to include your email address as I have done at the bottom of this page. This helps cut down on the amount of unsolicited "junk" mail you will receive
since "e-mail searching robots" cannot
pick up your email and add it to junk mail list.
- Requiring users to use a CGI form or returning to your home page to write a quick note seems inconsiderate.
Don't use a lot of images or large images.
- If you do use images, be sure to include the ALT, HEIGHT and WIDTH code.
- Quite a few Internet users surf the Net without loading images. Many that surf with "auto-load images on", still often hit the Stop
button before all images are loaded.
- You should definitely
view your page without loading images to see how it looks to these people.
- If you use
images, you should get your image's file size as small as possible by cutting
colors and cutting the image size
Sample Small GIFs
Only 1,136 bytes, 2 colors, 383 x 34 pixels
Only 2,585 bytes, 32 colors, 76 x 76 pixels
Only 2,884 bytes, 8 colors (different shades of red), 440 x 40 pixels
Don't use images of text for sub-titles on your page.
- This, of course, adds to the download time of your page.
- A more important reason is that if you use text instead of images, then your visitors can use the "find" function of their browsers to jump to sub-sections.
- Also, remember there are still people who view the web without loading images.
Be careful with using CGI & SSI. Avoid it if possible.
- Be careful not to slow down your page by doing "cute" things with these.
- SSI counters can really slow down your page.
- SSI randomly-chosen images or quotations can really slow down your page.
- Forcing people to use CGI to navigate your site seems inconsiderate.
- Forcing people to use CGI to email you a message seems inconsiderate.
Various Views on the Use of Advertising
- Don't Include Any Advertising.
- Some (maybe most) teachers think that educational sites should be free of advertising.
- However, even those people would probably find the following acceptable.
- Don't Include "Non-Paid-For" Advertising
- (If you didn't agree with the previous suggestion, then read on......)
- These are all forms of "non-paid-for" advertising.
- "This page best viewed using ..."
- "This site was chosen as site of the day by ..."
- "This site was voted to be in the top 10% by ..."
- "Member of ...."
- Many think that "The Internet Link Exchange" and other banner exchanges are as bad as regular advertising.
I doubt if very many people actually visit your site through this method. How many of those ads have you actually clicked?
If you do decide to use their service or a similar service, put the ad at the bottom of your page.
(Why should the ad be more important than what you are offering?)
- These only slow down and clutter up your page (especially if you include an image,
too) and don't really serve any purpose. If your site has a sponsor, then
advertising is serving a purpose.
- If You Need to Include Advertising, then...
- Don't put the ad at the very top of your page.
- It's your page. Your title should be at the top.
- I would personally recommend putting the ad at the bottom of the page.
- Your advertisers may not agree, though. However, if they are only paying per click-through, then it should be your choice.
- Common sense would seem to dictate that a visitor is more likely to click to another site after he/she has read the page he/she came to read.
- By putting the ad near the top of the page, you give your visitors a chance to click to another site. This means that there is a chance they will never make it back to your site.
- By putting the ad at the bottom of the page, you will appear less like a "money-grabber" out to make money with your web site, and more like a teacher who needs advertising to help make ends meet.
- Only accept non-animated GIF ads.
- Animations will often distract from what you are trying to teach.
- Never have more than one ad per page.
Choose a good page name.
- Don't choose a generic name such as "My ESL Pages"
- Avoid names or parts of names which have already been used. (eg. Cafe, Farm, Planet, Town, Club)
- Put the page name in the <title></title>, so that people have a descriptive bookmark to your page.
Don't ever change URLs within your directory.
- Avoid "File Not Found" error messages. Don't rename files within your own directory.
- Remember that visitors bookmark their favorite sub-pages
- Pages of "links" may also have added links to your sub-pages.
- Search Engines are likely to also have your sub-pages listed.
- If you have to change servers, then changing URLs is unavoidable.
Don't force experimentation on your visitors.
- Experimenting with javascript is fun, but forcing your visitors to use a javascript page when it is often more efficient using
regular HTML is inconsiderate.
- Forcing visitors to use an image map is inconsiderate since it requires those with slow connections to download an image and makes your page unusable by those using a browser that doesn't support images or image maps.
- Pull-down navigation menus driven by JavaScript will leave your non-JavaScript visitors no way to get to your other pages.
Make your page user-friendly for the frequent user.
If you have created the kind of page which is likely to be revisited, then ...
- Don't put in long introductions and include a lot of information that only
requires one-time reading.
- If you feel something like this is necessary, then put it on another page and offer a "for first-time visitors" link to that page.
- Slow-loading pages may keep visitors from returning.
- Don't use lots of images or large images.
- Don't embed files.
- Don't use frames.
- Don't use full-page column formatting.
TESL Specific Things to Consider
- About "links" pages.
- Consider just linking to one of the major sets of links instead of making a "links" page yourself.
- Spend time developing "content" rather than trying to maintain a set of links.
- Links go "not found" so quickly, that unless you are always monitoring your page, your page soon becomes dated.
- It may still be a good idea to maintain a short list of links for your students.
- Only include links that you really expect your students to visit.
- Then include a link to one of the major sets of links.
(For example: TESL/TEFL/TESOL/ESL/EFL/ESOL Links)
- Instead of trying to produce a "General ESL Site", focus on one area.
- A few examples of successful focused sites.
- Randall's ESL Cyber Listening Lab
- The primary focus is on listening exercises and quizzes.
- Self-Study Quizzes for ESL Students
- The primary focus is on quizzes.
- Dave's ESL Cafe
- The primary focus seems to be "communication" and sharing ideas using the message boards.
- It's better to have a "best" focused site, then an "average" general site.
(A Jack of all trades, master of none.)
- Do something that hasn't yet been done.
- There is little need to duplicate what someone else has done.
- The exception, of course, is that you think you can do it better.
- Visit a lot of the ESL/EFL sites to see what they don't have to offer.
- For example: (as of Sept. 14, 1998) There seem to be no sites focused on these.
- Minimal Pairs, Pronunciation
- English for ...
- Doctors
- Auto Mechanics
- Musicians
- An Archive of Reading Materials for ESL Students.
- etc.
- For more ideas, see ESL/EFL Web Sites We Would Like to See
A page where ESL Web users can let Web developers know what they would like to see.
Don't forget to do these things before you upload your page(s).
- Check your links.
- Make sure you don't have any links which result in "Not Found" error messages.
- If you have external links (links to pages on other sites), you'll have to keep checking the links from time to time.
- Check your spelling.
Obvious, but many pages have spelling errors.
From Other Web Pages That I Have Written
How Does Your Page Rate?
Optimize Your Web Page for Speed
1. Eliminate everything that doesn't show on the surface of the page.
This is the easiest thing to do to get your page to download more quickly.
- Eliminate multiple-spaces, tabs, returns, line-feeds, etc.
Remember that in HTML any amount of "white space" is reduced to one-space on the surface of the page.
Eliminating this "white space" in the HTML will in no way affect the way your page looks to the visitor, but will result in a smaller filesize.
How to Do It
With your text editor (or word processor) use the "FIND & REPLACE ALL" function.
- If there is no JavaScript or <pre> code on the page.
- Find RETURN (\r or \n in some text editors) and replace them with a SPACE.
- Find TAB (\t in some text editors) and replace them with a SPACE.
- Find 2 SPACES and replace them with 1 SPACE.
You may need to do this more than once.
- If there is JavaScript and no <pre> code on the page.
- Find 2 RETURNS (\r or \n in some text editors) and replace them with 1 RETURN.
You may need to do this more than once.
- Find a RETURN + SPACE and replace them with 1 RETURN.
- Find a SPACE + RETURN and replace them with 1 RETURN.
- Find TAB (\t in some text editors) and replace them with a SPACE.
- Find 2 SPACES and replace them with 1 SPACE.
You may need to do this more than once.
2. Eliminate junk put in by HTML editors
If you use an HTML editor (Netscape Communicator, PageMaker, etc.), you should learn enough about HTML to remove the excessive code produced by HTML editors.
This excessive code is put in to make programming the HTML editor easier. I have yet to see one where the programmer has taken the time to fine-tune the HTML.
Here are some things which are often seen in code produced by HTML editors which can be eliminated.
- </center> followed by <center>
There is no reason to stop centering, just to begin it again.
- </b> followed by <b>
There is no reason to stop the BOLD, just to begin it again.
Italics and other similar code can be removed in much the same way.
- <p><font size=-1>here is some text</font></p>
<p><font size=-1>here is some text</font></p>
<p><font size=-1>here is some text</font></p>
You can eliminate the 2nd & 3rd <p><font size=-1> and the 1st and 2nd </font>.
This is true for any repetitive FONT code -- color face, etc.
Eliminating this "junk" in the HTML will in no way affect the way your page looks to the visitor, but will result in a smaller filesize.
3. Use minimal HTML code
- Avoid overusing text font changes and color changes.
- Set the "text font color" in the <BODY> code instead of as a <FONT> code command.
- Use <BASE FONT= > instead of setting the font for each line.
4. Use short HTML code
If any of the following only occur once on your page, it won't make much difference, but if you use it a few hundred times, it could make a difference.
Here are some things which can be substituted in order to get a faster-loading small filesize.
- <B> for <STRONG>
- &nsp;
Use a regular space.
Doing this "conversion" in the HTML may slightly affect the way your page looks to some visitors, but not for many of your visitors.
5. Don't use any images or use only a few small ones.
For the fastest loading pages, don't use images.
It's probably not too bad to use one image for the title of the page, but with every image you add, your page will get slower.
If you do use images, cut the filesize to the smallest possible size. For GIF files, cutting the number of colors will cut the size of the file.
6. Especially don't use images for these.
- Dividing Lines
- There is perfectly good HTML code to produce lines. It displays on the page quickly and takes very little code.
For example:
- No image: <HR> is 4 characters.
- Image: <IMG SCR="gif/line.gif" HEIGHT="4" WIDTH="440"> is 45 characters (remember to count the spaces), plus you need to download the GIF image itself.
More realistically, most people probably would also add <CENTER></CENTER> on either side of the code adding another 16 characters.
- Dots
- Using the Unordered list code <UL><LI></UL> is fairly concise and attractive.
See the difference:
- No image: <LI>
- Image: <BR><IMG SCR="gif/dot.gif" HEIGHT="12" WIDTH="12">
- Sub-titles and other text on the page
- Using an image to display text is slower than just displaying the text.
An added negative point is that your visitor cannot use the browser's find function to find the sub-titles.
Another added negative point is that it probably won't look good when printed on paper. Even with a 1200 dpi printer, web images print at 72 dpi.
And yet another negative point is that visitors who don't load images will be totally lost unless you are sure that you add in the ALT code, which adds even more to your filesize.
7. Don't use tables
- Table formatting adds a lot of HTML code to your page, making the filesize larger.
- If you can get by without the table formatting, your page will be faster.
- The table won't be seen on the visitor's screen until the whole table is loaded into the visitor's computer.
- This can make your page appear to download more slowly than it actually does, since the visitor won't see
anything, until the final </TABLE> is loaded.
8. Don't use multiple-column page layout
The primary problem with this type of layout is the same as the second problem mentioned immediately above.
9. Don't use JavaScript
- Putting in a "cosmetic" JavaScript into your page doesn't accomplish much other than slowing down your page.
- Some people clutter up their pages with things that don't really add to the content of their pages; clocks, scrolling messages, etc.
- Using JavaScript to get "cool-looking" navigation is slower than simple links.
- Not only will your filesize be larger, thus slower to download, some people will not be able to use your navigation since they may have a JavaScript incompatible browser or may have intentionally disabled JavaScript.
- There are good uses of JavaScript.
- If you are doing a game or a computer-scored quiz, then the JavaScript on the page has a useful purpose.
10. Don't use CGI or SSI
- Using CGI or SSI for things that can be done with simple HTML code, just wastes the visitor's time.
- Things like using pull-down menus and a CGI to get to the next page should be avoided, since simple HTML links would be more efficient.
- Obviously, there are some uses of CGI which are useful.
- Some things can only be done using CGI.
Commonly Seen Things Which Are Best Avoided
- Frames
- Why People Do It
- It seems to be easier to navigate the site.
- Please note that there are some acceptable reasons for using frames. However, if they can be avoided, it is usually better.
- Why You Shouldn't Do It
- Visitors cannot easily bookmark the page they want to return to and must enter your site through the "front page", then navigate through your site until they find the page they want to return to.
- It requires more pages to be downloaded (at least 3 pages), thus increasing the download time.
- There were other reasons listed previously on this page. (I'll merge these two sections together.)
- 2-Column Page Layout
- Why People Do It
- It utilizes the whole "window" for those who have their browser's window set to a wide width.
- For some, it's just a carry over from how things were done on paper.
- It avoids frames, since you can put a left-hand (or right-hand) navigation "panel" on the same web page.
- You should note, that this usually requires the visitor to download more data than if he had downloaded a frame,
since the navigation part of the page is duplicated on each page.
- Why You Shouldn't Do It
- Your whole page (actually the whole table) must load before any of it begins to show on the visitor's screen.
- It requires visitors with a smaller screen or visitors who have their window widths narrower than yours, to scroll horizontally to see your page.
- It often requires the visitor to scroll down, then up, then down again.
- It requires more HTML code, increasing the filesize, thus increasing the download time.
Other Things to Avoid
- Having the same link, but with different text showing.
Example: Please feel free to send me
a message. My email address is fake@email.address.com.
- This often confuses the visitor.
- It increases the filesize.
- "This page best viewed at a 640 X 80."
- First, don't make this kind of page.
- Second, even if you make this kind of page, don't admit to your visitors that you "are being inconsiderate" to some of your visitors.
No junk mail, please.
To send corrections or comments, replace the $ with @.
ckelly$ge.aitech.ac.jp
I'm sorry about this, but it keeps the automatically generated junk mail to a minimum.
Copyright (C) 1995-1999 by Charles I. Kelly