> For the complete documentation index, see [llms.txt](https://pwa.spomky-labs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwa.spomky-labs.com/1.3.x/symfony-ux/network-information.md).

# Network Information

This controller uses the Network Information API\
to detect changes in the user’s network connection.\
It emits an event whenever the connection type or state changes (for example, switching from Wi-Fi to 4G).

**Usage**

```twig
<div data-controller="network-info">
  <p id="network-status">Loading network info...</p>
</div>

<script type="module">
  const el = document.querySelector('[data-controller="network-info"]');

  el.addEventListener('network-info:change', (e) => {
    const c = e.detail.connection;
    document.getElementById('network-status').textContent =
      `Type: ${c.effectiveType}, Downlink: ${c.downlink} Mbps, RTT: ${c.rtt} ms`;
  });
</script>
```

### Parameters

None

### Actions

None

### Targets

None

### Events

change: Emitted on controller connection and every time the browser detects a change in network conditions. Contains the NetworkInformation object with&#x20;

* `effectiveType`: the estimated connection type (`'slow-2g'`, `'2g'`, `'3g'`, `'4g'`, etc.)
* `downlink`: estimated bandwidth in megabits per second
* `rtt`: estimated round-trip latency in milliseconds
* `saveData`: `true` if the user has enabled data-saver mode
* `type`: (optional) connection medium (`'wifi'`, `'cellular'`, `'ethernet'`, `'none'`, etc., when supported)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://pwa.spomky-labs.com/1.3.x/symfony-ux/network-information.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.