Website review, no card needed

sohojbazar.com logo

sohojbazar.com website review

Visit site (opens in a new tab)Reviewed 9 November 202644 issues · 80 checks

This review found 44 issues worth fixing on sohojbazar.com, 18 of them high impact, across 80 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of sohojbazar.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sohojbazar.com at 0.6 s0.6 s
  2. sohojbazar.com at 1.2 s1.2 s
  3. sohojbazar.com at 1.9 s1.9 s
  4. sohojbazar.com at 2.5 s2.5 s
  5. sohojbazar.com at 3.1 s3.1 s
  6. sohojbazar.com at 3.7 s3.7 s
  7. sohojbazar.com at 4.3 s4.3 s
  8. sohojbazar.com at 4.9 s4.9 s

Speed

8 to fix64
  • Improve image delivery

    32.7 s · 18.5 MB

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

  • Use efficient cache lifetimes

    5.7 s · 2.4 MB

    70 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).

  • Render-blocking requests

    2.9 s

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

  • Font display

    1.1 s

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

  • Reduce unused JavaScript

    900 ms · 152 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Reduce unused CSS

    450 ms · 65 KiB

    About 65 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.

  • Legacy JavaScript

    400 ms · 34 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Facebook, Google Fonts and Bootstrap CDN and others), adding 422 KiB and 135 ms of main-thread time.

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 215 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 43.1 s

    43.1 s

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

  • Time to Interactive: 43.3 s

    43.3 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 10 images without width and height

    10 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 63 ms

    63 ms

    Scripts block the page for only 63 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 19.7 MB in 82 requests

    19.7 MB

    Your homepage downloads 19.7 MB in 82 requests on a phone: images 18.9 MB (39), scripts 521 KiB (18) and fonts 182 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 16.9 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    15.4 MB

    7 images are downloaded at several times the size a phone draws them, for example 2026-06-06-6a240acad564b.png at 3,200 px wide, shown at 370 px. Resized copies would save about 15.4 MB.

  • 21 images in older formats

    21 images (18.8 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.

  • 7 images below the first screen load straight away

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

  • About 5.6 g of CO₂ per visit

    5.58 g

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

Accessibility

10 to fixGoogle 7586
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 1 button without a name

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

  • 2 text elements with low contrast

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

  • 28 images without alt text

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

  • All page content should be contained by landmarks (10 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

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

  • 7 form fields without a label

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7567
  • No meta description

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

  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • No XML sitemap

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

  • 10 links crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 84 internal links, 6 external

    The homepage links to 84 pages on sohojbazar.com and 6 external pages.

2 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Sohoj Bazar Online Shopping | Sohoj Bazar Ecommerce”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://sohojbazar.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.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix83
  • 8 pages share 2 titles

    / and https://sohojbazar.com/lang/en all use the title “Sohoj Bazar Online Shopping | Sohoj Bazar Ecommerce”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://sohojbazar.com/lang/en, https://sohojbazar.com/shop-cart, https://sohojbazar.com/products, https://sohojbazar.com/categories, https://sohojbazar.com/sellers and https://sohojbazar.com/shopView/1 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://sohojbazar.com/lang/en, https://sohojbazar.com/categories, https://sohojbazar.com/sellers, https://sohojbazar.com/shopView/1, https://sohojbazar.com/shopView/2 and https://sohojbazar.com/shopView/3 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://sohojbazar.com/lang/en, https://sohojbazar.com/shop-cart, https://sohojbazar.com/products, https://sohojbazar.com/categories and https://sohojbazar.com/sellers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    31 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • No call to action on the first screen

    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 social proof

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

  • Only about 135 words

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

  • No risk reducer

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

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Sign up”, “Contact Us” and “Track Order”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at sohojbazar.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Namepart

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on sohojbazar.com, including 13 speed issues, 6 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25