Website review, no card needed

amlfoods.com logo

amlfoods.com website review

Visit site (opens in a new tab)Reviewed 28 October 202642 issues · 84 checks

This review found 42 issues worth fixing on amlfoods.com, 14 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
3.3 s1.0 sJul 11Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
Jul 11, 20261.3 s
Sep 12, 20262.7 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
307 ms227 msSep 12Oct 24298 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 2026261 ms
Sep 19, 2026256 ms
Sep 26, 2026248 ms
Oct 3, 2026236 ms
Oct 10, 2026263 ms
Oct 17, 2026271 ms
Oct 24, 2026298 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 amlfoods.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amlfoods.com at 0.6 s0.6 s
  2. amlfoods.com at 1.1 s1.1 s
  3. amlfoods.com at 1.7 s1.7 s
  4. amlfoods.com at 2.2 s2.2 s
  5. amlfoods.com at 2.8 s2.8 s
  6. amlfoods.com at 3.4 s3.4 s
  7. amlfoods.com at 3.9 s3.9 s
  8. amlfoods.com at 4.5 s4.5 s

Speed

9 to fix40
  • Improve image delivery

    3.5 s · 2.2 MB

    23 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.

  • Reduce unused JavaScript

    1.9 s · 817 KiB

    About 817 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.

  • Use efficient cache lifetimes

    1.1 s · 238 KiB

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

  • Mobile performance score: 40

    40/100

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

  • Reduce unused CSS

    600 ms · 144 KiB

    About 144 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.

  • Render-blocking requests

    700 ms

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 817 KiB and 590 ms of main-thread time.

  • Font display

    450 ms

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

  • Google Tag Manager adds 333 ms

    333 ms

    Google Tag Manager costs a phone 333 ms of main-thread work and 518 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.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 20 KiB

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 116 ms

    116 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.7 s

    12.7 s

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

  • Time to Interactive: 21.9 s

    21.9 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • Cumulative Layout Shift: 0.328

    0.328

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

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

    3.0 s

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

  • Real-user INP: 305 ms

    305 ms

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

  • Largest content (LCP) got 52% slower for real visitors

    +52%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Total Blocking Time: 225 ms

    225 ms

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

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

    +10%

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

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

Images and page weight

4 to fix43
  • Page weight: 5.4 MB in 121 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 121 requests on a phone: images 3.5 MB (35), scripts 1.5 MB (64) and stylesheets 145 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 18 images in older formats

    18 images (2.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.

  • 12 images below the first screen load straight away

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

  • 1 image far larger than shown

    3 KiB

    1 image is downloaded at several times the size a phone draws it, for example aml-logo.jpg at 238 px wide, shown at 77 px. Resized copies would save about 3 KiB.

  • About 1.5 g of CO₂ per visit

    1.52 g

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

Accessibility

4 to fixGoogle 8894
  • 21 text elements with low contrast

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

  • 5 tap targets too small

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 28 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

4 to fixGoogle 10080
  • Title is long (130 characters)

    Your title is 130 characters, so Google will cut it off around 60: “AML Foods: Leading Grocery Provider in The Bahamas | Solomon’s, Fresh Market, Cost Right,…”.

  • 5 H1 headlines

    There are 5 <h1> headlines (“Shop Online”, “Brand Updates” and “Values”). One clear main headline is easier for people and search engines.

  • Meta description is long (449 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 55 internal links, 25 external

    The homepage links to 55 pages on amlfoods.com and 25 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://amlfoods.com/home/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

  • No llms.txt

    There is no https://amlfoods.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 (389 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 2 pages without a meta description

    https://amlfoods.com/cost-right-memberships and https://amlfoods.com/first-care have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://amlfoods.com/incoming-vendor-products and https://amlfoods.com/ecommerce use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://amlfoods.com/cost-right-memberships and https://amlfoods.com/first-care have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://amlfoods.com/solomons-fresh-markets has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://amlfoods.com/eleuthera-markets and https://amlfoods.com/harbour-island-markets took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 to fixGoogle 10093
  • 5 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

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

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

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

  • Thin social proof

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 253 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop Online”, “Contact Us” and “LEARN MORE”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

  • 13 cookies set on arrival

    13

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 amlfoods.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
React
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on amlfoods.com, including 21 speed issues, 4 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