Website review, no card needed

grandties.co.uk logo

grandties.co.uk website review

Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 78 checks

This review found 36 issues worth fixing on grandties.co.uk, 9 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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 grandties.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grandties.co.uk at 1.7 s1.7 s
  2. grandties.co.uk at 3.4 s3.4 s
  3. grandties.co.uk at 5.1 s5.1 s
  4. grandties.co.uk at 6.8 s6.8 s
  5. grandties.co.uk at 8.5 s8.5 s
  6. grandties.co.uk at 10.2 s10.2 s
  7. grandties.co.uk at 11.9 s11.9 s
  8. grandties.co.uk at 13.6 s13.6 s

Speed

8 to fix71
  • Render-blocking requests

    11.0 s

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

  • Mobile performance score: 71

    71/100

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

  • Improve image delivery

    884 KiB

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

  • Reduce unused JavaScript

    300 ms · 252 KiB

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

  • Use efficient cache lifetimes

    281 KiB

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

  • 2,083 HTML elements

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

  • Shopify adds 146 ms

    146 ms

    Shopify costs a phone 146 ms of main-thread work and 403 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.

  • ecomsend.com adds 0 ms

    0 ms

    ecomsend.com costs a phone 0 ms of main-thread work and 408 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Shopify, nfcube.com and shop.app and others), adding 867 KiB and 155 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 52 KiB

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

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 104 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 42 ms

    42 ms

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

Core Web Vitals

4 to fix74
  • Speed Index: 18.2 s

    18.2 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • 1 image without width and height

    1 image 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.

3 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 55 ms

    55 ms

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

Images and page weight

4 to fix52
  • Page weight: 4.0 MB in 251 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 251 requests on a phone: images 2.2 MB (68), other files 794 KiB (106) and scripts 741 KiB (53). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1217-Handy-Lifestyle011.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).

  • 9 images far larger than shown

    395 KiB

    9 images are downloaded at several times the size a phone draws them, for example GrandTies_InsulateCoffeeMug_Main__PeachCremePink1_Transparen at 1,024 px wide, shown at 230 px. Resized copies would save about 395 KiB.

  • 7 images below the first screen load straight away

    7 images further down the page (296 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.14 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8993
  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 5 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 96 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “GrandTies I Quality Drinkware, Cookware Set, Kitchenware, Pet Supplies – GrandTies-UK”.

  • 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 (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.

  • Meta description is long (319 characters)

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 168 internal links, 11 external

    The homepage links to 168 pages on grandties.co.uk and 11 external pages.

4 checks passed
  • Canonical URL set

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

  • 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://grandties.co.uk/sitemap.xml.

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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://grandties.co.uk/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 1 page without a title

    https://grandties.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://grandties.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 9 pages without a meta description

    https://grandties.co.uk/collections/all, https://grandties.co.uk/collections/drinkware, https://grandties.co.uk/collections/bottles, https://grandties.co.uk/collections/jugs, https://grandties.co.uk/collections/pets and https://grandties.co.uk/collections/bowls-feeders and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://grandties.co.uk/products/insulated-coffee-mug-with-sliding-lid-16oz-460ml-grande-atlantis-blue, https://grandties.co.uk/products/insulated-coffee-mug-with-sliding-lid-16oz-460ml-grande-caffe-latte-beige, https://grandties.co.uk/products/insulated-coffee-mug-with-sliding-lid-16oz-460ml-grande-carrot-orange, https://grandties.co.uk/products/insulated-coffee-mug-with-sliding-lid-16oz-460ml-grande-cobalt-blue and https://grandties.co.uk/products/insulated-coffee-mug-with-sliding-lid-16oz-460ml-grande-cranberry-red use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://grandties.co.uk/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://grandties.co.uk/collections/drinkware, https://grandties.co.uk/collections/insulated-coffee-mug, https://grandties.co.uk/collections/pets and https://grandties.co.uk/customer_authentication/redirect took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

1 to fixGoogle 10093
  • 68 small tap targets

    68 of 110 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 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.

  • No analytics detected

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

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

  • About 673 words of copy

    The homepage carries about 673 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: “Shop Now”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Return to shop”, “Shop Now” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Risk reducer mentioned

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 7 cookies set on arrival

    7

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 grandties.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

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

Apps your storefront loads

Instafeed · Ecomsend · Appio Amazon Reviews · Shipbyamazonfba · Selleasy

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

Stack

E-commerce
Shopify
Hosting
Shopify

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 grandties.co.uk, including 12 speed issues, 4 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