> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.nector.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Nector & Website Speed — Explained Clearly

# 🚀 Understanding Website Speed Impact with Nector Scripts

## Introduction  
Some brands may notice Nector scripts appearing in tools like **Google PageSpeed Insights or Lighthouse** and assume they are slowing down their website.  

This article clarifies how Nector scripts actually behave, why they appear in performance reports, and how to validate their real impact on your site’s speed.

---

## Step 1: How Nector Scripts Load on Your Website  

Nector scripts are designed to load **asynchronously and in a deferred manner**.  

This means:  
* They load **only after your primary website content is visible**  
* They do **not block critical rendering**  
* They do **not delay the initial user experience**

Additionally:  
* All Nector scripts and APIs are **cached at the edge (CDN level)**  
* This ensures **maximum performance and minimal latency globally**  
* Requests are served from the **nearest location to the user**, reducing load time further  

👉 In simple terms: your customers can interact with your website **before Nector scripts even begin loading**, and when they do load, they are delivered **fast and efficiently**.

---

## Step 2: Why Nector Appears in Performance Reports  

Tools like **Google PageSpeed Insights and Lighthouse** analyse the **entire lifecycle of your webpage**, not just the initial load.

This includes:  
* Scripts that load **after the page is visible**  
* Background scripts that are **non-blocking**  
* Total resource weight (not just performance impact)

Because of this:  
👉 Even **deferred and non-blocking scripts like Nector’s** may still appear in reports  
👉 This can sometimes give the impression that they affect speed — even when they don’t impact real user experience  

---

## Step 3: Validate the Actual Impact (Recommended Test)  

To confirm this on your own website, you can run a simple test:

1. Temporarily disable Nector scripts  
2. Run your website through **PageSpeed Insights or Lighthouse**  
3. Compare:
* Initial load time  
* First Contentful Paint (FCP)  
* User interaction readiness  

💡 You’ll notice that:  
* **Core performance metrics remain largely unchanged**  
* The **user experience stays the same**  

---

## Step 4: What This Means for Your Brand  

Even if Nector appears in performance tools:  

* ❌ It does **not slow down your storefront experience**  
* ❌ It does **not block page rendering**  
* ❌ It does **not impact customer interaction timing**  

Instead, Nector operates in the background — ensuring:  
* Loyalty widgets  
* Rewards  
* Referrals  
* Reviews  

…are loaded **only after your site is already usable**, and delivered via **high-speed edge caching infrastructure**.

---

## Why This Matters 💡  

For growth-focused brands, the priority is:  
👉 Fast user experience **+** engagement features  

Nector is built to support both by:  
* Keeping your storefront performance intact  
* Delivering scripts via **edge caching for faster response times**  
* Adding retention layers without compromise  

---

## 🎯 Pro Tip  

When evaluating performance tools like **PageSpeed Insights or Lighthouse**:  
* Focus on **real user metrics** (FCP, LCP, TTI)  
* Not just total script weight  

Because:  
👉 Not all scripts that appear in reports actually affect performance  

---

## 🚀 Wrap-Up  

Nector scripts are intentionally designed to be:  

* ✔ Non-blocking  
* ✔ Asynchronous  
* ✔ Edge-cached for low latency  
* ✔ Performance-safe  

While tools may still list them in reports, the **actual customer experience remains fast, smooth, and unaffected**.

If you’d like help reviewing your setup or validating performance further, our team is always here to assist 💛