Website review, no card needed

senorfrogs.com logo

senorfrogs.com website review

Visit site (opens in a new tab)Reviewed 26 October 202629 issues · 84 checks

This review found 29 issues worth fixing on senorfrogs.com, 11 of them high impact, across 84 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
3.1 s1.5 sMay 9Oct 241.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.5 s
Aug 22, 20262.1 s
Aug 29, 20261.8 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
143 ms108 msMay 9Oct 24133 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026112 ms
May 30, 2026113 ms
Jun 6, 2026114 ms
Jun 13, 2026116 ms
Jun 20, 2026118 ms
Jun 27, 2026120 ms
Jul 4, 2026119 ms
Jul 11, 2026119 ms
Jul 18, 2026120 ms
Jul 25, 2026120 ms
Aug 1, 2026121 ms
Aug 8, 2026123 ms
Aug 15, 2026129 ms
Aug 22, 2026135 ms
Aug 29, 2026139 ms
Sep 5, 2026137 ms
Sep 12, 2026138 ms
Sep 19, 2026137 ms
Sep 26, 2026132 ms
Oct 3, 2026132 ms
Oct 10, 2026129 ms
Oct 17, 2026131 ms
Oct 24, 2026133 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 senorfrogs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. senorfrogs.com at 0.6 s0.6 s
  2. senorfrogs.com at 1.3 s1.3 s
  3. senorfrogs.com at 1.9 s1.9 s
  4. senorfrogs.com at 2.6 s2.6 s
  5. senorfrogs.com at 3.2 s3.2 s
  6. senorfrogs.com at 3.8 s3.8 s
  7. senorfrogs.com at 4.5 s4.5 s
  8. senorfrogs.com at 5.1 s5.1 s

Speed

7 to fix52
  • Use efficient cache lifetimes

    6.7 s · 13.2 MB

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

  • Improve image delivery

    1.2 s · 2.3 MB

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

  • Reduce unused JavaScript

    2.6 s · 507 KiB

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

  • Mobile performance score: 52

    52/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Facebook and others), adding 1.0 MB and 864 ms of main-thread time.

  • Google Tag Manager adds 275 ms

    275 ms

    Google Tag Manager costs a phone 275 ms of main-thread work and 363 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.6 s

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

  • Legacy JavaScript

    150 ms · 31 KiB

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

    64 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 21.7 s

    21.7 s

    Your largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Señor Frog’s Mexican Food logo”.

  • Speed Index: 14.1 s

    14.1 s

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

  • Time to Interactive: 22.2 s

    22.2 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • 43 images without width and height

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

  • Total Blocking Time: 217 ms

    217 ms

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

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

    +18%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 133 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: 153 ms

    153 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 397 ms

    397 ms

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

  • Largest content (LCP) got 37% faster for real visitors

    -37%

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

  • Cumulative Layout Shift: 0.04

    0.04

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

Images and page weight

5 to fix18
  • Page weight: 14.0 MB in 104 requests

    14.0 MB

    Your homepage downloads 14.0 MB in 104 requests on a phone: media 8.0 MB (1), images 4.4 MB (51) and scripts 1.1 MB (21). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    senor-frogs-locations-around-the-world-2.jpg weighs 553 KiB. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    1,015 KiB

    9 images are downloaded at several times the size a phone draws them, for example senor-frogs-locations-around-the-world-2.jpg at 2,000 px wide, shown at 340 px. Resized copies would save about 1,015 KiB.

  • 9 images below the first screen load straight away

    9 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (629 KiB) 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 4.0 g of CO₂ per visit

    3.97 g

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

Accessibility

3 to fixGoogle 9596
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 3 links without text

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

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

2 checks passed
  • Every image has alt text

    All 84 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 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
  • 3 links with vague text

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

  • 73 internal links, 35 external

    The homepage links to 73 pages on senorfrogs.com and 35 external pages.

8 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Welcome to Señor Frog’s, where the party never ends! Mexican restaurant & bar across Mexico, USA & the Caribbean. New d…”.

  • One H1 headline

    Your main headline reads: “Come for the food stay for the fun”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Señor Frog’s, Mexican Restaurant & Fiesta | Grupo Anderson's”.

  • Canonical URL set

    The canonical URL is https://senorfrogs.com/.

  • Structured data in place

    Structured data found: Restaurant 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.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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://senorfrogs.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 (765 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 4 pages share 2 titles

    https://senorfrogs.com/menu-cozumel-international-ssa and https://senorfrogs.com/menu-cozumel-punta-langosta all use the title “Menu Cozumel | Señor Frog’s”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages share a meta description

    https://senorfrogs.com/menu-cozumel-international-ssa and https://senorfrogs.com/menu-cozumel-punta-langosta 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 39 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

1 to fixGoogle 10093
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

    61 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 633 words of copy

    The homepage carries about 633 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP MX” and “BOOK”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop MX”, “Order” and “Book”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

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

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 senorfrogs.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on senorfrogs.com, including 13 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