Website review, no card needed

foodiebrands.com logo

foodiebrands.com website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 81 checks

This review found 28 issues worth fixing on foodiebrands.com, 8 of them high impact, across 81 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
4.1 s2.2 sSep 12Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
Sep 12, 20262.5 s
Sep 26, 20263.4 s
Oct 3, 20263.6 s
Oct 10, 20263.9 s
Oct 17, 20263.3 s
Oct 24, 20262.7 s
Oct 31, 20263.2 s

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 foodiebrands.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. foodiebrands.com at 1.0 s1.0 s
  2. foodiebrands.com at 1.9 s1.9 s
  3. foodiebrands.com at 2.9 s2.9 s
  4. foodiebrands.com at 3.9 s3.9 s
  5. foodiebrands.com at 4.9 s4.9 s
  6. foodiebrands.com at 5.8 s5.8 s
  7. foodiebrands.com at 6.8 s6.8 s
  8. foodiebrands.com at 7.8 s7.8 s

Speed

4 to fix85
  • Render-blocking requests

    4.2 s

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

  • Mobile performance score: 85

    85/100

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

  • Reduce unused CSS

    450 ms · 86 KiB

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

  • Main-thread work: 2.2 s

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

  • 5 long tasks on the main thread

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

  • Reduce unused JavaScript

    88 KiB

    About 88 KiB of JavaScript is downloaded but never used on this page.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cloudflare CDN), adding 20 KiB and 19 ms of main-thread time.

  • Improve image delivery

    20 KiB

    1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 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.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

8 to fix50
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.8 s

    2.8 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

    Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Unleash Culinary Excellence With Dish Catering Company of t…”. Most of its time is resource load delay (1.3 s).

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Time to Interactive: 3.9 s

    3.9 s

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.7 MB in 66 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 66 requests on a phone: media 4.8 MB (3), scripts 273 KiB (14) and images 222 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.61 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.4 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

7 to fixGoogle 7990
  • 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.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (7 elements)

    Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

4 to fixGoogle 7789
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://dish.ae/sitemap_index.xml, so Google discovers your pages only by following links.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 42 internal links, 4 external

    The homepage links to 42 pages on foodiebrands.com and 4 external pages.

6 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Award-winning luxury catering in Dubai & Abu Dhabi. Bespoke menus for corporate events, gala dinners & private occasion…”.

  • One H1 headline

    Your main headline reads: “Unleash Culinary Excellence With Dish”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Luxury Catering in Dubai & Abu Dhabi | Dish Catering UAE”.

  • Canonical URL set

    The canonical URL is https://dish.ae/.

  • Structured data in place

    Structured data found: ImageObject, Organization, Person, Service and WebPage.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

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

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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 7 pages slow to respond

    https://dish.ae/about-us, https://dish.ae/blogs, https://dish.ae/blogs/corporate-catering-workplace-culture-dubai-uae, https://dish.ae/blogs/private-dining-in-dubai, https://dish.ae/festive-catering and https://dish.ae/corporate-catering and 1 other took over 3 s to send their HTML from our server.

  • 14 internal pages checked

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

7 checks passed
  • Linked pages load

    10 pages of 14 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

1 to fixGoogle 9292
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 2 low-resolution images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

    The homepage carries about 644 words of visible text.

6 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “ENQUIRE NOW” and “Enquire now”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 38 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Matomo.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 foodiebrands.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

Company

Headquarters
Dubai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on foodiebrands.com, including 12 speed issues, 4 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