Website review, no card needed

madeincookware.co.uk logo

madeincookware.co.uk website review

Visit site (opens in a new tab)Reviewed 5 November 202622 issues · 73 checks

This review found 22 issues worth fixing on madeincookware.co.uk, 5 of them high impact, across 73 checks. The most urgent: page weight: 14.6 MB in 307 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.2 s821 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026934 ms
May 23, 2026898 ms
May 30, 2026875 ms
Jun 6, 2026866 ms
Jun 13, 2026859 ms
Jun 20, 2026872 ms
Jun 27, 2026893 ms
Jul 4, 2026916 ms
Jul 11, 2026962 ms
Jul 18, 2026976 ms
Jul 25, 2026962 ms
Aug 1, 20261.0 s
Aug 8, 2026973 ms
Aug 15, 2026984 ms
Aug 22, 2026946 ms
Aug 29, 2026903 ms
Sep 5, 2026896 ms
Sep 12, 2026882 ms
Sep 19, 2026893 ms
Sep 26, 2026881 ms
Oct 3, 2026863 ms
Oct 10, 20261.0 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
132 ms104 msMay 16Oct 31120 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026107 ms
May 23, 2026113 ms
May 30, 2026119 ms
Jun 6, 2026120 ms
Jun 13, 2026120 ms
Jun 20, 2026120 ms
Jun 27, 2026120 ms
Jul 4, 2026121 ms
Jul 11, 2026122 ms
Jul 18, 2026122 ms
Jul 25, 2026122 ms
Aug 1, 2026121 ms
Aug 8, 2026122 ms
Aug 15, 2026125 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026128 ms
Sep 19, 2026128 ms
Sep 26, 2026126 ms
Oct 3, 2026124 ms
Oct 10, 2026125 ms
Oct 17, 2026122 ms
Oct 24, 2026121 ms
Oct 31, 2026120 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 madeincookware.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix80
  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    950 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Bold Commerce, Shopify and Klaviyo and others), adding 964 KiB and 560 ms of main-thread time.

  • Reduce unused JavaScript

    447 KiB

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

  • Use efficient cache lifetimes

    299 KiB

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

  • Main-thread work: 2.1 s

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

  • 1,974 HTML elements

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

  • Improve image delivery

    245 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    55 KiB

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

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

    67 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 12.2 s

    12.2 s

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

  • Largest content (LCP) got 21% slower for real visitors

    +21%

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

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EXPLORE PROFESSIONAL COOKWARE”.

  • Cumulative Layout Shift: 0.155

    0.155

    The layout shifts by 0.155 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Tap response (INP) got 10% slower for real visitors

    +10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 107 ms to 120 ms 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.3 s

    1.3 s

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

  • Real-user INP: 102 ms

    102 ms

    Real visitors wait 102 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: 519 ms

    519 ms

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

  • Speed Index: 2.8 s

    2.8 s

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

  • Total Blocking Time: 104 ms

    104 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

Images and page weight

1 to fix70
  • Page weight: 14.6 MB in 307 requests

    14.6 MB

    Your homepage downloads 14.6 MB in 307 requests on a phone: media 11.6 MB (1), scripts 1.1 MB (81) and other files 889 KiB (143). Under 2 MB keeps phones on slow connections fast.

  • About 4.1 g of CO₂ per visit

    4.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.13 g of CO₂e: 496.1 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

3 to fixGoogle 9095
  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 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: 48 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9283
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “Made In: Professional-Quality Cookware, Non Stick, Carbon ... – Made In Cookware - UK”.

  • 142 internal links, 24 external

    The homepage links to 142 pages on madeincookware.co.uk and 24 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Made In is delivering Stainless Steel, Non Stick, Carbon Steel, Knives, Plates, and Glasses directly to your door at ho…”.

  • Canonical URL set

    The canonical URL is https://www.madeincookware.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://www.madeincookware.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 (1,312 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.madeincookware.co.uk/pages/reviews and https://www.madeincookware.co.uk/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.madeincookware.co.uk/pages/cookware-finder-quiz 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 40 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
  • 10 small tap targets

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

  • 5 JavaScript errors while loading

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

Content and conversion

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

    The homepage carries about 416 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop All”, “Shop now” and “Shop Stainless Clad”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and “100,000+ Reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 26 cookies set on arrival

    26

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

  • 41 other companies contacted

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

Apps your storefront loads

Consentmo Gdpr · Eg Auto Add To Cart · Attentive · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Gdpr Backpack · Countdown Timer · bazaarvoice.com · boldapps.net · siena.cx

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
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
4 open roles
Teams
Marketing (2), Operations (1), Product Design (1)
Job board
bamboohr

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on madeincookware.co.uk, including 11 speed issues and 2 SEO issues. 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