shagna.pk website review

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

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

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

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

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

7 third-party services load with your homepage (Shopify, Google Tag Manager and jQuery CDN and others), adding 548 KiB and 294 ms of main-thread time.

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

About 10 KiB of CSS is downloaded but never applied on this page.

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

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 KiB could be saved by minifying JavaScript.

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 39.7 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 41.3 s. Good is under 3.8 s.

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

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

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

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

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

Your homepage downloads 53.0 MB in 266 requests on a phone: media 42.0 MB (27), images 9.2 MB (24) and other files 853 KiB (121). Under 2 MB keeps phones on slow connections fast.

5 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

1 image (854 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.

1 image further down the page (561 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

5 images are downloaded at several times the size a phone draws them, for example Ek-dopahar-mobile-banner-live-now.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 149 KiB.

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

Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 3 <h1> headlines (“”, “FOR CULTURE TO BE RELEVANT, IT NEEDS TO BE DYNAMIC” and “FOR CULTURE TO BE RELEVANT, IT NEEDS TO BE DYNAMIC”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("mailto:[email protected]")”.

The homepage links to 105 pages on shagna.pk and 11 external pages.

https://shagna.pk/collections/all, https://shagna.pk/collections/dilras-luxury-lawn and https://shagna.pk/collections/ek-dopahar have no meta description, so Google writes the search snippet from whatever text it finds.

https://shagna.pk/products/sp-106-kali-raat, https://shagna.pk/products/sp-107-rang and https://shagna.pk/products/sp-108-nain-tara use the same meta description. A description written for each page earns more clicks.

https://shagna.pk/collections/all, https://shagna.pk/collections/new-arrival, https://shagna.pk/collections/premium-raw-silk, https://shagna.pk/collections/mehfil-festive-formals, https://shagna.pk/collections/dilras-luxury-lawn and https://shagna.pk/collections/ek-dopahar have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

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.

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

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

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