TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: time spent on web pages From:Arlen -dot- P -dot- Walker -at- jci -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 29 Jan 2001 09:04:11 -0600
Acquiring this information is quite problematic:
scenario 1: Person loads a page from the website, and spends the next 30
seconds waiting for the page to load, decides after waiting for it the page
is useless, and clicks another link.
scenario 2: Person loads the web page quickly, and spends the next thirty
seconds studying the information presented, before moving on.
Both scenarios look the same to the web server. (Note: on scenario 1, the
load delay can be caused by many things unrelated to the web design,
including slow modem, or busy firewall,proxy server.) Only 2 is relevant to
the question.
Scenario 1: Person loads page, studies it for half an hour, quits the
browser because the task is now satisfactorily completed.
Scenario 2: Person loads page, takes one quick glance and deems the page
completely unsuitable, so hits the back button on his browser to go look at
the next link in the Google list.
Again, both scenarios look the same to your webserver. Only 1 is relevant
to the question.
Scenario 1: Person loads page, studies it carefully because the page is
chock full of useful information, then clicks a followup link.
Scenario 2: Person loads page, studies it carefully because the information
design on the page is so hideous it takes great effort to extract useful
information from it, then clicks a followup link.
Scenario 3: Person loads page, gets interrupted by a telephone or a
visitor, comes back and glances at the page, then clicks followup link.
All three look the same to your webserver. Secnario 1 is relevant to the
question, scenario 2 is a fault, yet will look like a Good Thing under this
study, 3 is completely irrelevant.
Have fun,
Arlen
Chief Managing Director In Charge, Department of Redundancy Department
DNRC 224
Arlen -dot- P -dot- Walker -at- JCI -dot- Com
----------------------------------------------
In God we trust; all others must provide data.
----------------------------------------------
Opinions expressed are mine and mine alone.
If JCI had an opinion on this, they'd hire someone else to deliver it.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
