ucook.co.za website review

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

Your mobile performance score is 40 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, posthog.com and Facebook and others), adding 1.7 MB and 1.8 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 941 ms on a phone.

9 images could be 538 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Google Tag Manager costs a phone 561 ms of main-thread work and 554 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.

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

posthog.com costs a phone 428 ms of main-thread work and 251 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.

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

Facebook costs a phone 255 ms of main-thread work and 229 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.

The page has 1,717 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

nudjly.com costs a phone 75 ms of main-thread work and 342 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.

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

219 KiB could be saved by minifying JavaScript.

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

21 KiB JavaScript is shipped twice across bundles.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

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 visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UCOOK”. Most of its time is resource load delay (4.6 s).

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

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

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

Your homepage downloads 4.6 MB in 157 requests on a phone: scripts 2.8 MB (59), images 1.4 MB (37) and fonts 237 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 21 pages on ucook.co.za and 9 external pages.

A phone browser shows 486 words, but the HTML your server sends has only 78. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://www.ucook.co.za/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.

https://www.ucook.co.za/cms/gifts, https://www.ucook.co.za/cms/deals, https://www.ucook.co.za/cms/about-ucook, https://www.ucook.co.za/cms/ucook-store-cavendish, https://www.ucook.co.za/cms/recycle and https://www.ucook.co.za/cms/partnerships all use the title “UCOOK | Meal Kits & Meal Delivery Service South Africa | UCOOK”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ucook.co.za/cms/gifts, https://www.ucook.co.za/cms/deals, https://www.ucook.co.za/cms/about-ucook, https://www.ucook.co.za/cms/ucook-store-cavendish, https://www.ucook.co.za/cms/recycle and https://www.ucook.co.za/cms/partnerships use the same meta description. A description written for each page earns more clicks.

https://www.ucook.co.za/meal-kit, https://www.ucook.co.za/frozen, https://www.ucook.co.za/wine, https://www.ucook.co.za/support, https://www.ucook.co.za/terms and https://www.ucook.co.za/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ucook.co.za/market, https://www.ucook.co.za/market/store/weekend-meal-kits, https://www.ucook.co.za/cms/deals, https://www.ucook.co.za/wine and https://www.ucook.co.za/cms/partnerships 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.

https://www.ucook.co.za/market, https://www.ucook.co.za/market/store/weekend-meal-kits, https://www.ucook.co.za/cms/gifts and https://www.ucook.co.za/cms/deals took over 3 s to send their HTML from our server.

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

Large scripts ship without source maps.

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

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

The homepage carries about 486 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, Meta Pixel and Microsoft Clarity and 1 more (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.

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

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.

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