Website review, no card needed

epicsales.com logo

epicsales.com website review

Visit site (opens in a new tab)Reviewed 25 October 202633 issues · 71 checks

This review found 33 issues worth fixing on epicsales.com, 13 of them high impact, across 71 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

Full-page screenshot of epicsales.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. epicsales.com at 0.6 s0.6 s
  2. epicsales.com at 1.3 s1.3 s
  3. epicsales.com at 1.9 s1.9 s
  4. epicsales.com at 2.5 s2.5 s
  5. epicsales.com at 3.2 s3.2 s
  6. epicsales.com at 3.8 s3.8 s
  7. epicsales.com at 4.4 s4.4 s
  8. epicsales.com at 5.0 s5.0 s

Speed

12 to fix39
  • Reduce unused JavaScript

    7.5 s · 1.2 MB

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

  • Render-blocking requests

    3.8 s

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

  • Use efficient cache lifetimes

    2.2 s · 1.0 MB

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

  • Mobile performance score: 39

    39/100

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

  • Improve image delivery

    150 ms · 4.1 MB

    38 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, hsappstatic.net and Google Tag Manager and others), adding 2.7 MB and 1.6 s of main-thread time.

  • Reduce unused CSS

    970 ms · 189 KiB

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

  • Google CDN adds 554 ms

    554 ms

    Google CDN costs a phone 554 ms of main-thread work and 1.1 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.

  • hsappstatic.net adds 408 ms

    408 ms

    hsappstatic.net costs a phone 408 ms of main-thread work and 703 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 Tag Manager adds 381 ms

    381 ms

    Google Tag Manager costs a phone 381 ms of main-thread work and 624 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.9 s

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

  • 16 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • Font display

    150 ms

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

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

    7 ms

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

Core Web Vitals

7 to fix48
  • First Contentful Paint: 15.5 s

    15.5 s

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

  • Largest Contentful Paint: 26.6 s

    26.6 s

    Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “America's Premier Fresh Food Sales Agency Connecting food m…”.

  • Speed Index: 15.5 s

    15.5 s

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

  • Time to Interactive: 30.8 s

    30.8 s

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

  • 60 images without width and height

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

  • Cumulative Layout Shift: 0.169

    0.169

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

  • Total Blocking Time: 350 ms

    350 ms

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

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

Images and page weight

1 to fix0
  • Page weight: 9.5 MB in 183 requests

    9.5 MB

    Your homepage downloads 9.5 MB in 183 requests on a phone: images 5.3 MB (77), scripts 2.7 MB (41) and fonts 777 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • About 2.7 g of CO₂ per visit

    2.70 g

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

Accessibility

5 to fix80
  • [role]s do not have all required [aria-*] attributes

    [role]s do not have all required [aria-*] attributes (3 elements).

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

SEO

2 to fixGoogle 10093
  • 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, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 88 internal links, 4 external

    The homepage links to 88 pages on epicsales.com and 4 external pages.

6 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Epic Sales Partners lead sales to multiple food industry channels, giving fresh food manufacturers a consistent path to…”.

  • One H1 headline

    Your main headline reads: “America's Premier Fresh Food Sales Agency”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Epic Sales Partners: Fresh Food Catalysts”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

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

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 6984
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 console errors

    3 errors were logged to the browser console during Google's test (“requestStorageAccess: Permission denied.”).

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • 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

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

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

    The homepage carries about 631 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Schedule a Call” and “Download Now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

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

Upkeep, stack and company

Stack

CMS
HubSpot CMS
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on epicsales.com, including 19 speed issues, 2 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