Website review, no card needed

cupsdirect.co.uk logo

cupsdirect.co.uk website review

Visit site (opens in a new tab)Reviewed 6 November 202627 issues · 99 checks

This review found 27 issues worth fixing on cupsdirect.co.uk, 10 of them high impact, across 99 checks. The most urgent: improve image delivery. 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
1.2 s933 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 2026982 ms
Jun 20, 2026965 ms
Jun 27, 2026967 ms
Jul 4, 2026972 ms
Jul 11, 2026977 ms
Jul 18, 2026978 ms
Jul 25, 2026974 ms
Aug 1, 2026979 ms
Aug 8, 2026994 ms
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
131 ms108 msMay 16Oct 31117 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026111 ms
May 23, 2026111 ms
May 30, 2026111 ms
Jun 6, 2026115 ms
Jun 13, 2026119 ms
Jun 20, 2026120 ms
Jun 27, 2026121 ms
Jul 4, 2026126 ms
Jul 11, 2026128 ms
Jul 18, 2026126 ms
Jul 25, 2026123 ms
Aug 1, 2026124 ms
Aug 8, 2026123 ms
Aug 15, 2026126 ms
Aug 22, 2026126 ms
Aug 29, 2026121 ms
Sep 5, 2026121 ms
Sep 12, 2026121 ms
Sep 19, 2026121 ms
Sep 26, 2026120 ms
Oct 3, 2026118 ms
Oct 10, 2026119 ms
Oct 17, 2026119 ms
Oct 24, 2026118 ms
Oct 31, 2026117 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

Live view · interaction off

Speed

7 to fix75
  • Improve image delivery

    1.2 s · 1.4 MB

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

  • Render-blocking requests

    1.3 s

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

  • 6,320 HTML elements

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

  • Main-thread work: 6.3 s

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

  • Mobile performance score: 75

    75/100

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

  • Use efficient cache lifetimes

    350 ms · 90 KiB

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

  • Reduce unused CSS

    300 ms · 49 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, 9gtb.com and Shopify and others), adding 534 KiB and 181 ms of main-thread time.

  • Font display

    150 ms

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

  • 5 long tasks on the main thread

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

  • Reduce unused JavaScript

    63 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

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

    15 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Group of platter boxes filled with sandwiches and served wi…”.

  • Time to Interactive: 10.2 s

    10.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    +6%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 117 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-31, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 117 ms

    117 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 353 ms

    353 ms

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

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 123 ms

    123 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix64
  • Page weight: 4.4 MB in 325 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 325 requests on a phone: images 2.8 MB (167), other files 650 KiB (70) and scripts 572 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    PLAT_720x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.2 g of CO₂ per visit

    1.24 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9194
  • 12 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • 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 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “CupsDirect Food & Drink Packaging - Biodegradable Catering Disposables”.

  • Meta description is long (317 characters)

    Your meta description is 317 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 13 links crawlers can't follow

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

  • 460 internal links, 4 external

    The homepage links to 460 pages on cupsdirect.co.uk and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “<img src="//cupsdirect.co.uk/cdn/shop/files/cupsdirect-catering-supplies-logo-bicolor_2x_6a6f7934-456a-4203-b186-751a74…”.

  • Canonical URL set

    The canonical URL is https://cupsdirect.co.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

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

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://cupsdirect.co.uk/sitemap.xml.

AI search readiness

100
4 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 (3,338 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 10 pages without a meta description

    /collections/cups, /collections/paper-cups-for-hot-drinks, /collections/single-wall-paper-hot-cups, /collections/double-wall-hot-cups, /collections/aqueous-compostable-hot-cups and /collections/lids-accessories and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    /pages/about has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 138 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (cupsdirect.co.uk).

  • Valid certificate (46 days left)

    The certificate from Let's Encrypt · YE1 verifies for cupsdirect.co.uk and is valid for another 46 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://cupsdirect.co.uk redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 44 links work

    All 44 links checked from your homepage (40 internal, 4 external) answered without errors; 6 did not answer within 5 s.

Domain and trust

  • No CAA record

    cupsdirect.co.uk has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    cupsdirect.co.uk's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 16 years old

    16 years

    cupsdirect.co.uk was registered in Dec 2009 through Tucows Inc t/a Tucows. An established domain carries more trust with email providers and search engines.

  • Registered until Dec 2027

    cupsdirect.co.uk is registered until Dec 2027.

Content and conversion

2 to fix79
  • 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.

  • No analytics detected

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

  • About 2,860 words of copy

    The homepage carries about 2,860 words of visible text.

5 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Track Order”, “Shop Food Tray Range” and “Shop our Bagasse Range”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 93 testimonial or review blocks, a star rating and 2 trust badges.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Email authentication

1 to fix75
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be cupsdirect.co.uk is still delivered. Add a report address, check the reports, then move to quarantine.

  • Email authentication score: 75/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 +a +mx +ip4:50.28.61.68 include:servers.mcsv.net include:shops.shopify.com include:spf.protection.outlook.com in…”.

  • DKIM signing found

    A DKIM key is published (selector “s1” and “s2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

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

  • 24 other companies contacted

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

Apps on your store

Your storefront loads 6 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Klaviyo Email Marketing Sms · Reviews Co Uk Product And Merchant Review Collection · Discount Kit · firstbits.com.br · gorgias.chat · 9gtb.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Colchester

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on cupsdirect.co.uk, including 10 speed issues, 3 SEO issues and 2 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