Website review, no card needed

unitedbiscuits.com logo

unitedbiscuits.com website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 79 checks

This review found 32 issues worth fixing on unitedbiscuits.com, 10 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
2.0 s1.5 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.8 s
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
92 ms82 msMay 2Oct 1784 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202687 ms
May 9, 202687 ms
May 16, 202685 ms
May 23, 202686 ms
May 30, 202685 ms
Jun 6, 202683 ms
Jun 13, 202686 ms
Jun 20, 202686 ms
Jun 27, 202687 ms
Jul 4, 202689 ms
Jul 11, 202689 ms
Jul 18, 202691 ms
Jul 25, 202691 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202687 ms
Aug 29, 202688 ms
Sep 5, 202686 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202685 ms
Oct 3, 202685 ms
Oct 10, 202685 ms
Oct 17, 202684 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 unitedbiscuits.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix64
  • Use efficient cache lifetimes

    1.4 s · 1.1 MB

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

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cookiebot and Amazon Web Services), adding 1.1 MB and 151 ms of main-thread time.

  • 1,555 HTML elements

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

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 941 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.

  • Reduce unused CSS

    150 ms · 67 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 109 ms. During a long task the page ignores taps.

  • Improve image delivery

    95 KiB

    11 images could be 95 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    27 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 94 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • Time to Interactive: 9.1 s

    9.1 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 970 ms

    970 ms

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -3%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 59 ms

    59 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.svg at 235 px wide, shown at 66 px. Resized copies would save about 61 KiB.

  • About 0.5 g of CO₂ per visit

    0.49 g

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

3 checks passed
  • Page weight: 1.7 MB in 56 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 56 requests on a phone: images 1.2 MB (30), scripts 244 KiB (14) and fonts 158 KiB (6). That is a lean page.

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

Accessibility

5 to fixGoogle 9294
  • 3 text elements with low contrast

    3 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 (22 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • 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 (2 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 46 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 9278
  • Title is short (6 characters)

    Your title is only 6 characters: “pladis”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (34 characters)

    Your meta description is only 34 characters: “Bringing happiness with every bite”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Bringing happiness with every bite” and “Bringing happiness with every bite”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 16 links with vague text

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

  • 124 internal links, 14 external

    The homepage links to 124 pages on unitedbiscuits.com and 14 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is http://www.pladisglobal.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.pladisglobal.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

  • Opted out of AI training for 1 crawler

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

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

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

  • Text is in the HTML

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

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://www.pladisglobal.com/en-ng declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.pladisglobal.com/en-ng all use the title “pladis”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.pladisglobal.com/about-us/annual-report-2025 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 10093
  • 15 small tap targets

    15 of 48 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: 1 testimonial or review block. 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 554 words of copy

    The homepage carries about 554 words of visible text.

2 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact us”, “Learn more about our heritage” and “Learn more about our Verkade brand”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • 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 unitedbiscuits.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
Drupal
Framework
jQuery
Analytics
Google Tag Manager

Company

Founded
1948
Headquarters
Hayes

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on unitedbiscuits.com, including 14 speed issues, 5 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
unitedbiscuits.com website review: scores and fixes