Website review, no card needed

amkette.com logo

amkette.com website review

Visit site (opens in a new tab)Reviewed 20 October 202649 issues · 86 checks

This review found 49 issues worth fixing on amkette.com, 20 of them high impact, across 86 checks. The most urgent: 6 images over 500 KB. 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.8 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
205 ms180 msMay 2Oct 17199 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026183 ms
May 9, 2026186 ms
May 16, 2026188 ms
May 23, 2026191 ms
May 30, 2026191 ms
Jun 6, 2026193 ms
Jun 13, 2026193 ms
Jun 20, 2026191 ms
Jun 27, 2026190 ms
Jul 4, 2026187 ms
Jul 11, 2026184 ms
Jul 18, 2026183 ms
Jul 25, 2026186 ms
Aug 1, 2026187 ms
Aug 8, 2026192 ms
Aug 15, 2026194 ms
Aug 22, 2026195 ms
Aug 29, 2026197 ms
Sep 5, 2026199 ms
Sep 12, 2026202 ms
Sep 19, 2026202 ms
Sep 26, 2026202 ms
Oct 3, 2026201 ms
Oct 10, 2026199 ms
Oct 17, 2026199 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 amkette.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amkette.com at 1.1 s1.1 s
  2. amkette.com at 2.2 s2.2 s
  3. amkette.com at 3.2 s3.2 s
  4. amkette.com at 4.3 s4.3 s
  5. amkette.com at 5.4 s5.4 s
  6. amkette.com at 6.5 s6.5 s
  7. amkette.com at 7.6 s7.6 s
  8. amkette.com at 8.6 s8.6 s

Speed

12 to fix33
  • Reduce unused JavaScript

    2.4 s · 2.8 MB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 20). 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, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,552 HTML elements

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

  • Improve image delivery

    10.9 MB

    61 images could be 10.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, pickrr.com and shiprocket.in and others), adding 2.9 MB and 1.8 s of main-thread time.

  • pickrr.com adds 455 ms

    455 ms

    pickrr.com costs a phone 455 ms of main-thread work and 1.3 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.

  • Google Tag Manager adds 472 ms

    472 ms

    Google Tag Manager costs a phone 472 ms of main-thread work and 541 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 adds 357 ms

    357 ms

    shiprocket.in costs a phone 357 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.

  • 15 long tasks on the main thread

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

  • Shopify adds 109 ms

    109 ms

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

  • Minify JavaScript

    150 ms · 76 KiB

    76 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • Use efficient cache lifetimes

    122 KiB

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

  • 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: 10 ms

    10 ms

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

Core Web Vitals

12 to fix0
  • 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: 45.8 s

    45.8 s

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

  • Time to Interactive: 53.1 s

    53.1 s

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

  • Speed Index: 13.1 s

    13.1 s

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

  • Total Blocking Time: 938 ms

    938 ms

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.5 s

    3.5 s

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

  • Real-user INP: 215 ms

    215 ms

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

  • Real-user CLS: 0.16

    0.16

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 47 images without width and height

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

  • Cumulative Layout Shift: 0.15

    0.15

    The layout shifts by 0.15 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

1 checks passed
  • Real-user TTFB: 747 ms

    747 ms

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

Images and page weight

5 to fix18
  • 6 images over 500 KB

    6 images weigh 60.5 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 17.2 MB in 370 requests

    17.2 MB

    Your homepage downloads 17.2 MB in 370 requests on a phone: images 13.3 MB (148), scripts 2.5 MB (89) and other files 1,006 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • 22 images far larger than shown

    2.9 MB

    22 images are downloaded at several times the size a phone draws them, for example EvoFoxAIMobileCooler.390.png at 3,840 px wide, shown at 82 px. Resized copies would save about 2.9 MB.

  • 5 images in older formats

    5 images (60.0 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.

  • 21 images below the first screen load straight away

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

  • About 4.9 g of CO₂ per visit

    4.88 g

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

Accessibility

11 to fixGoogle 8787
  • 33 buttons without a name

    33 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    7 elements hidden from screen readers can still receive keyboard focus.

  • [role="img"] and [role="image"] elements must have alternative text (5 elements)

    [role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.

  • 4 text elements with low contrast

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

  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

  • 18 links without text

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

  • 6 form fields without a label

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

  • ARIA role should be appropriate for the element (4 elements)

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

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 226 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 11 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 9293
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “In The Press” and “Testimonials”). One clear main headline is easier for people and search engines.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 235 internal links, 35 external

    The homepage links to 235 pages on amkette.com and 35 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Shop the latest Wireless Earbuds, Speakers, Gaming Keyboards, IT Peripherals, and Accessories, available online at a ve…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Amkette | EvoFox | TWS | IT Peripherals | Accessories”.

  • Canonical URL set

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

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

AI search readiness

100
4 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,515 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 7385
  • 68 small tap targets

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

  • 6 third-party cookies

    6 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 null (reading 'addEventListener')”.

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

  • Thin social proof

    Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

3 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Track Your Order”, “Register Your Product” and “Join the Tribe”.

  • 38 short forms

    38 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 16 cookies set on arrival

    16

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

  • 31 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

Company

Founded
1984
Headquarters
New Delhi

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on amkette.com, including 24 speed issues, 2 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