Website review, no card needed

threejerksjerky.com logo

threejerksjerky.com website review

Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 70 checks

This review found 32 issues worth fixing on threejerksjerky.com, 10 of them high impact, across 70 checks. The most urgent: avoid multiple page redirects. 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 threejerksjerky.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix67
  • Avoid multiple page redirects

    2.6 s

    The page goes through 1 redirect before it starts loading, costing about 2.6 s. Link and advertise the final URL directly.

  • Render-blocking requests

    1.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, ShareThis and Hotjar and others), adding 1.1 MB and 943 ms of main-thread time.

  • Mobile performance score: 67

    67/100

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

  • Use efficient cache lifetimes

    550 ms · 342 KiB

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

  • Reduce unused JavaScript

    757 KiB

    About 757 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 390 ms

    390 ms

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

  • Reduce unused CSS

    400 ms · 28 KiB

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

  • Main-thread work: 2.4 s

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

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 25 KiB

    25 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

    19 KiB

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

  • Improve image delivery

    11 KiB

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

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

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

5 to fix79
  • Time to Interactive: 21.2 s

    21.2 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Thanks for trusting us jerks over the years. We appreciate …”. Most of its time is element render delay (2.4 s).

  • Total Blocking Time: 220 ms

    220 ms

    Scripts block taps and scrolling for 220 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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 306 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 306 requests on a phone: scripts 1.5 MB (99), images 844 KiB (35) and other files 834 KiB (144). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.95 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 9391
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 25 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (17 characters)

    Your title is only 17 characters: “Three Jerks Jerky”. 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.

  • One H1 headline

    Your <h1> is empty.

  • 31 internal links, 16 external

    The homepage links to 31 pages on threejerksjerky.com and 16 external pages.

5 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Only the finest filet mignon is used when making Three Jerks Jerky. We carefully and lovingly jerkify our fine meats wi…”.

  • Canonical URL set

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

  • 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://www.threejerksjerky.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.

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.

  • llms.txt published

    The site publishes https://www.threejerksjerky.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 9 linked pages are broken

    Your homepage links to https://www.threejerksjerky.com/pages/about-us, https://www.threejerksjerky.com/pages/faq-1, https://www.threejerksjerky.com/pages/contact, https://www.threejerksjerky.com/products/chipotle-adobo-filet-mignon-beef-jerky, https://www.threejerksjerky.com/products/memphis-bbq-filet-mignon-beef-jerky and https://www.threejerksjerky.com/products/original-filet-mignon-beef-jerky and 3 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages without a meta description

    https://www.threejerksjerky.com/collections/all-products, https://www.threejerksjerky.com/blogs/news and https://www.threejerksjerky.com/collections/shop-jerky have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.threejerksjerky.com/collections/all-products, https://www.threejerksjerky.com/blogs/news and https://www.threejerksjerky.com/collections/shop-jerky have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.threejerksjerky.com/collections/all-products and https://www.threejerksjerky.com/collections/shop-jerky have 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5489
  • 3 third-party cookies

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.threejerksjerky.com/cdn/shop/t/68/assets/klaviyo.css?v=33824' because its MIME…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • 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.

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

  • Only about 24 words

    The homepage has only about 24 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

3 checks passed
  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop”, “Contact” and “Buy now”.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 of them by other companies (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.

  • 35 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on threejerksjerky.com, including 14 speed issues, 3 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