Website review, no card needed

primofeeds.com logo

primofeeds.com website review

Visit site (opens in a new tab)Reviewed 8 November 202626 issues · 95 checks

This review found 26 issues worth fixing on primofeeds.com, 7 of them high impact, across 95 checks. The most urgent: page weight: 4.1 MB in 212 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.2 s1.0 sMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
72 ms62 msMay 16Oct 3168 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202663 ms
May 23, 202663 ms
May 30, 202669 ms
Jun 6, 202670 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202670 ms
Jul 11, 202667 ms
Jul 18, 202668 ms
Jul 25, 202667 ms
Aug 1, 202670 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 22, 202668 ms
Aug 29, 202664 ms
Sep 5, 202663 ms
Sep 12, 202665 ms
Sep 19, 202667 ms
Sep 26, 202669 ms
Oct 3, 202670 ms
Oct 10, 202670 ms
Oct 17, 202670 ms
Oct 24, 202670 ms
Oct 31, 202668 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 primofeeds.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. primofeeds.com at 0.4 s0.4 s
  2. primofeeds.com at 0.8 s0.8 s
  3. primofeeds.com at 1.1 s1.1 s
  4. primofeeds.com at 1.5 s1.5 s
  5. primofeeds.com at 1.9 s1.9 s
  6. primofeeds.com at 2.3 s2.3 s
  7. primofeeds.com at 2.6 s2.6 s
  8. primofeeds.com at 3.0 s3.0 s

primofeeds.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix70
  • Mobile performance score: 70

    70/100

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

  • Render-blocking requests

    350 ms

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

  • 1,856 HTML elements

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

  • Improve image delivery

    176 KiB

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

  • 2 long tasks on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, Unpkg and shop.app and others), adding 311 KiB and 49 ms of main-thread time.

  • Reduce unused CSS

    10 KiB

    About 10 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    6 KiB

    4 files are served with short cache lifetimes, so returning visitors download them again (6 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.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 13.7 s

    13.7 s

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

  • Time to Interactive: 14.3 s

    14.3 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 61 ms

    61 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 626 ms

    626 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

  • Total Blocking Time: 64 ms

    64 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 212 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 212 requests on a phone: images 2.8 MB (47), other files 766 KiB (98) and scripts 294 KiB (55). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.17 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.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 9395
  • 58 images without alt text

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

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

  • 5 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 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 9281
  • Title is short (29 characters)

    Your title is only 29 characters: “Primo Feeds · Primo Feeds LLC”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (18 characters)

    Your meta description is only 18 characters: “Feeding Champions.”. 70 to 160 characters is enough to sell the click.

  • 21 H1 headlines

    There are 21 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 168 internal links, 5 external

    The homepage links to 168 pages on primofeeds.com and 5 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://primofeeds.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://primofeeds.com/sitemap.xml.

AI search readiness

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

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

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes /llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 13 pages share a meta description

    /pages/primo-feeds-awards-program, /collections/mid-west, /collections/show-feed-mid-west, /collections/sow-feed-mid-west, /collections/medicated-starters-mid-west and /collections/skin-hair and 7 others use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    /pages/primo-feeds-near-you and /pages/primo-mid-west-dealers-list have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 22 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: hcCountdownSettings is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://primofeeds.com/account.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (primofeeds.com).

  • Valid certificate (80 days left)

    The certificate from Let's Encrypt · YE1 verifies for primofeeds.com and is valid for another 80 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://primofeeds.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 44 links work

    All 44 links checked from your homepage (40 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    primofeeds.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

3 checks passed
  • Domain is 3 years old

    3 years

    primofeeds.com was registered in Jul 2023 through Wix.com Ltd.. An established domain carries more trust with email providers and search engines.

  • DNSSEC is on

    primofeeds.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.

  • Registered until Jul 2035

    primofeeds.com is registered until Jul 2035.

Content and conversion

3 to fix50
  • 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.

  • No social proof

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

  • No analytics detected

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

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

    The homepage carries about 684 words of visible text.

2 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Get Started”, “Shop all” and “Shop Mid West”.

  • 20 short forms

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

Email authentication

2 to fix35
  • No DMARC policy

    primofeeds.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 35/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

1 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com ~all”.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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).

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Geo Pro Geolocation · Tapcart Mobile App · Sales Discounts · Easylocation

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

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on primofeeds.com, including 7 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