redmangousa.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, Google Tag Manager and Google Analytics and others), adding 702 KiB and 209 ms of main-thread time.

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.0 MB in 54 requests on a phone: images 1.8 MB (8), scripts 641 KiB (19) and fonts 359 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

No meta description, so Google writes its own snippet from whatever text it finds.

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

Google's crawler is blocked from indexing this page.

Your title is 176 characters, so Google will cut it off around 60: “Red Mango | Red Mango is committed to providing the healthiest and best tasting all-natur…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 20 pages on redmangousa.com and 2 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

There is no https://redmangousa.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://redmangousa.com/menu, https://redmangousa.com/frozen-yogurt, https://redmangousa.com/nutrition, https://redmangousa.com/club-mango-rewards, https://redmangousa.com/gift-cards and https://redmangousa.com/red-mango-better-for-you-franchise and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://redmangousa.com/menu and https://redmangousa.com/frozen-yogurt all use the title “Our Menu | Red Mango”. Search engines can't tell which page to show for a search, so each competes with the others.

https://redmangousa.com/menu, https://redmangousa.com/frozen-yogurt, https://redmangousa.com/nutrition, https://redmangousa.com/club-mango-rewards, https://redmangousa.com/gift-cards and https://redmangousa.com/red-mango-better-for-you-franchise and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://redmangousa.com/menu, https://redmangousa.com/frozen-yogurt, https://redmangousa.com/gift-cards, https://redmangousa.com/red-mango-better-for-you-franchise, https://redmangousa.com/about and https://redmangousa.com/news and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://redmangousa.com/.

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

3 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://sitemedia.blob.core.windows.net/redmango/2019/03/site.webmanifest' from origin 'https://…”.

3 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 133 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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