# Lightweight Telemetry The foundation of Signet is its microscopic footprint. In an ecosystem where third-party scripts are the primary cause of slow load times and main-thread blocking, Signet takes a radical approach to efficiency. #### The 1KB Standard Our tracking script has been optimized down to less than 1KB in size. For comparison, legacy analytics tags often exceed 45KB and pull in additional dependencies that can bloat the total payload to over 100KB. Signet executes in a single, non-blocking network request. This ensures that the integration of analytics has zero perceptible impact on the end-user experience. #### Core Web Vitals Protection Search engines prioritize user experience metrics, specifically the Core Web Vitals: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Heavy analytics scripts often degrade these scores by consuming CPU cycles during the critical initial rendering phase. Signet is designed to be invisible to these metrics. It loads asynchronously and defers execution until critical resources have settled, ensuring that your SEO rankings are never compromised by your analytics tools. #### Global Edge Delivery The script is distributed via a high-performance content delivery network with points of presence across the globe. Whether your user is accessing your application from Tokyo, London, or San Francisco, the latency remains negligible. This edge-first architecture ensures that data collection is reliable even on slow cellular networks or high-latency connections. --- # 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.signtoken.vip/2.-core-features/lightweight-telemetry.md?ask= ``` 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.