Website review, no card needed

amhuk.in logo

amhuk.in website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 88 checks

This review found 39 issues worth fixing on amhuk.in, 16 of them high impact, across 88 checks. The most urgent: page weight: 102.1 MB in 444 requests. 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
1.5 s1.2 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
200 ms150 msMay 16Oct 31191 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026159 ms
May 23, 2026156 ms
May 30, 2026157 ms
Jun 6, 2026158 ms
Jun 13, 2026165 ms
Jun 20, 2026168 ms
Jun 27, 2026166 ms
Jul 4, 2026172 ms
Jul 11, 2026172 ms
Jul 18, 2026175 ms
Jul 25, 2026180 ms
Aug 1, 2026179 ms
Aug 8, 2026184 ms
Aug 15, 2026187 ms
Aug 22, 2026188 ms
Aug 29, 2026191 ms
Sep 5, 2026190 ms
Sep 12, 2026189 ms
Sep 19, 2026187 ms
Sep 26, 2026187 ms
Oct 3, 2026187 ms
Oct 10, 2026191 ms
Oct 17, 2026192 ms
Oct 24, 2026194 ms
Oct 31, 2026191 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 amhuk.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amhuk.in at 1.4 s1.4 s
  2. amhuk.in at 2.8 s2.8 s
  3. amhuk.in at 4.2 s4.2 s
  4. amhuk.in at 5.6 s5.6 s
  5. amhuk.in at 7.0 s7.0 s
  6. amhuk.in at 8.5 s8.5 s
  7. amhuk.in at 9.9 s9.9 s
  8. amhuk.in at 11.3 s11.3 s

Speed

11 to fix41
  • Use efficient cache lifetimes

    3.5 s · 720 KiB

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

  • Reduce unused JavaScript

    3.4 s · 572 KiB

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

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 9.5 s

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

  • 3,098 HTML elements

    The page has 3,098 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 (Facebook, Shopify and Google Tag Manager and others), adding 99.3 MB and 1.2 s of main-thread time.

  • Shopify adds 207 ms

    207 ms

    Shopify costs a phone 207 ms of main-thread work and 98.2 MB 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

    600 ms · 381 KiB

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

  • Reduce unused CSS

    760 ms · 56 KiB

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

  • Facebook adds 308 ms

    308 ms

    Facebook costs a phone 308 ms of main-thread work and 288 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 182 ms

    182 ms

    gokwik.co costs a phone 182 ms of main-thread work and 510 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 210 ms. During a long task the page ignores taps.

  • Render-blocking requests

    200 ms

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

  • Legacy JavaScript

    150 ms · 49 KiB

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

  • Duplicated JavaScript

    12 KiB

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

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.3 s

    14.3 s

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

  • Speed Index: 18.4 s

    18.4 s

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

  • Time to Interactive: 14.7 s

    14.7 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Total Blocking Time: 759 ms

    759 ms

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

  • Real-user INP: 416 ms

    416 ms

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

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

    +22%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

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

    1.2 s

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

  • Real-user TTFB: 477 ms

    477 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 102.1 MB in 444 requests

    102.1 MB

    Your homepage downloads 102.1 MB in 444 requests on a phone: media 97.2 MB (16), images 2.0 MB (77) and scripts 1.4 MB (61). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Untitled_Design_10_a7a1fa49-2fb6-4f2f-8d79-eacd096ed2f2.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).

  • 1 image far larger than shown

    113 KiB

    1 image is downloaded at several times the size a phone draws it, for example AMHUK_UPI_10_Percent_Offer_High_Quality.png at 7,092 px wide, shown at 374 px. Resized copies would save about 113 KiB.

  • 1 image in older formats

    1 image (64 KiB) is 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.

  • About 28.9 g of CO₂ per visit

    28.93 g

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

Accessibility

8 to fixGoogle 9490
  • ARIA toggle fields must have an accessible name (104 elements)

    ARIA toggle fields must have an accessible name: 104 elements on the page fail this check, rated serious by axe-core.

  • 17 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails 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.

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

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • Meta description is long (290 characters)

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

  • 2 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 103 internal links, 11 external

    The homepage links to 103 pages on amhuk.in and 11 external pages.

6 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Discover Your Style | Online Shopping For Men - ASHTOM”.

  • Canonical URL set

    The canonical URL is https://www.amhuk.in/.

  • Structured data in place

    Structured data found: 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.amhuk.in/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 7 pages share a title

    /, https://www.amhuk.in/collections/all, https://www.amhuk.in/policies/shipping-policy, https://www.amhuk.in/collections/cargo-pant, https://www.amhuk.in/collections/denim-jeans and https://www.amhuk.in/collections/hoodie and 1 other all use the title “Discover Your Style | Online Shopping For Men - ASHTOM”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.amhuk.in/collections/all, https://www.amhuk.in/policies/shipping-policy, https://www.amhuk.in/collections/hoodie and https://www.amhuk.in/collections/joggers have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    6 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 3 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replaceChild')”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    19 of 22 tappable elements near the top are at least 24 px.

  • 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 732 words of copy

    The homepage carries about 732 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop AMHUK Collection”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “Track Your Order” and “Return & Exchange Request”.

  • 5 short forms

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

  • Social proof on the page

    Social proof on the homepage: 75 testimonial or review blocks, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 22 cookies set on arrival

    22

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 amhuk.in, 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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Optis Color Swatch · Quizell Navigation

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

E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on amhuk.in, including 19 speed issues, 3 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