Website review, no card needed

aafeeder.com logo

aafeeder.com website review

Visit site (opens in a new tab)Reviewed 1 November 202653 issues · 99 checks

This review found 53 issues worth fixing on aafeeder.com, 19 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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.3 sMay 9Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
96 ms77 msMay 9Oct 2492 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202679 ms
May 16, 202679 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202690 ms
Jun 13, 202691 ms
Jun 20, 202691 ms
Jun 27, 202694 ms
Jul 4, 202689 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202689 ms
Aug 1, 202694 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202693 ms
Aug 29, 202689 ms
Sep 5, 202689 ms
Sep 12, 202692 ms
Sep 19, 202691 ms
Sep 26, 202694 ms
Oct 3, 202692 ms
Oct 10, 202694 ms
Oct 17, 202693 ms
Oct 24, 202692 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 aafeeder.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aafeeder.com at 0.6 s0.6 s
  2. aafeeder.com at 1.2 s1.2 s
  3. aafeeder.com at 1.9 s1.9 s
  4. aafeeder.com at 2.5 s2.5 s
  5. aafeeder.com at 3.1 s3.1 s
  6. aafeeder.com at 3.7 s3.7 s
  7. aafeeder.com at 4.3 s4.3 s
  8. aafeeder.com at 5.0 s5.0 s

Speed

14 to fix28
  • Reduce unused JavaScript

    1.0 s · 1.0 MB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 28

    28/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, octocom.ai and sticky.io and others), adding 4.3 MB and 1.7 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 680 KiB

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

  • Reduce unused CSS

    610 ms · 74 KiB

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

  • Google Tag Manager adds 368 ms

    368 ms

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

  • 12 long tasks on the main thread

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

  • Bigcommerce adds 206 ms

    206 ms

    Bigcommerce costs a phone 206 ms of main-thread work and 1.7 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

    370 KiB

    6 images could be 370 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • octocom.ai adds 276 ms

    276 ms

    octocom.ai costs a phone 276 ms of main-thread work and 667 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.

  • Main-thread work: 3.4 s

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

  • sticky.io adds 260 ms

    260 ms

    sticky.io costs a phone 260 ms of main-thread work and 347 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.

  • Google CDN adds 190 ms

    190 ms

    Google CDN costs a phone 190 ms of main-thread work and 293 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 · 5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 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.

  • Real-user CLS: 0.26

    0.26

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

  • Time to Interactive: 21.6 s

    21.6 s

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

  • Largest Contentful Paint: 6.1 s

    6.1 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.411

    0.411

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 12 images without width and height

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

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

    +17%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 79 ms to 92 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-24, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 76 ms

    76 ms

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

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

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

Images and page weight

2 to fix64
  • Page weight: 4.8 MB in 118 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 118 requests on a phone: scripts 2.6 MB (52), images 1.4 MB (18) and fonts 622 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AAFPic1.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.3 g of CO₂ per visit

    1.35 g

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

13 to fixGoogle 6884
  • 6 buttons without a name

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

  • 7 tap targets too small

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

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 13 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

8 to fixGoogle 8565
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (17 characters)

    Your title is only 17 characters: “All About Feeders”. 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.

  • Meta description is long (375 characters)

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

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

  • No XML sitemap

    No XML sitemap at https://aafeeder.com/sitemap.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 112 internal links, 7 external

    The homepage links to 112 pages on aafeeder.com and 7 external pages.

2 checks passed
  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

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://aafeeder.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 (459 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 1 page without a meta description

    https://aafeeder.com/silkworms has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://aafeeder.com/dubia-roaches and https://aafeeder.com/roaches/dubia-roaches use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Uncaught NotSupportedError: Failed to execute 'define' on 'CustomElementRegistry': the name "shipfare-information-popup…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 314 words of copy

    The homepage carries about 314 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “DUBIA ROACHES SHOP NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Register”, “Order Protection Instructions” and “Dubia Roaches shop now”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Segment.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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 Segment (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 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 aafeeder.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager | Segment
Hosting
Bigcommerce

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on aafeeder.com, including 22 speed issues, 8 SEO issues and 2 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