Website review, no card needed

tumbleweedrestaurants.com logo

tumbleweedrestaurants.com website review

Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 87 checks

This review found 32 issues worth fixing on tumbleweedrestaurants.com, 13 of them high impact, across 87 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.4 sSep 5Oct 241.4 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
86 ms83 msSep 5Oct 2484 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202686 ms
Sep 12, 202685 ms
Sep 19, 202685 ms
Sep 26, 202684 ms
Oct 3, 202683 ms
Oct 10, 202685 ms
Oct 17, 202684 ms
Oct 24, 202684 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 tumbleweedrestaurants.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix52
  • Reduce unused JavaScript

    3.9 s · 883 KiB

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

  • Render-blocking requests

    2.7 s

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

  • Improve image delivery

    1.9 s · 826 KiB

    9 images could be 826 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Reduce unused CSS

    1.1 s · 247 KiB

    About 247 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and PayPal and others), adding 1.7 MB and 1.1 s of main-thread time.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • YouTube adds 613 ms

    613 ms

    YouTube costs a phone 613 ms of main-thread work and 989 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.

  • Use efficient cache lifetimes

    600 ms · 103 KiB

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

  • Google Tag Manager adds 328 ms

    328 ms

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

  • 10 long tasks on the main thread

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

  • Main-thread work: 2.8 s

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

  • Font display

    150 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 93 but mobile only 52. 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 13.3 s

    13.3 s

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

  • Largest Contentful Paint: 20.5 s

    20.5 s

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

  • Time to Interactive: 21.7 s

    21.7 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • Total Blocking Time: 209 ms

    209 ms

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

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

    1.7 s

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

  • Real-user INP: 70 ms

    70 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 773 ms

    773 ms

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

  • 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.6 MB in 125 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 125 requests on a phone: scripts 1.7 MB (44), images 1.3 MB (16) and stylesheets 287 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.01 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.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 8994
  • 7 tap targets too small

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

  • 2 text elements with low contrast

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

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

  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10078
  • No H1 headline

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

  • Title is long (144 characters)

    Your title is 144 characters, so Google will cut it off around 60: “Authentic Mexican Food & Margarita Restaurant, Mesquite Grilled Steaks, Weekend Dining, T…”.

  • Meta description is long (178 characters)

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

  • 46 internal links, 9 external

    The homepage links to 46 pages on tumbleweedrestaurants.com and 9 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, Restaurant and WebPage.

  • 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.tumbleweedrestaurants.com/sitemap_index.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.tumbleweedrestaurants.com/gift-cards, https://www.tumbleweedrestaurants.com/franchise and https://www.tumbleweedrestaurants.com/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.tumbleweedrestaurants.com/team, https://www.tumbleweedrestaurants.com/history, https://www.tumbleweedrestaurants.com/weekly-lunch-specials and https://www.tumbleweedrestaurants.com/franchise have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.tumbleweedrestaurants.com/team, https://www.tumbleweedrestaurants.com/contact, https://www.tumbleweedrestaurants.com/weekly-lunch-specials, https://www.tumbleweedrestaurants.com/retail, https://www.tumbleweedrestaurants.com/gift-cards and https://www.tumbleweedrestaurants.com/sitemap 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.

  • 13 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 2 broken images

    2 images failed to load on a phone, for example https://tumbleweed1.wpengine.com/wp-content/uploads/2021/09/logo1-1-300x55.png.

  • 5 third-party cookies

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

  • 2 small tap targets

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

  • Browser-reported issues

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

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

    The homepage carries about 252 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER ONLINE”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Contact”, “Order Online” and “ORDER ONLINE”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 13 cookies set on arrival

    13

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 tumbleweedrestaurants.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 Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

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