Website review, no card needed

cabofishtaco.com logo

cabofishtaco.com website review

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

This review found 33 issues worth fixing on cabofishtaco.com, 12 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
4.0 s2.4 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.6 s
May 9, 20262.6 s
May 16, 20262.6 s
May 23, 20262.9 s
May 30, 20263.3 s
Jun 6, 20263.5 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.8 s
Jul 18, 20263.8 s
Jul 25, 20263.5 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.7 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
88 ms78 msMay 2Oct 1786 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202687 ms
May 9, 202686 ms
May 16, 202681 ms
May 23, 202679 ms
May 30, 202680 ms
Jun 6, 202679 ms
Jun 13, 202685 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202686 ms
Jul 18, 202685 ms
Jul 25, 202683 ms
Aug 1, 202681 ms
Aug 8, 202686 ms
Aug 15, 202685 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202685 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202685 ms
Oct 3, 202685 ms
Oct 10, 202685 ms
Oct 17, 202686 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 cabofishtaco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cabofishtaco.com at 0.9 s0.9 s
  2. cabofishtaco.com at 1.7 s1.7 s
  3. cabofishtaco.com at 2.6 s2.6 s
  4. cabofishtaco.com at 3.4 s3.4 s
  5. cabofishtaco.com at 4.3 s4.3 s
  6. cabofishtaco.com at 5.1 s5.1 s
  7. cabofishtaco.com at 6.0 s6.0 s
  8. cabofishtaco.com at 6.8 s6.8 s

Speed

7 to fix61
  • Use efficient cache lifetimes

    6.5 s · 1.3 MB

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

  • Render-blocking requests

    2.3 s

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

  • Improve image delivery

    1.8 s · 438 KiB

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

  • Reduce unused JavaScript

    1.6 s · 325 KiB

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

  • Reduce unused CSS

    1.2 s · 257 KiB

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

  • Mobile performance score: 61

    61/100

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

  • Font display

    350 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and cdnfonts.com), adding 90 KiB and 28 ms of main-thread time.

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    10 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.6 s

    17.6 s

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

  • Time to Interactive: 17.6 s

    17.6 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Largest content (LCP) got 24% slower for real visitors

    +24%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 86 ms 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: 2.0 s

    2.0 s

    Real visitors wait 2.0 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.01

    0.01

    For real visitors the layout shifts by 0.01 (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: 532 ms

    532 ms

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

  • Cumulative Layout Shift: 0.054

    0.054

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 40 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 40 requests on a phone: images 2.3 MB (9), scripts 484 KiB (13) and fonts 347 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • About 1.0 g of CO₂ per visit

    0.98 g

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

2 checks passed
  • 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

7 to fixGoogle 9190
  • 10 text elements with low contrast

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

  • 4 images without alt text

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

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

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

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

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

  • 14 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 39 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: 39 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10086
  • No H1 headline

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

  • No XML sitemap

    No XML sitemap at https://www.cabofishtaco.com/sitemap.xml, so Google discovers your pages only by following links.

  • 37 internal links, 22 external

    The homepage links to 37 pages on cabofishtaco.com and 22 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Serving Curbside Pickup and Delivery Baja Mexican Food to our amigos in Blacksburg, Charlotte and Roanoke. Keeping you …”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Cabo Fish Taco - Baja Seagrill | Cabo Fish Taco”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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.

AI search readiness

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

  • Organization data: 4 of 6 facts

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

  • llms.txt published

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

Other pages

6 to fix52
  • 4 linked pages are broken

    Your homepage links to https://www.cabofishtaco.com/blacksburg, //employment, https://www.cabofishtaco.com/cookie-policy and https://www.cabofishtaco.com/catering, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.cabofishtaco.com/ballantyne-2 and //ballantyne all use the title “Ballantyne Mexican Seagrill - Charlotte NC | Cabo Fish Taco”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.cabofishtaco.com/franchising, https://www.cabofishtaco.com/privacy, https://www.cabofishtaco.com/about, https://www.cabofishtaco.com/locations and https://www.cabofishtaco.com/connect have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.cabofishtaco.com/ballantyne-2 and //ballantyne use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example //ballantyne, whose canonical is https://www.cabofishtaco.com/ballantyne-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.cabofishtaco.com/app, https://www.cabofishtaco.com/privacy, https://www.cabofishtaco.com/locations and https://www.cabofishtaco.com/connect have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.cabofishtaco.com/locations has 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.

  • 9 pages slow to respond

    https://www.cabofishtaco.com/ballantyne-2, https://www.cabofishtaco.com/charlotte, https://www.cabofishtaco.com/cabofoodtruck, https://www.cabofishtaco.com/app, https://www.cabofishtaco.com/franchising and https://www.cabofishtaco.com/privacy and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “grecaptcha is not defined”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    26 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 133 words

    The homepage has only about 133 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Download App” and “Order Online choose location”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Order Online”, “Download App” and “Order Onlinechoose location”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 cabofishtaco.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
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 cabofishtaco.com, including 12 speed issues, 2 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