ummejannah.com website review

12 images could be 497 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, TikTok and Google Tag Manager and others), adding 1.1 MB and 447 ms of main-thread time.

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

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

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

Google Fonts costs a phone 0 ms of main-thread work and 351 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.

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

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

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

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 9.3 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 10.8 s. Good is under 3.8 s.

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

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 160 requests on a phone: images 1.1 MB (23), scripts 870 KiB (43) and other files 726 KiB (83). Under 2 MB keeps phones on slow connections fast.

Gemini_Generated_Image_hsgbtfhsgbtfhsgb.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).

4 images are downloaded at several times the size a phone draws them, for example 28E3C78C-E048-4B2D-B4D4-BBE7FC56CD70.jpg at 900 px wide, shown at 189 px. Resized copies would save about 211 KiB.

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

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

1 text element doesn'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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 24 characters: “Umme Jannah – UmmeJannah”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 104 pages on ummejannah.com and 4 external pages.

https://ummejannah.com/pages/b2b, https://ummejannah.com/collections/new-arrivals-1, https://ummejannah.com/collections/kids-abaya, https://ummejannah.com/collections/premium-modal and https://ummejannah.com/collections/lace-modal have no meta description, so Google writes the search snippet from whatever text it finds.

https://ummejannah.com/collections/new-arrivals-1, https://ummejannah.com/collections/abayas, https://ummejannah.com/collections/kids-abaya, https://ummejannah.com/collections/georgette-hijab, https://ummejannah.com/collections/jersey-hijabs and https://ummejannah.com/collections/modal-hijabs and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://ummejannah.com/.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 778 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 Tag Manager, Meta Pixel, Snap Pixel and TikTok Pixel (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 18 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.