sanomads.com website review

38 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

47 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.

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

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

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and Clarity and others), adding 2.1 MB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 555 ms of main-thread work and 674 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.

ContentSquare costs a phone 409 ms of main-thread work and 160 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 1,589 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 24 ms of main-thread work and 1.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.

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

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

Desktop scores 77 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

The layout shifts by 0.256 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

8 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.

13 images weigh 27.0 MB together. On a phone connection a single image that size takes seconds.

24 images are downloaded at several times the size a phone draws them, for example Unveiling_Poppy_shopify_store.webp at 2,652 px wide, shown at 292 px. Resized copies would save about 22.5 MB.

Your homepage downloads 8.4 MB in 332 requests on a phone: images 5.1 MB (55), scripts 1.2 MB (64) and media 1.0 MB (1). Under 2 MB keeps phones on slow connections fast.

23 images further down the page (28.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

20 images (28.1 MB) are 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.

ChatGPT_Image_Sep_25_2026_02_37_29_PM_1_640x640.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

21 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 57 elements on the page fail this check, rated minor by axe-core.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 75 characters, so Google will cut it off around 60: “Sanomads – Shopify Experts Agency | eCommerce Growth Specialists – SANOMADS”.

Your meta description is 170 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

The homepage links to 48 pages on sanomads.com and 16 external pages.

https://www.sanomads.com/pages/ecommerce-marketing, https://www.sanomads.com/pages/shopify-development-services, https://www.sanomads.com/pages/shopify-app-development, https://www.sanomads.com/pages/shopify-design-services, https://www.sanomads.com/pages/seo-services and https://www.sanomads.com/pages/ai-design and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.sanomads.com/pages/case-study, whose canonical is https://www.sanomads.com/pages/case-studies. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://www.sanomads.com/.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Your longest form asks for 9 fields (4 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (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 15 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.