sagnomore.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.9 s faster on a phone.

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (YouTube, ecomposer.app and Clarity and others), adding 6.5 MB and 1.0 s of main-thread time.

11 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

YouTube costs a phone 682 ms of main-thread work and 1.9 MB 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.

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

Shopify costs a phone 29 ms of main-thread work and 4.1 MB 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 1,990 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

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.

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

Your largest element takes 32.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SHOP NOW”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 9.5 MB in 367 requests on a phone: images 5.4 MB (36), scripts 2.5 MB (157) and other files 910 KiB (140). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Untitled_design_2_9dfab22a-d0c3-4825-8b04-d38be6e77535.png at 1,280 px wide, shown at 350 px. Resized copies would save about 26 KiB.

8 images further down the page (305 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

2 buttons have no accessible name, so screen readers announce just “button”.

8 tap targets are too small or too close together to hit reliably with a finger.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 64 pages on sagnomore.com and 5 external pages.

https://sagnomore.com/collections/neck-less and https://sagnomore.com/pages/neck-less%C2%AE-50-off-promotion-terms-conditions all use the title “Fix Neck Sag Without Surgery | Neck Less by Sagnomore”. Search engines can't tell which page to show for a search, so each competes with the others.

https://sagnomore.com/collections/neck-less and https://sagnomore.com/pages/neck-less%C2%AE-50-off-promotion-terms-conditions use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://sagnomore.com/pages/collections, whose canonical is https://sagnomore.com/collections/neck-less. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sagnomore.com/collections/neck-less, https://sagnomore.com/products/neck-less-no-trace-bundle-for-short-hair, https://sagnomore.com/pages/collections, https://sagnomore.com/pages/neck-less%C2%AE-50-off-promotion-terms-conditions and https://sagnomore.com/collections/neckless-one-time-purchase have no <h1> headline, so visitors and search engines get no clear main topic.

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

7 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,488 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 21 cookies, 1 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.