mamshie.com website review

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

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

5 third-party services load with your homepage (leadconnectorhq.com, Cloudflare and Google Fonts and others), adding 13.1 MB and 215 ms of main-thread time.

filesafe.space costs a phone 0 ms of main-thread work and 10.6 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.

About 162 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

leadconnectorhq.com costs a phone 166 ms of main-thread work and 690 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.

imagekit.io costs a phone 0 ms of main-thread work and 1.7 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.

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

1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

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

Polyfills for old browsers add 10 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.

Your largest element takes 54.8 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 54.9 s. Good is under 3.8 s.

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

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

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

6 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 13.2 MB in 103 requests on a phone: images 12.2 MB (21), scripts 557 KiB (50) and fonts 262 KiB (6). Under 2 MB keeps phones on slow connections fast.

4 images weigh 10.5 MB together. On a phone connection a single image that size takes seconds.

21 images are downloaded at several times the size a phone draws them, for example 6a60dab344497f2c4a523b58.png at 1,360 px wide, shown at 390 px. Resized copies would save about 5.4 MB.

5 images (10.6 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.

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

6a60dab344497f2c4a523b58.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 3.74 g of CO₂e: 449.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 18 characters: “MamShie Essentials”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 7 <h1> headlines (“Drop the Invisible Load, MamShie.”, “Drop the Invisible Load, MamShie.” and “My Featured Products”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://mamshie.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 39 pages on mamshie.com and 5 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://mamshie.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://mamshie.com/products-list/collections/resources-for-young-families, https://mamshie.com/products-list/collections/stationery-goodies and https://mamshie.com/products-list/collections/digital-assets-raw-illustrations have no <title>, so Google invents the link text in results.

/, https://mamshie.com/shop-now, https://mamshie.com/about and https://mamshie.com/products-list all use the title “MamShie Essentials”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mamshie.com/shop-now, https://mamshie.com/about, https://mamshie.com/products-list, https://mamshie.com/products-list/collections/resources-for-young-families, https://mamshie.com/products-list/collections/stationery-goodies and https://mamshie.com/products-list/collections/digital-assets-raw-illustrations and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mamshie.com/products-list, https://mamshie.com/products-list/collections/resources-for-young-families, https://mamshie.com/products-list/collections/stationery-goodies, https://mamshie.com/products-list/collections/digital-assets-raw-illustrations, https://mamshie.com/product-details/product/diye-i-can-read-program and https://mamshie.com/product-details/product/diye-kakapit-o-kakabit and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mamshie.com/product-details/product/diye-i-can-read-program, https://mamshie.com/product-details/product/diye-kakapit-o-kakabit, https://mamshie.com/product-details/product/diye-baby-book-v2-collection, https://mamshie.com/product-details/product/diye-the-book-of-psalms-volume-2, https://mamshie.com/product-details/product/diye-the-god-of-my-little-things-volume-3 and https://mamshie.com/product-details/product/diye-loving-beyond-today and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Opening the homepage sets 4 cookies, 2 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.