studiobeej.com website review

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

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

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

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

About 186 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (shiprocket.in, Google Tag Manager and Facebook and others), adding 1.1 MB and 1.6 s of main-thread time.

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

shiprocket.in costs a phone 430 ms of main-thread work and 76 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 Tag Manager costs a phone 306 ms of main-thread work and 437 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.

36 KiB could be saved by minifying JavaScript.

The page has 1,981 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

34 KiB could be saved by minifying CSS.

Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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 9.1 s on a phone. Good is under 1.8 s.

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

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

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

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

56 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 7.9 MB in 367 requests on a phone: images 3.5 MB (60), scripts 2.8 MB (116) and other files 989 KiB (151). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example vanya-cork-saddle-bag-group-mood-shot_1024x.jpg at 1,024 px wide, shown at 165 px. Resized copies would save about 1.3 MB.

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

10 images (763 KiB) 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.

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

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

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

2 links inside paragraphs rely on colour alone to stand out.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 27 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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 67 characters, so Google will cut it off around 60: “Sustainable fashion and lifestyle accessories in India- Studio Beej”.

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

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

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

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

The homepage links to 189 pages on studiobeej.com and 4 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.

https://studiobeej.com/collections/new-arrivals and https://studiobeej.com/collections/bestsellers have no meta description, so Google writes the search snippet from whatever text it finds.

https://studiobeej.com/collections/summer-edit, https://studiobeej.com/collections/new-arrivals, https://studiobeej.com/collections/bestsellers, https://studiobeej.com/collections/reverse, https://studiobeej.com/collections/handbags and https://studiobeej.com/collections/accessories have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://instafeed.nfcube.com/assets/img/loader.gif.

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

6 errors were logged to the browser console while the page loaded, for example “MinMaxify is deactivated for this website. Please don't forget to remove minmaxify-head.liquid still being referenced b…”.

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

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

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 615 words of visible text.

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 22 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.