Website review, no card needed

4rsmokehouse.com logo

4rsmokehouse.com website review

Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 81 checks

This review found 33 issues worth fixing on 4rsmokehouse.com, 15 of them high impact, across 81 checks. The most urgent: render-blocking 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.6 s1.5 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
157 ms118 msMay 2Oct 17152 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026124 ms
May 9, 2026123 ms
May 16, 2026122 ms
May 23, 2026122 ms
May 30, 2026122 ms
Jun 6, 2026122 ms
Jun 13, 2026122 ms
Jun 20, 2026125 ms
Jun 27, 2026127 ms
Jul 4, 2026129 ms
Jul 11, 2026131 ms
Jul 18, 2026133 ms
Jul 25, 2026135 ms
Aug 1, 2026135 ms
Aug 8, 2026137 ms
Aug 15, 2026141 ms
Aug 22, 2026145 ms
Aug 29, 2026145 ms
Sep 5, 2026145 ms
Sep 12, 2026144 ms
Sep 19, 2026145 ms
Sep 26, 2026147 ms
Oct 3, 2026149 ms
Oct 10, 2026151 ms
Oct 17, 2026152 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 4rsmokehouse.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 4rsmokehouse.com at 0.5 s0.5 s
  2. 4rsmokehouse.com at 1.0 s1.0 s
  3. 4rsmokehouse.com at 1.5 s1.5 s
  4. 4rsmokehouse.com at 1.9 s1.9 s
  5. 4rsmokehouse.com at 2.4 s2.4 s
  6. 4rsmokehouse.com at 2.9 s2.9 s
  7. 4rsmokehouse.com at 3.4 s3.4 s
  8. 4rsmokehouse.com at 3.9 s3.9 s

Speed

10 to fix28
  • Render-blocking requests

    4.8 s

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

  • Improve image delivery

    2.5 s · 1.6 MB

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

  • Use efficient cache lifetimes

    2.5 s · 477 KiB

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

  • Reduce unused JavaScript

    2.2 s · 403 KiB

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

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28 (desktop: 75). 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, Facebook and TikTok and others), adding 1.2 MB and 1.0 s of main-thread time.

  • Google Tag Manager adds 344 ms

    344 ms

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

    300 ms · 48 KiB

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

  • Facebook adds 287 ms

    287 ms

    Facebook costs a phone 287 ms of main-thread work and 259 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: 2.1 s

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 51 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 75 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

    4 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 22.2 s

    22.2 s

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

  • Time to Interactive: 22.5 s

    22.5 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Cumulative Layout Shift: 0.318

    0.318

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

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

    +23%

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

  • Total Blocking Time: 535 ms

    535 ms

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

6 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: 161 ms

    161 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 435 ms

    435 ms

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

Images and page weight

4 to fix25
  • Page weight: 4.0 MB in 113 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 113 requests on a phone: images 1.8 MB (25), scripts 1.3 MB (41) and fonts 731 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    4RGB-Holiday-Photos_00014-scaled.jpg weighs 930 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    755 KiB

    1 image is downloaded at several times the size a phone draws it, for example 4RGB-Holiday-Photos_00014-scaled.jpg at 2,560 px wide, shown at 370 px. Resized copies would save about 755 KiB.

  • 3 images in older formats

    3 images (1.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.

  • About 1.1 g of CO₂ per visit

    1.15 g

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

1 checks passed
  • Images load when needed

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

Accessibility

4 to fixGoogle 9794
  • 1 button without a name

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

  • 17 text elements with low contrast

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

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

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

  • 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 (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 2 links with vague text

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

  • 45 internal links, 20 external

    The homepage links to 45 pages on 4rsmokehouse.com and 20 external pages.

8 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “4 Rivers Smokehouse is an award-winning BBQ restaurant offering the best slow-smoked barbecue in Florida and Georgia, s…”.

  • One H1 headline

    Your main headline reads: “The Art of Smoking”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “4 Rivers Smokehouse | The Art of Smoking”.

  • Canonical URL set

    The canonical URL is https://www.4rsmokehouse.com/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and VideoObject.

  • 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.4rsmokehouse.com/sitemap_index.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://www.4rsmokehouse.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 (640 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages share a title

    https://www.4rsmokehouse.com/locations/coral-springs and https://www.4rsmokehouse.com/locations/middleton all use the title “#1 BBQ Coral Springs | 4 Rivers Smokehouse”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.4rsmokehouse.com/locations/coral-springs and https://www.4rsmokehouse.com/locations/middleton 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 38 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.

  • 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
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

  • About 606 words of copy

    The homepage carries about 606 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP” and “ORDER TAKEOUT & DELIVERY”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Order Online” and “LEARN MORE”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 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 TikTok Pixel (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • 20 other companies contacted

    Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 4rsmokehouse.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager

Company

Founded
2009

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 4rsmokehouse.com, including 17 speed issues, 1 SEO issue 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