LimeSpot is built to load without slowing your store down. Its script loads in the background, and your page appears and works while LimeSpot fills in recommendations.
Availability
Plan: Growth Agents plan · Platform: SHOPLINE
How LimeSpot keeps your pages fast
It doesn't block your page. A small LimeSpot loader sits in your page's head and loads everything else asynchronously. Your theme keeps loading while LimeSpot asks for recommendations, then LimeSpot fills in the boxes when they arrive.
It loads only what's needed. Some LimeSpot content is only drawn when a shopper scrolls to it. Product images in boxes can load lazily, as they come into view.
It picks the right image size. Box images give the browser a choice of sizes, and the browser downloads only the one that suits the shopper's screen.
Ads code waits for consent. The part of LimeSpot used for ad retargeting loads only after a shopper allows marketing cookies.
Its code stays small. LimeSpot's storefront code is checked against strict size limits before every release.
Images and accessibility
Every product image in a LimeSpot box gets the product's title as its alt text. That helps shoppers who use screen readers.
What about SEO?
LimeSpot builds recommendation boxes in the shopper's browser with JavaScript after the page loads. They aren't part of the page HTML your store sends.
Speed scores such as Lighthouse are lab tests. Google ranks pages using real-visitor measurements (Core Web Vitals) and, above all, relevance and engagement. Recommendations that help shoppers find more products can improve engagement.
Note
Don't count on recommendation boxes as search-engine content. Write product descriptions and collection text in your platform as usual.
Keep layout shift low
A box that appears high on the page can push content down as it loads. This is called layout shift, and Google measures it as Cumulative Layout Shift (CLS). To keep it low:
Place boxes below the content shoppers see first, such as below the product description or near the bottom of the page.
On the Home page, avoid placing a box at the very top, above your main banner.
Where a theme already has a product grid in the right spot, replace that grid with a LimeSpot box in Studio instead of adding a new section. See Add, move, replace and delete boxes.
Studio and your Analytics
Working in Studio never counts as a store visit. Your own edits and previews don't affect your traffic numbers in LimeSpot Analytics.
Does LimeSpot change my theme?
LimeSpot only adds what it needs to load: a script tag added to your store.
Troubleshooting
You see | Why | What to do |
A speed test flags a LimeSpot script | Speed tools list every script on the page, including those that load in the background. | Check real-visitor data (Core Web Vitals in Google Search Console) rather than a single lab score. |
Content jumps when a box loads | The box sits above content the shopper is already looking at. | Move the box lower, or replace an existing theme section with it. |