Website review, no card needed

whyteandmackayltd.com logo

whyteandmackayltd.com website review

Visit site (opens in a new tab)Reviewed 1 November 202637 issues · 75 checks

This review found 37 issues worth fixing on whyteandmackayltd.com, 10 of them high impact, across 75 checks. The most urgent: 2 images over 500 KB. 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

Full-page screenshot of whyteandmackayltd.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix85
  • Mobile performance score: 85

    85/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Optanon and Macropod BugHerd and others), adding 722 KiB and 579 ms of main-thread time.

  • Improve image delivery

    525 KiB

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

  • Use efficient cache lifetimes

    504 KiB

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

  • Reduce unused JavaScript

    449 KiB

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

  • Google Tag Manager adds 397 ms

    397 ms

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

  • Font display

    400 ms

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

  • 6 long tasks on the main thread

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

  • Reduce unused CSS

    130 ms · 35 KiB

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

  • Legacy JavaScript

    38 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix93
  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 215 ms

    215 ms

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

  • 4 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “By clicking “Accept All Cookies”, you agree to the storing …”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix55
  • 2 images over 500 KB

    2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.8 MB

    2 images are downloaded at several times the size a phone draws them, for example 2-min.jpg at 3,240 px wide, shown at 390 px. Resized copies would save about 1.8 MB.

  • 2 images in older formats

    2 images (2.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

2 checks passed
  • Page weight: 1.7 MB in 38 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 38 requests on a phone: scripts 898 KiB (11), images 617 KiB (7) and fonts 190 KiB (4). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8390
  • 4 text elements with low contrast

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

6 to fixGoogle 9276
  • Title is short (25 characters)

    Your title is only 25 characters: “Home | Whyte & Mackay Ltd”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 27 internal links, 2 external

    The homepage links to 27 pages on whyteandmackayltd.com and 2 external pages.

3 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Since 1844, Whyte & Mackay Ltd’s roots have been firmly planted in Scotland. Today we continue to grow our portfolio of…”.

  • One H1 headline

    Your main headline reads: “Whyte and Mackay”.

  • robots.txt in place

    robots.txt is in place.

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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

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

Other pages

3 to fix75
  • 6 pages without a title

    https://whyteandmackayltd.com/news, https://whyteandmackayltd.com/bulk-private-label, https://whyteandmackayltd.com/our-company/our-policies/anti-bribery-policy, https://whyteandmackayltd.com/our-company/our-policies/responsible-drinking, https://whyteandmackayltd.com/our-company/our-policies/anti-slavery-and-human-trafficking and https://whyteandmackayltd.com/terms-and-conditions have no <title>, so Google invents the link text in results.

  • 8 pages without a meta description

    https://whyteandmackayltd.com/news, https://whyteandmackayltd.com/bulk-private-label, https://whyteandmackayltd.com/our-company/our-policies/anti-bribery-policy, https://whyteandmackayltd.com/our-company/our-policies/responsible-drinking, https://whyteandmackayltd.com/our-company/our-policies/anti-slavery-and-human-trafficking and https://whyteandmackayltd.com/our-company/our-policies/tax-governance and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://whyteandmackayltd.com/our-brands, https://whyteandmackayltd.com/our-company, https://whyteandmackayltd.com/our-locations, https://whyteandmackayltd.com/our-board, https://whyteandmackayltd.com/news and https://whyteandmackayltd.com/contact-us and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://whyteandmackayltd.com/our-brands, https://whyteandmackayltd.com/our-company, https://whyteandmackayltd.com/our-locations, https://whyteandmackayltd.com/our-board, https://whyteandmackayltd.com/news and https://whyteandmackayltd.com/contact-us and 3 others 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.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9289
  • 17 small tap targets

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

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 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

4 to fix50
  • 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 social proof

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

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

  • Only about 153 words

    The homepage has only about 153 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact us” and “Get In Touch”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

  • 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). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

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

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on whyteandmackayltd.com, including 12 speed issues, 6 SEO issues and 4 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