Website review, no card needed

mishalakhani.com logo

mishalakhani.com website review

Visit site (opens in a new tab)Reviewed 3 November 202633 issues · 78 checks

This review found 33 issues worth fixing on mishalakhani.com, 10 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
2.1 s1.6 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20262.0 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
147 ms79 msMay 16Oct 31139 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202688 ms
May 30, 202687 ms
Jun 6, 202687 ms
Jun 13, 202691 ms
Jun 20, 202694 ms
Jun 27, 202695 ms
Jul 4, 202699 ms
Jul 11, 202699 ms
Jul 18, 202695 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202697 ms
Aug 15, 2026101 ms
Aug 22, 202698 ms
Aug 29, 202698 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202697 ms
Sep 26, 202697 ms
Oct 3, 2026101 ms
Oct 10, 2026111 ms
Oct 17, 2026128 ms
Oct 24, 2026138 ms
Oct 31, 2026139 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

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

How it loaded on a phone

  1. mishalakhani.com at 4.3 s4.3 s
  2. mishalakhani.com at 8.6 s8.6 s
  3. mishalakhani.com at 12.9 s12.9 s
  4. mishalakhani.com at 17.2 s17.2 s
  5. mishalakhani.com at 21.5 s21.5 s
  6. mishalakhani.com at 25.8 s25.8 s
  7. mishalakhani.com at 30.1 s30.1 s
  8. mishalakhani.com at 34.4 s34.4 s

Speed

9 to fix58
  • Reduce unused JavaScript

    1.9 s · 381 KiB

    About 381 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Main-thread work: 4.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (ContentSquare, Clarity and Snapchat and others), adding 1,014 KiB and 1.1 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • ContentSquare adds 497 ms

    497 ms

    ContentSquare costs a phone 497 ms of main-thread work and 162 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.

  • Render-blocking requests

    450 ms

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

  • Use efficient cache lifetimes

    350 ms · 82 KiB

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

  • Improve image delivery

    352 KiB

    5 images could be 352 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • azurefd.net adds 34 ms

    34 ms

    azurefd.net costs a phone 34 ms of main-thread work and 320 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.

  • Reduce unused CSS

    200 ms · 37 KiB

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

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 125 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.

  • Legacy JavaScript

    4 KiB

    Polyfills for old browsers add 4 KiB JavaScript that modern phones do not need.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 14.9 s

    14.9 s

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

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Tap response (INP) got 57% slower for real visitors

    +57%

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

  • Real-user TTFB: 822 ms

    822 ms

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

  • Largest content (LCP) held steady for real visitors

    0%

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

5 checks passed
  • Real-user INP: 149 ms

    149 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Total Blocking Time: 142 ms

    142 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.3 MB in 299 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 299 requests on a phone: scripts 1.1 MB (75), other files 1.1 MB (204) and images 936 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    12_M_F.jpg 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).

  • About 0.9 g of CO₂ per visit

    0.93 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9396
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 links without text

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 101 internal links, 6 external

    The homepage links to 101 pages on mishalakhani.com and 6 external pages.

8 checks passed
  • Meta description: 102 characters

    Your meta description is 102 characters: “Official Misha Lakhani estore. Refresh your wardrobe with our latest ready to wear and couture styles.”.

  • One H1 headline

    Your main headline reads: “MISHA LAKHANI”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Misha Lakhani | Official Estore”.

  • Canonical URL set

    The canonical URL is https://www.mishalakhani.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mishalakhani.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

    The site publishes https://www.mishalakhani.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://www.mishalakhani.com/collections/tunics-kurtas-cc, https://www.mishalakhani.com/collections/everyday-jackets, https://www.mishalakhani.com/collections/kaftans-jalabiyas, https://www.mishalakhani.com/collections/co-ord-sets, https://www.mishalakhani.com/collections/pants-rtw and https://www.mishalakhani.com/collections/kaftans and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.mishalakhani.com/collections/new-arrivals, https://www.mishalakhani.com/collections/wardrobe-staples, https://www.mishalakhani.com/collections/tunics-kurtas-cc, https://www.mishalakhani.com/collections/everyday-jackets, https://www.mishalakhani.com/collections/kaftans-jalabiyas and https://www.mishalakhani.com/collections/co-ord-sets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://www.mishalakhani.com/collections/new-arrivals, https://www.mishalakhani.com/collections/wardrobe-staples, https://www.mishalakhani.com/collections/tunics-kurtas-cc, https://www.mishalakhani.com/collections/everyday-jackets, https://www.mishalakhani.com/collections/kaftans-jalabiyas and https://www.mishalakhani.com/collections/co-ord-sets and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 6 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'push')”.

  • 1 distorted image

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

  • Browser-reported issues

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

1 checks passed
  • 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 44 words

    The homepage has only about 44 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
  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP ALL” and “CALL US”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    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.

  • 19 cookies set on arrival

    19

    Opening the homepage sets 19 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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 mishalakhani.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on mishalakhani.com, including 17 speed 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