showoffff.in website review

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

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

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

8 third-party services load with your homepage (shiprocket.in, ContentSquare and Shopify and others), adding 2.5 MB and 1.6 s of main-thread time.

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

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

Your mobile performance score is 52 (desktop: 39). Pages that score under 90 lose visitors before the first paint.

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

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

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

shiprocket.in costs a phone 308 ms of main-thread work and 120 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.

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

gokwik.co costs a phone 224 ms of main-thread work and 866 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 290 ms of main-thread work and 177 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.

starapps.studio costs a phone 164 ms of main-thread work and 386 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 2,010 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

81 KiB could be saved by minifying JavaScript.

25 KiB JavaScript is shipped twice across bundles.

16 KiB could be saved by minifying CSS.

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.

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 18.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 28.0 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 430 requests on a phone: scripts 2.8 MB (98), images 1.9 MB (46) and other files 1.2 MB (252). Under 2 MB keeps phones on slow connections fast.

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

6 images (3.2 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.

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

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

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

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Alternative text of images should not be repeated as text: 4 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.

2 links have no real href, so search engines can't follow them.

The homepage links to 240 pages on showoffff.in and 9 external pages.

There is no https://showoffff.in/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://showoffff.in/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://showoffff.in/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://showoffff.in/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://showoffff.in/customer_authentication/redirect, https://showoffff.in/collections/mens-new-arrivals, https://showoffff.in/collections/womens-new-arrivals, https://showoffff.in/collections/men-bestsellers, https://showoffff.in/collections/women-bestsellers and https://showoffff.in/collections/women-dresses and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: “700K+ ACTIVE CUSTOMERS”. 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 shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 591 words of visible text.

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