Technical team manager

Optimise the performance of key User Journeys at every step

• Ensure key User Journeys are delivering optimum performance end-to-end - identify slow downs, errors and inconsistent performance
• Ensure Infrastructure will comfortably handle expected loads at busy times
• Quickly pinpoint performance issues and bottlenecks with drill-down detail, and RePlay past errors and see raw HTML/javascript etc
• combine infratstructure metrics with those from the user’s perspective
• Obtain hard facts to show where technical improvements are really necessary – cover your back
• Get credit for well performing User Journeys and focus team resources on poorly performing steps, or page components. Each User Journey will perform differently because of different code, technology blocks and database calls so test journeys which cover all technology blocks
• Identify the route causes of slow downs, errors and inconsistent performance. You’ll often find that the existing slow pages you know about, are not always the root cause when a particular journey suffers it’s slowest performance
• Set and measure SLAs on the basis of User Journey testing results
• Share results in a common language with Marketing and business teams

Resources for technical managers

Managing bandwidth for increased traffic ››

First steps on your user journeys ››

Is the website down today? ››

SEO - how to use spiders to maximise page indexing ››

Understanding web performance graphs at a glance ››

IE7 developments - 7th heaven or is Microsoft still at sixes and sevens? ››

Firefox 1.5 - new features ››

Uncivil websites - browser compatibility problems ››

Moving images on to a separate server ››

Leading by example - How do leading websites balance server load with interesting content? ››

Top 10 tips for effective caching ››

How to use headers to maximise caching ››

A 10 point plan for load testing - what to plan for and what to expect ››

Six key steps to load testing ››

Is automated validation testing helpful or burdensome? ››

Unearthing hidden functionality flaws ››