> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices/3.4.2.2-account-for-connectivity-issues.md).

# 3.4.2.2 Account for connectivity issues

Account for connectivity issues in different regions, considering the deployment options provided by the Building Blocks.

1. Assess Connectivity Conditions and User Needs: Understand the network conditions under which your users will be accessing your service.
2. Optimise Web Performance: Minimise the size of your resources and fix performance issues.
3. Implement Progressive Loading: Design your service so that it loads the most critical content first.
4. Use a Content Delivery Network (CDN): If your users are spread across a wide geographical area, using a CDN can speed up load times.
5. Utilise Service Workers for Offline Functionality: Service workers can intercept network requests and serve cached responses. Google's Workbox can help with this.
6. Choose the Right Caching Strategies: For instance, you might cache static resources for faster loading and implement a "network first, then cache" strategy for dynamic content.
7. Implement Local Storage: Consider storing some data locally on the user's device.
8. Test Under Low-Connectivity Conditions: Use browser developer tools or network throttling tools to simulate various network conditions.


---

# 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://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices/3.4.2.2-account-for-connectivity-issues.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.