Website review, no card needed

mintapple.co.uk logo

mintapple.co.uk website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 84 checks

This review found 29 issues worth fixing on mintapple.co.uk, 10 of them high impact, across 84 checks. The most urgent: page weight: 11.2 MB in 456 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

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.3 sJul 25Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
149 ms121 msSep 12Nov 7138 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 2026124 ms
Sep 19, 2026127 ms
Sep 26, 2026128 ms
Oct 3, 2026137 ms
Oct 10, 2026146 ms
Oct 17, 2026136 ms
Nov 7, 2026138 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 mintapple.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mintapple.co.uk at 3.0 s3.0 s
  2. mintapple.co.uk at 5.9 s5.9 s
  3. mintapple.co.uk at 8.9 s8.9 s
  4. mintapple.co.uk at 11.8 s11.8 s
  5. mintapple.co.uk at 14.8 s14.8 s
  6. mintapple.co.uk at 17.7 s17.7 s
  7. mintapple.co.uk at 20.7 s20.7 s
  8. mintapple.co.uk at 23.7 s23.7 s

Speed

9 to fix84
  • Main-thread work: 4.2 s

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

  • 3,126 HTML elements

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

  • Mobile performance score: 84

    84/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Shopify and others), adding 1.7 MB and 625 ms of main-thread time.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Reduce unused JavaScript

    342 KiB

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

  • Klaviyo adds 227 ms

    227 ms

    Klaviyo costs a phone 227 ms of main-thread work and 745 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.

  • Google Tag Manager adds 207 ms

    207 ms

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

  • Shopify adds 164 ms

    164 ms

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

  • Improve image delivery

    225 KiB

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

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    36 KiB

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

  • Use efficient cache lifetimes

    29 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 14.0 s

    14.0 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 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.6 s

    1.6 s

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

  • Real-user INP: 140 ms

    140 ms

    Real visitors wait 140 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: 1.2 s

    1.2 s

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

  • Real-user TTFB: 411 ms

    411 ms

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

  • Total Blocking Time: 176 ms

    176 ms

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

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 11.2 MB in 456 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 456 requests on a phone: media 7.1 MB (1), other files 1.8 MB (306) and scripts 1.4 MB (118). Under 2 MB keeps phones on slow connections fast.

  • About 3.2 g of CO₂ per visit

    3.18 g

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

3 checks passed
  • 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.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8789
  • 100 tap targets too small

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

  • Scrollable region must have keyboard access (20 elements)

    Scrollable region must have keyboard access: 20 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • 20 buttons without a name

    20 buttons have no accessible name, so screen readers announce just “button”.

  • 4 images without alt text

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

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

  • 22 links without text

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

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

1 to fixGoogle 9295
  • Meta description is long (307 characters)

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

  • 401 internal links, 10 external

    The homepage links to 401 pages on mintapple.co.uk and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “MINTAPPLE.”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “MINTAPPLE. | Official Store | Luxury Apple Accessories”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://mintapple.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 description; sameAs (social profiles) and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://mintapple.co.uk/collections/the-outlet-clearance, https://mintapple.co.uk/collections/small-leather-accessories, https://mintapple.co.uk/collections/travel-goods-by-mintapple and https://mintapple.co.uk/collections/newin have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://mintapple.co.uk/collections/gifts-for-him, https://mintapple.co.uk/collections/personalised-leather-collections, https://mintapple.co.uk/collections/apple-watch-straps, https://mintapple.co.uk/collections/best-sellers and https://mintapple.co.uk/collections/newin have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://mintapple.co.uk/collections/the-outlet-clearance, https://mintapple.co.uk/collections/gifts-for-him, https://mintapple.co.uk/collections/personalised-leather-collections and https://mintapple.co.uk/collections/black-friday-sale took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 96 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
  • 68 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://mintapple.co.uk/cdn/shop/t/244/assets/cart-drawer.css?v=74642' because its MIME ty…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 739 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”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop All”, “JOIN NOW FOR FREE” and “SHOP NOW”.

  • 6 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 15 cookies set on arrival

    15

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 mintapple.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Zepto Product Personalizer · Sami Wholesale · Checkout Rules · Propel Replays · Essential Loyalty Rewards · Boo Eu Withdrawal Button

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Droitwich Spa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on mintapple.co.uk, including 12 speed issues, 1 SEO issue 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