Website review, no card needed

neemans.com logo

neemans.com website review

Visit site (opens in a new tab)Reviewed 19 November 202643 issues · 91 checks

This review found 43 issues worth fixing on neemans.com, 12 of them high impact, across 91 checks. The most urgent: main-thread work: 19.1 s. 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.9 s2.3 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.4 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.6 s
Oct 31, 20262.6 s
Nov 7, 20262.5 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
348 ms215 msMay 30Nov 14317 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026230 ms
Jun 6, 2026243 ms
Jun 13, 2026254 ms
Jun 20, 2026257 ms
Jun 27, 2026254 ms
Jul 4, 2026253 ms
Jul 11, 2026252 ms
Jul 18, 2026256 ms
Jul 25, 2026265 ms
Aug 1, 2026270 ms
Aug 8, 2026279 ms
Aug 15, 2026280 ms
Aug 22, 2026274 ms
Aug 29, 2026269 ms
Sep 5, 2026265 ms
Sep 12, 2026266 ms
Sep 19, 2026278 ms
Sep 26, 2026288 ms
Oct 3, 2026295 ms
Oct 10, 2026311 ms
Oct 17, 2026323 ms
Oct 24, 2026328 ms
Oct 31, 2026333 ms
Nov 7, 2026328 ms
Nov 14, 2026317 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 neemans.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. neemans.com at 1.8 s1.8 s
  2. neemans.com at 3.6 s3.6 s
  3. neemans.com at 5.4 s5.4 s
  4. neemans.com at 7.1 s7.1 s
  5. neemans.com at 8.9 s8.9 s
  6. neemans.com at 10.7 s10.7 s
  7. neemans.com at 12.5 s12.5 s
  8. neemans.com at 14.3 s14.3 s

Speed

13 to fix45
  • Main-thread work: 19.1 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 720 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 45

    45/100

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

  • 5,979 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and gokwik.co and others), adding 2.3 MB and 3.0 s of main-thread time.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    50 ms · 899 KiB

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

  • Render-blocking requests

    800 ms

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

  • Clarity adds 572 ms

    572 ms

    Clarity costs a phone 572 ms of main-thread work and 29 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.

  • gokwik.co adds 463 ms

    463 ms

    gokwik.co costs a phone 463 ms of main-thread work and 820 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.

  • 20 long tasks on the main thread

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

  • Convert Insights adds 270 ms

    270 ms

    Convert Insights costs a phone 270 ms of main-thread work and 158 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.

  • Shopify adds 257 ms

    257 ms

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

  • Improve image delivery

    50 ms · 107 KiB

    6 images could be 107 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

  • Reduce unused CSS

    79 KiB

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

  • Minify JavaScript

    72 KiB

    72 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    36 KiB

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

  • Duplicated JavaScript

    24 KiB

    24 KiB JavaScript is shipped twice across bundles.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 30 ms

    30 ms

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

Core Web Vitals

10 to fix33
  • 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.

  • Time to Interactive: 30.0 s

    30.0 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Largest Contentful Paint: 4.8 s

    4.8 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 322 ms

    322 ms

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

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

    +36%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 934 ms

    934 ms

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix64
  • Page weight: 6.2 MB in 697 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 697 requests on a phone: scripts 2.6 MB (124), other files 1.9 MB (429) and images 1.0 MB (89). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    App_Banner_c64d0ae9-62fa-4e7a-aa4a-1f9c89a8d5b1.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 1.8 g of CO₂ per visit

    1.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.76 g of CO₂e: 211.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

7 to fixGoogle 8592
  • 94 text elements with low contrast

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

  • 8 tap targets too small

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

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

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

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

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

  • 2 form fields without a label

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

  • 2 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

2 checks passed
  • Every image has alt text

    All 369 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • Structured data has 2 problems

    Structured data found (BreadcrumbList and ImageObject) but with 2 problems, for example “ImageObject: contentUrl is not an absolute URL ("//neemans.com/cdn/shop/files/Desktop_Banner_14.jpg…”.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 370 internal links, 7 external

    The homepage links to 370 pages on neemans.com and 7 external pages.

7 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Footwear for Men & Women - Explore the wide range of stylish Sneakers, Slip Ons, Slippers & Loafers for men & women onl…”.

  • One H1 headline

    Your main headline reads: “Buy Shoes for Men & Women Online - Neemans”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Buy Shoes for Men & Women Online - Neemans”.

  • Canonical URL set

    The canonical URL is https://neemans.com/.

  • 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://neemans.com/sitemap.xml.

AI search readiness

2 to fix70
  • 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.

  • Parts of the site are closed to 1 AI crawler

    Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

2 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (2,238 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://neemans.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://neemans.com/pages/download-the-app and https://neemans.com/pages/neemans-order-tracker have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://neemans.com/pages/storelocator, https://neemans.com/pages/download-the-app, https://neemans.com/collections/all-products, https://neemans.com/pages/neemans-comfort-club, https://neemans.com/pages/neemans-order-tracker and https://neemans.com/pages/brand-impact and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 136 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

3 to fixGoogle 7385
  • 10 small tap targets

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

  • 5 third-party cookies

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

  • 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

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  • About 1,540 words of copy

    The homepage carries about 1,540 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download App” and “Search Download App Search”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Download App”, “Download Mobile App” and “🏷️ Buy 2 Get 7%, Buy 3 Get 10%”.

  • 28 short forms

    28 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 186 testimonial or review blocks, 2 customer or partner logos, a star rating and “trusted by 5M+ customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager 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.

  • 26 cookies set on arrival

    26

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

  • 44 other companies contacted

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

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Gokwik Cart Slide Cart Drawer · Togethr · Fealtyx Neeman · amazonaws.com · nitrocommerce.ai

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Employees
260
Headquarters
Hyderabad

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on neemans.com, including 23 speed issues, 2 SEO issues and 1 conversion gap. 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