Website review, no card needed

amtradeinc.com logo

amtradeinc.com website review

Visit site (opens in a new tab)Reviewed 20 November 202632 issues · 79 checks

This review found 32 issues worth fixing on amtradeinc.com, 9 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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 amtradeinc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amtradeinc.com at 0.8 s0.8 s
  2. amtradeinc.com at 1.6 s1.6 s
  3. amtradeinc.com at 2.4 s2.4 s
  4. amtradeinc.com at 3.3 s3.3 s
  5. amtradeinc.com at 4.1 s4.1 s
  6. amtradeinc.com at 4.9 s4.9 s
  7. amtradeinc.com at 5.7 s5.7 s
  8. amtradeinc.com at 6.5 s6.5 s

Speed

7 to fix58
  • Use efficient cache lifetimes

    8.5 s · 1.8 MB

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

  • Improve image delivery

    4.3 s · 797 KiB

    5 images could be 797 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.3 s faster on a phone.

  • Render-blocking requests

    4.8 s

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

  • Mobile performance score: 58

    58/100

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

  • Reduce unused CSS

    600 ms · 106 KiB

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

  • Reduce unused JavaScript

    450 ms · 94 KiB

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

  • Font display

    350 ms

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

  • Minify JavaScript

    150 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 14 KiB

    14 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 53 ms. During a long task the page ignores taps.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and mymanhattancom.com), adding 171 KiB and 3 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

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

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 12.0 s

    12.0 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Time to Interactive: 12.0 s

    12.0 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.106

    0.106

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

  • 1 image without width and height

    1 image 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.

1 checks passed
  • Total Blocking Time: 3 ms

    3 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.0 MB in 92 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 92 requests on a phone: images 1.1 MB (11), scripts 370 KiB (41) and fonts 344 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (97 KiB) 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.

  • 2 images below the first screen load straight away

    2 images further down the page (83 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9094
  • 11 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 12 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 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 7773
  • No meta description

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

  • Title is short (7 characters)

    Your title is only 7 characters: “Amtrade”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

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

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

  • No X (Twitter) card tag

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

  • 131 internal links, 0 external

    The homepage links to 131 pages on amtradeinc.com and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “new home”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • 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://www.amtradeinc.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.

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.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 4 pages share 2 titles

    https://www.amtradeinc.com/mtr-brands/ready-to-eat and https://www.amtradeinc.com/indias-nature/ready-to-eat-2 all use the title “Ready to Eat – Amtrade”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.amtradeinc.com/mtr-product-catalogue, https://www.amtradeinc.com/mtr-brands, https://www.amtradeinc.com/mtr-brands/breakfast, https://www.amtradeinc.com/mtr-brands/beverages, https://www.amtradeinc.com/mtr-brands/ready-to-eat and https://www.amtradeinc.com/mtr-brands/ready-to-eat-mixes and 9 others 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 37 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.

  • 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 15 pages that loaded have a <title>.

Best practices

Google 96100
  • 1 low-resolution image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    65 of 66 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 610 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT US”, “Learn More” and “Contact Us”.

  • 2 short forms

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

Privacy and tracking

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

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 amtradeinc.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Hosting
GoDaddy

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on amtradeinc.com, including 13 speed issues, 6 SEO issues and 5 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