Website review, no card needed

uacfoodsng.com logo

uacfoodsng.com website review

Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 81 checks

This review found 36 issues worth fixing on uacfoodsng.com, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
5.9 s5.0 sMay 30Nov 145.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.7 s
Jun 6, 20265.4 s
Jun 13, 20265.3 s
Jun 20, 20265.3 s
Jun 27, 20265.3 s
Jul 4, 20265.5 s
Jul 11, 20265.3 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.3 s
Aug 8, 20265.4 s
Aug 15, 20265.7 s
Aug 22, 20265.8 s
Aug 29, 20265.8 s
Sep 5, 20265.6 s
Sep 12, 20265.4 s
Sep 19, 20265.4 s
Sep 26, 20265.2 s
Oct 3, 20265.5 s
Oct 10, 20265.2 s
Oct 17, 20265.1 s
Oct 24, 20265.1 s
Oct 31, 20265.2 s
Nov 7, 20265.4 s
Nov 14, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
205 ms146 msMay 30Nov 14160 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026170 ms
Jun 6, 2026161 ms
Jun 13, 2026165 ms
Jun 20, 2026179 ms
Jun 27, 2026176 ms
Jul 4, 2026198 ms
Jul 11, 2026186 ms
Jul 18, 2026174 ms
Jul 25, 2026169 ms
Aug 1, 2026174 ms
Aug 8, 2026170 ms
Aug 15, 2026159 ms
Aug 22, 2026154 ms
Aug 29, 2026153 ms
Sep 5, 2026159 ms
Sep 12, 2026170 ms
Sep 19, 2026178 ms
Sep 26, 2026179 ms
Oct 3, 2026176 ms
Oct 10, 2026180 ms
Oct 17, 2026168 ms
Oct 24, 2026165 ms
Oct 31, 2026177 ms
Nov 7, 2026168 ms
Nov 14, 2026160 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 uacfoodsng.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uacfoodsng.com at 1.5 s1.5 s
  2. uacfoodsng.com at 3.0 s3.0 s
  3. uacfoodsng.com at 4.4 s4.4 s
  4. uacfoodsng.com at 5.9 s5.9 s
  5. uacfoodsng.com at 7.4 s7.4 s
  6. uacfoodsng.com at 8.9 s8.9 s
  7. uacfoodsng.com at 10.4 s10.4 s
  8. uacfoodsng.com at 11.8 s11.8 s

Speed

7 to fix62
  • Reduce unused JavaScript

    1.6 s · 235 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Use efficient cache lifetimes

    350 ms · 11.8 MB

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

  • Improve image delivery

    1.0 MB

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    320 ms · 11 KiB

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

  • Main-thread work: 2.5 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Unpkg and others), adding 200 KiB and 213 ms of main-thread time.

  • Legacy JavaScript

    200 ms · 30 KiB

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

  • Minify CSS

    160 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

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

    2 ms

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

Core Web Vitals

8 to fix67
  • 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 LCP: 6.2 s

    6.2 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 34.4 s

    34.4 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1 of 4”. Most of its time is resource load delay (7.5 s).

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 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 170 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

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

4 checks passed
  • Real-user INP: 192 ms

    192 ms

    Real visitors wait 192 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.

  • Total Blocking Time: 104 ms

    104 ms

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

  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

1 to fix33
  • Page weight: 12.7 MB in 83 requests

    12.7 MB

    Your homepage downloads 12.7 MB in 83 requests on a phone: images 11.9 MB (51), scripts 609 KiB (20) and fonts 90 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 3.6 g of CO₂ per visit

    3.59 g

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

Accessibility

6 to fixGoogle 8991
  • 8 text elements with low contrast

    8 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 (15 elements)

    All page content should be contained by landmarks: 15 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.

  • 7 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

6 to fixGoogle 9078
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Our Latest Company Updates” and “Follow us on social media”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • No XML sitemap

    No XML sitemap at https://uacfoodsng.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at uacfoodsng.com/robots.txt, the first file search crawlers ask for.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 59 internal links, 3 external

    The homepage links to 59 pages on uacfoodsng.com and 3 external pages.

3 checks passed
  • Meta description: 100 characters

    Your meta description is 100 characters: “UAC Foods Limited is a leading manufacturer and marketer of tasty, nourishing convenience foods. ...”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “UAC Foods | Creating Valuable Foods For Life.”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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://uacfoodsng.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading 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 fix88
  • 4 pages share 2 titles

    https://uacfoodsng.com/news-and-events/uac-foods-marks-international-day-of-the-girl-child-with-leadership-and-mentorship-engagement and https://uacfoodsng.com/news-and-events/supreme-ice-cream-brings-joy-to-children-s-day-with-supreme-kids-fiesta all use the title “Event | UAC Foods”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without an H1

    https://uacfoodsng.com/about, https://uacfoodsng.com/management, https://uacfoodsng.com/contact, https://uacfoodsng.com/store-location, https://uacfoodsng.com/careers and https://uacfoodsng.com/brands/funtime-chips have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://uacfoodsng.com/management, https://uacfoodsng.com/brands/funtime-snacks, https://uacfoodsng.com/news-and-events, https://uacfoodsng.com/contact, https://uacfoodsng.com/store-location and https://uacfoodsng.com/careers 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.

  • 4 pages slow to respond

    https://uacfoodsng.com/brands/swan-spring-water, https://uacfoodsng.com/brands/funtime-snacks, https://uacfoodsng.com/news-and-events and https://uacfoodsng.com/contact took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 9693
  • 12 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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 fix71
  • No social proof

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

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 616 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “Shop Now”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “Shop Now”.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 uacfoodsng.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
Webflow
Framework
Nuxt
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on uacfoodsng.com, including 15 speed issues, 6 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