Your e-Business Quality Partner eValid™ -- The Web Quality Suite
Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading.
© Copyright 2000-2011 by Software Research, Inc.

eValid -- Power User Tips & Tricks
Prior   |   Catalog   |   eValid Home   |   Search   |   Next

Become an eValid Power User!
eValid Power User's Tips and Tricks can help you use eValid to get better results, quicker, and easier. Each Tips and Tricks item addresss one or two issues that will help you to increase your effectiveness with eValid.

> How to Tune Up A Single Web Page

  WebSite page performance depends on the detailed composition of the
  page.  Some pages are very simple, with few components and constituent
  images.  Some are quite complex.

  "Tuning a WebSite Page" means studying how long each component takes
  to download.  You can do this very easiy with eValid because you can
  see how long each piece of the page takes to download.

  (1) Record Your Script:  Start by recording a script at the URL you
  are trying to optimize.

  Make sure you have:
    eValid > Settings > Preferences: Real-Time Recording ON

  After the page is fully loaded, press RETURN every 5 seconds or so,
  until you have a total of about 10 repeats of the download.  This time
  delay is long enough so that the Web will "release the connection"
  between downloads -- you get a more-accurate timing this way.

  (2) Set eValid to Run with No Cache, with Detailed Timings.  If you
  load from the local cache your timing will be quick, but won't
  indicate bottlenecks.  Use these two settings:
    eValid > Settings > Cache Manager: Never Use Cache ON and:
    eValid > Settings > Preferences: Log Messages DETAILED

  (3) Play the Script and Study the Chart.  Play back the script and
  watch it continuously re-download the page.  When the playback is done
  use:
    eValid > View Log Graphs: Performance

  to produce the timing chart.  Use your mouse to study how long each
  element took to download.  What you're looking for is the one or two
  or three slowest loading components.  They are the ones that slow down
  the page and might need to be fixed for better performance.

  See this URL for an example:
    Sample Timing/Tuning Chart