> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/theme-settings/optimizations.md). # Optimizations ### Performance * **Enable instant.page library** to preload the next page as a user hovers over a link. This will feel faster to the user, but it will not impact performance scores done by testing tools such as Google lighthouse, as these tools only measure the performance of the initial page load. There is a chance that instant.page will not work with third party apps or analytics services depending on how they are loaded, so you may wish to disable this option if experiencing any issues with your apps. ### Accessibility * **Show focus outlines on text inputs:** By default, the browser will show an outline around inputs that are currently focused. This is required for accessibility if the user is using a screenreader or keyboard to navigate. If this option is **disabled**, we use a third-party library to detect if a user is using a mouse or touch screen, and hide the outlines. If you want to minimize the use of uneccessary javascript libaries or you are concerned about accessibility, you can enable this option. * **Video description button on videos:** By default, we use the video alt text as a video description in order allow merchants to meet the [1.2.1 Audio-only and Video-only (Prerecorded)](https://www.w3.org/TR/WCAG22/#audio-only-and-video-only-prerecorded) success criterion of the Web Content Accessibility Guidelines. You can disable this option if needed, but please note that not including an alternative to video content is an accessibility failure and may put you at a increased risk of litigation. --- # 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.ultramarinastudios.com/theme-settings/optimizations.md?ask=&goal= ``` `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.