# Overall Scoring

## Overview

Once metric scores are calculated, Provider Intelligence calculates an overall score for providers in each location to identify the top choices.

## Overall Score Calculation

Provider rankings are based on weighted aggregate overall scores that combine your [prioritized metrics](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/build-a-query/prioritize-metrics) with their scores from your preferred [results calculation](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/build-a-query/specify-results-calculation) method (**Performance** or **Performance & Stability**):

1. **Apply user metric priorities**: You prioritize metrics (for example, latency → loss → jitter → TTFB (if you selected applications as destinations)) within the [query builder](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/build-a-query). These priorities translate to weights:

   * **4 Metrics**, including TTFB (when applications are selected):

   | Priority Position | Weight |
   | ----------------- | ------ |
   | 1st (highest)     | 40%    |
   | 2nd               | 30%    |
   | 3rd               | 20%    |
   | 4th               | 10%    |

   * **3 Metrics**, excluding TTFB (when no applications are selected):

   | Priority Position | Weight |
   | ----------------- | ------ |
   | 1st (highest)     | 50%    |
   | 2nd               | 33.3%  |
   | 3rd               | 16.7%  |
2. **Calculate per-metric scores:** For each metric, use either:

   * **Performance score** (if you selected **Performance** mode), or
   * **Combined score** (if you selected **Performance & Stability** mode)

   See [Specify Results Calculation](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/build-a-query/specify-results-calculation) to understand when and why to choose **Performance** or **Performance & Stability**.
3. **Calculate overall score:** Multiply each metric's score by its weight and sum them:

   ```
   Overall Score = (Weight₁ × Score₁) + (Weight₂ × Score₂) + (Weight3 × Score3) + (if including TTFB)(Weight4 × Score4)
   ```
4. **Sort providers:** Order providers by overall score from highest to lowest.

### Key Considerations

* **For each user location**, all providers are scored using the same formula, then placed in descending order. Providers that feature in multiple locations might perform the same (for example, 15 ms latency) but score differently in each location because scores are relative. See [Understanding Scores](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/scoring-methodologies/understanding-scores) for more information.
* Changing any one field within the query builder can affect provider scoring. See [Build a Query](https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/build-a-query) for more information.

## Example Calculation

**Your Prioritization**: Latency > Loss > Jitter > TTFB

**Provider Scores (using Performance mode)**:

* Latency: 90
* Loss: 95
* Jitter: 85
* TTFB: 88

**Calculation**:

```
Overall Score = (0.40 × 90) + (0.30 × 95) + (0.20 × 85) + (0.10 × 88)
              = 36 + 28.5 + 17.0 + 8.8
              = 90.3
```

**Result**: Provider's overall score is 90.3.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thousandeyes.com/product-documentation/internet-insights/provider-intelligence/scoring-methodologies/overall-scoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.