looplaboratories.com website review

About 611 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

A phone's processor spends 6.1 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (alia-prod.com, Shopify and loox.io and others), adding 1.7 MB and 1.0 s of main-thread time.

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

13 files are served with short cache lifetimes, so returning visitors download them again (264 KiB).

Polyfills for old browsers add 55 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

About 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

Shopify costs a phone 200 ms of main-thread work and 752 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 2,506 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

cloudfront.net costs a phone 150 ms of main-thread work and 387 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

12 long tasks block the main thread while loading, the longest for 169 ms. During a long task the page ignores taps.

2 images could be 21 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Load video:”.

The page becomes fully interactive after 15.9 s. Good is under 3.8 s.

Visually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.

Real visitors wait 416 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 375 ms in total while the page loads. Good is under 200 ms.

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 288 ms to 319 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.0 MB in 383 requests on a phone: media 6.0 MB (1), scripts 1.8 MB (171) and other files 916 KiB (149). Under 2 MB keeps phones on slow connections fast.

1 image (50 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 2.82 g of CO₂e: 338.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

17 visible links have no text or label, so screen readers cannot say where they go.

The homepage links to 62 pages on looplaboratories.com and 20 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://zipstring.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://zipstring.com/pages/zipstring-instructions has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://files.alia-prod.com/zipstringlogo.webp-1769038974034.

5 errors were logged to the browser console while the page loaded, for example “Error sending user session Error: Shopify session id is missing”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 129 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 43 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 59 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.