Live Apdex Report

    Apdex Report [?] is powered by
    WatchMouse website monitoring.

    LinkedIn

    See our LinkedIn profile, click on this button:

    APDEX

    Apdex Alliance Welcomes WatchMouse

    Today, the Apdex Alliance welcomes its latest sponsor. WatchMouse tests websites, services and applications utilizing an infrastructure that includes over 58 worldwide remote monitoring stations and a global network of checkpoints in 26 countries. The worldwide coverage is impressive as shown in the map below.

    WatchMouse has implemented Apdex reporting in its tools. You can easily add Apdex reports to the many monitoring systems that WatchMouse supplies. But this is just one from a wide range of reporting tools available. They support many user platforms along with detailed test settings. I have been using the tool for a while and will be writing about how to use Apdex with WatchMouse in the future.

    WatchMouse has also implemented a great Live Apdex Report widget that is running on the left of this website. We have been working with WatchMouse to make is simple and informative. I hope you agree. You can add the Apdex widget to track any service and make it part of your website (public or private). I am still experimenting with the widget. At the moment it is reporting on my two favorite websites (this one and NetForecast). But I think we should widen the scope of sites to track. Got any suggestions?

    I recommend you try out their service which is available with a free 30-day trail.

    Gomez Launches Apdex-Based “User Experience Index”

    It’s the busiest online shopping week of the year, and to mark it Gomez has launched a novel way to show how well retail websites are performing from a user’s viewpoint. This is a noteworthy first. Called the Compuware Gomez Retail User Experience Index (UX Index for short), this new report is much easier to interpret than traditional reports that simply rank websites by response time or other raw metrics.

    Rather than report raw numbers for response time, availability and consistency, the UX Index uses Apdex scoring methodology to give websites one user experience-based score, which Gomez rolls up into a macro view of how well websites are performing for the top 500 online retailers, the top 15 retailer websites, and the top 15 mobile retailer websites. They also show how well the sites are performing relative to a baseline. Because Apdex factors in response time, consistency as well as availability, it enables Gomez to assign a single score to a measurement sample. This aspect of Apdex also makes it easy to aggregate the results of many websites into a single group score–allowing Gomez to compare multiple benchmarks over time.

    Gomez assigns every unique test an outcome of Satisfied, Tolerating or Frustrated. These categories are defined as:

    • Satisfied: Page response time of 2 seconds or less;
    • Tolerating: Page response time of between 2 and 8 seconds;
    • Frustrated: Page response time of greater than 8 seconds or the test failed.

    An Apdex score is determined by comparing the ratio of all Satisfied tests and half the Tolerating tests to the total of all tests. A score of 100 means that all tests (or users) in the sample fell into the Satisfied bucket. A score of zero indicates that all tests (or users) fell into the Frustrated bucket. Generally, a score of lower than 70 is considered poor, and 70 or greater is considered fair. A score between 85 and above 94 is considered good. A score above 94 is considered excellent.

    If there is one day of the year when retail websites are stressed to the maximum, Cyber Monday is it, so check out the UX Index here and see how things look. Later this week we plan to analyze how well the websites tested fared on Black Friday and Cyber Monday.

    Apdex-G and Apdex-R Composite Sections 1-5

    I’m writing a series of posts about Generalizing Apdex. This is #25. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec documents, Apdex-G and Apdex-R, are enclosed in square brackets and prefixed by the document type, like this: [G 1] and [R 1].

    Drafts of the Apdex-G spec were posted as Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, Section [5] Reporting, and Section [6] References.

    Drafts of the Apdex-R spec were posted as Section [1] Introduction and [2] Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, and Section [5] Reporting. Those posts show how the proposed Apdex-R spec is derived from the present Apdex spec.

    This post consolidates the Apdex-G and Apdex-R proposals side-by-side, without annotations, allowing sections 1-5 of both documents to be viewed together.

    Continue reading Apdex-G and Apdex-R Composite Sections 1-5

    Apdex-R Section [5] Reporting

    I’m writing a series of posts about Generalizing Apdex. This is #24. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec documents, Apdex-G and Apdex-R, are enclosed in square brackets and prefixed by the document type, like this: [G 1] and [R 1].

    Drafts of the Apdex-G spec were posted as Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, Section [5] Reporting, and Section [6] References.

    The first draft of Apdex-R began with Sections 1 and 2, Section 3, and Section 4. This post covers Section 5.

    Continue reading Apdex-R Section [5] Reporting

    Apdex-R Section [4] Calculating the Index

    I’m writing a series of posts about Generalizing Apdex. This is #23. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec documents, Apdex-G and Apdex-R, are enclosed in square brackets and prefixed by the document type, like this: [G 1] and [R 1].

    Drafts of the Apdex-G spec were posted as Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, Section [5] Reporting, and Section [6] References.

    The first draft of Apdex-R began with Sections 1 and 2, then Section 3. This post covers Section 4.

    Continue reading Apdex-R Section [4] Calculating the Index

    Apdex-R Section [3] Calculation Inputs

    I’m writing a series of posts about Generalizing Apdex. This is #22. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec documents, Apdex-G and Apdex-R, are enclosed in square brackets and prefixed by the document type, like this: [G 1] and [R 1].

    Drafts of the Apdex-G spec were posted as Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, Section [5] Reporting, and Section [6] References.

    The first draft of Apdex-R began with Sections 1 and 2. This post covers Section 3.

    Continue reading Apdex-R Section [3] Calculation Inputs

    Apdex-R Section [1] Introduction and [2] Overview

    I’m writing a series of posts about Generalizing Apdex. This is #21. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec documents, Apdex-G and Apdex-R, are enclosed in square brackets and prefixed by the document type, like this: [G 1] and [R 1].

    Drafts of the Apdex-G spec were posted as Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, Section [5] Reporting, and Section [6] References.

    This post presents the first draft of Apdex-R, Sections 1 and 2. Apdex-R specifies the Apdex rules for reporting response-time measurements, therefore my first draft draws heavily on the present Apdex spec. My goal is to reformat the present spec’s rules within the context established by Apdex-G. To allow both documents to be viewed together, I show Apdex-G (draft #2, plus a few subsequent amendments) on the left, and Apdex-R (draft #1) on the right.

    Differences between Apdex-R and the corresponding sections of the present spec are highlighted, as follows:

    • text deleted from the present spec
    • new text added to Apdex-R (plus a few additions to Apdex-G draft #2)
    • new text created for Apdex-G, now being repeated in Apdex-R for readability
    • notes, questions, issues to be resolved

    While major deletions, additions, and changes to the present spec are marked, many minor wording changes to the present spec’s text, to improve continuity and clarity of meaning, are not marked. I believe those changes do not substantially alter the meaning and intent of the present spec.

    Continue reading Apdex-R Section [1] Introduction and [2] Overview

    Apdex-G Section [6] References

    I’m writing a series of posts about Generalizing Apdex. This is #20. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec, Apdex-G, are enclosed in square brackets, like this: [1].

    I have been working systematically through the process of generalizing the current Apdex spec. Along the way, I have been skipping over parts of the current spec to work on the paragraphs that presented challenges. I am now going back to fill in those less contentious paragraphs, posting updated drafts of each section of the Apdex-G spec. The first five are Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, and Section [5] Reporting; today I continue with Section [6] References.

    Continue reading Apdex-G Section [6] References

    Apdex-G Section [5] Reporting

    I’m writing a series of posts about Generalizing Apdex. This is #19. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec, Apdex-G, are enclosed in square brackets, like this: [1].

    I have been working systematically through the process of generalizing the current Apdex spec. Along the way, I have been skipping over parts of the current spec to work on the paragraphs that presented challenges. I am now going back to fill in those less contentious paragraphs, posting updated drafts of each section of the Apdex-G spec. The first four are Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, and Section [4] Calculating the Index; today I continue with Section [5] Reporting.

    Continue reading Apdex-G Section [5] Reporting

    Apdex-G Section [4] Calculating the Index

    I’m writing a series of posts about Generalizing Apdex. This is #18. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec, Apdex-G, are enclosed in square brackets, like this: [1].

    I have been working systematically through the process of generalizing the current Apdex spec. Along the way, I have been skipping over parts of the current spec to work on the paragraphs that presented challenges. I am now going back to fill in those less contentious paragraphs, posting updated drafts of each section of the Apdex-G spec. The first three are Section [1] Introduction, Section [2] Index Overview, and Section [3] Calculation Inputs; today I continue with Section [4] Calculating the Index.

    Continue reading Apdex-G Section [4] Calculating the Index