> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/voicetrends/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/voicetrends/performance/performance-graphs.md).

# Performance Graphs

The y-axis on each graph depicts the statistical value indicated by the graph name. The x-axis displays the specified period (day, week, month).

To enlarge each graph, click the thumbnail of the graph from within the page, or select it from the sub-menu under the Performance section.

To change the period interval on this graph, select one of the Day/Week/Month buttons located in the top right of this menu. Selecting one of these changes the period of the x-axis on the graph.

To view the data for a specific phone number, select the desired phone number from the drop-down menu in the top left. “*All Phone Numbers*” is the default setting for this menu until changed by the user.

## **JS Errors**

This total is calculated based on the number of JavaScript errors encountered. This is synonymous with an error.semantic.ecmascript event.

![](/files/-M5hKPQDdQ8s6i-Hyv49)

## **JS Errors per Call**

This graph depicts the total number of JavaScript (ecmascript) errors divided by the total calls for a given period. The metric is useful in contrast with the JS Errors graph because the JS Errors per call data should scale linearly with the number of calls, as opposed to the fixed JS Errors total.

![](/files/-M5hKPQEbHyC7LKGAysP)

## **Fetch Errors**

This total is calculated based on the number of resource fetch errors encountered. This is synonymous with an error.badfetch event. Fetch errors include all remote content, including vxml page fetches, audio fetches, and remote request via the \<data> tag.

![](/files/-M5hKPQNmT77eBEzKeak)

## **Fetch Errors per Call**

This graph represents the total number of fetch (error.badfetch) errors divided by the total calls for a given period. This metric is useful in contrast with the Fetch Errors graph because the Fetch Errors per call data should scale linearly with the number of calls, as opposed to the fixed Fetch Errors total.

![](/files/-M5hKPQM91W28HeWXDOg)

## **Average Page Load**

The average page load is calculated as the sum of the time it took to fetch every page divided by the sum of all page fetches. This is displayed as seconds with a precision of 4 decimal places.

![](/files/-M5hKPQLnkyYLh3vsspl)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.plumvoice.com/voicetrends/performance/performance-graphs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.