Website review, no card needed

theminagroup.com logo

theminagroup.com website review

Visit site (opens in a new tab)Reviewed 19 November 202627 issues · 77 checks

This review found 27 issues worth fixing on theminagroup.com, 9 of them high impact, across 77 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.2 s964 msMay 30Nov 14990 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Nov 14, 2026990 ms
Real-visitor tap response (INP)75th percentile, phones
97 ms87 msMay 30Nov 1493 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202693 ms
Jun 6, 202694 ms
Jun 13, 202695 ms
Jun 20, 202694 ms
Jun 27, 202693 ms
Jul 4, 202694 ms
Jul 11, 202691 ms
Jul 18, 202691 ms
Jul 25, 202691 ms
Aug 1, 202692 ms
Aug 8, 202692 ms
Aug 15, 202692 ms
Aug 22, 202689 ms
Aug 29, 202688 ms
Sep 5, 202690 ms
Sep 12, 202692 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 202694 ms
Oct 10, 202693 ms
Oct 17, 202695 ms
Oct 24, 202695 ms
Oct 31, 202696 ms
Nov 7, 202695 ms
Nov 14, 202693 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 theminagroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix65
  • Render-blocking requests

    3.0 s

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

  • Improve image delivery

    8.2 MB

    12 images could be 8.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 65

    65/100

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

  • Use efficient cache lifetimes

    750 ms · 111 KiB

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

  • Reduce unused JavaScript

    600 ms · 105 KiB

    About 105 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 173 KiB

    About 173 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (termly.io, Google CDN and FontAwesome CDN and others), adding 597 KiB and 108 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 30.3 s

    30.3 s

    Your largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Explore our restaurants”.

  • Time to Interactive: 32.8 s

    32.8 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

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

    2.1 s

    Real visitors wait 2.1 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.6 s

    1.6 s

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

  • Real-user TTFB: 696 ms

    696 ms

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

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

    -10%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 16 ms

    16 ms

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

Images and page weight

5 to fix18
  • Page weight: 10.2 MB in 59 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 59 requests on a phone: images 9.4 MB (21), scripts 493 KiB (14) and fonts 117 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 10 images over 500 KB

    10 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    5.0 MB

    11 images are downloaded at several times the size a phone draws them, for example restaurants-05.jpg at 1,920 px wide, shown at 358 px. Resized copies would save about 5.0 MB.

  • 14 images in older formats

    14 images (9.4 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.

  • 10 images below the first screen load straight away

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

  • About 2.9 g of CO₂ per visit

    2.88 g

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

Accessibility

2 to fixGoogle 10097
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 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
  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 22 internal links, 3 external

    The homepage links to 22 pages on theminagroup.com and 3 external pages.

8 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Discover award-winning restaurants by Chef Michael Mina, offering exceptional cuisine and world-class hospitality.”.

  • One H1 headline

    Your main headline reads: “ABOUT MINA GROUP”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “The MINA Group | Chef Michael Mina”.

  • Canonical URL set

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

  • Structured data in place

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

  • XML sitemap found

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

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://theminagroup.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 (318 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 4 pages without a meta description

    https://theminagroup.com/happenings, https://theminagroup.com/happenings/bar-sprezzatura-opens-in-portland, https://theminagroup.com/happenings/ayesha-curry-brings-sweet-july-cafe-home-to-charlotte and https://theminagroup.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

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

  • 3 pages without an H1

    https://theminagroup.com/ambassador, https://theminagroup.com/happenings/bar-sprezzatura-opens-in-portland and https://theminagroup.com/happenings/ayesha-curry-brings-sweet-july-cafe-home-to-charlotte have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://theminagroup.com/careers and https://theminagroup.com/contact 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
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • 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 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 5 small tap targets

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

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

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

  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. 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 365 words of copy

    The homepage carries about 365 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn more”, “Book now” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 theminagroup.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
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on theminagroup.com, including 11 speed issues, 1 SEO issue 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