Website review, no card needed

ziggyfamily.com logo

ziggyfamily.com website review

Visit site (opens in a new tab)Reviewed 7 November 202632 issues · 89 checks

This review found 32 issues worth fixing on ziggyfamily.com, 13 of them high impact, across 89 checks. The most urgent: main-thread work: 6.4 s. 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
2.3 s1.8 sMay 16Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
202 ms149 msMay 16Oct 31186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026155 ms
May 23, 2026157 ms
May 30, 2026162 ms
Jun 6, 2026167 ms
Jun 13, 2026170 ms
Jun 20, 2026176 ms
Jun 27, 2026179 ms
Jul 4, 2026185 ms
Jul 11, 2026188 ms
Jul 18, 2026189 ms
Jul 25, 2026193 ms
Aug 1, 2026194 ms
Aug 8, 2026194 ms
Aug 15, 2026196 ms
Aug 22, 2026196 ms
Aug 29, 2026195 ms
Sep 5, 2026196 ms
Sep 12, 2026195 ms
Sep 19, 2026194 ms
Sep 26, 2026192 ms
Oct 3, 2026191 ms
Oct 10, 2026192 ms
Oct 17, 2026187 ms
Oct 24, 2026187 ms
Oct 31, 2026186 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 ziggyfamily.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ziggyfamily.com at 1.2 s1.2 s
  2. ziggyfamily.com at 2.5 s2.5 s
  3. ziggyfamily.com at 3.7 s3.7 s
  4. ziggyfamily.com at 4.9 s4.9 s
  5. ziggyfamily.com at 6.2 s6.2 s
  6. ziggyfamily.com at 7.4 s7.4 s
  7. ziggyfamily.com at 8.6 s8.6 s
  8. ziggyfamily.com at 9.9 s9.9 s

Speed

8 to fix53
  • Main-thread work: 6.4 s

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

  • 3,540 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (loox.io, TikTok and rechargecdn.com and others), adding 1.1 MB and 1.2 s of main-thread time.

  • Use efficient cache lifetimes

    850 ms · 406 KiB

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

  • Mobile performance score: 53

    53/100

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

  • Reduce unused JavaScript

    450 ms · 385 KiB

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

  • Render-blocking requests

    550 ms

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

  • loox.io adds 401 ms

    401 ms

    loox.io costs a phone 401 ms of main-thread work and 278 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.

  • 15 long tasks on the main thread

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

  • Improve image delivery

    171 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    28 KiB

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

  • Minify JavaScript

    11 KiB

    11 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    11 KiB

    About 11 KiB of CSS is downloaded but never applied on this page.

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

    16 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 19.2 s

    19.2 s

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

  • Largest Contentful Paint: 7.5 s

    7.5 s

    Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Chat adulte stérilisé avec la pâtée de Noël Ziggy pour chat”.

  • Speed Index: 10.2 s

    10.2 s

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

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

    +20%

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

  • Total Blocking Time: 542 ms

    542 ms

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

8 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.9 s

    1.9 s

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

  • Real-user INP: 155 ms

    155 ms

    Real visitors wait 155 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 700 ms

    700 ms

    Real visitors wait 700 ms for your server to start answering (75th percentile). Good is under 800 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.

  • 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

1 to fix70
  • Page weight: 4.2 MB in 319 requests

    4.2 MB

    Your homepage downloads 4.2 MB in 319 requests on a phone: images 1.5 MB (88), scripts 1.4 MB (92) and other files 786 KiB (119). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (339 KiB) 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 1.2 g of CO₂ per visit

    1.19 g

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

2 checks passed
  • 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

10 to fixGoogle 7687
  • 3 buttons without a name

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

  • Elements must only use permitted ARIA attributes (20 elements)

    Elements must only use permitted ARIA attributes: 20 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • 3 tap targets too small

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

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

  • 9 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

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

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

Google 92100
  • 177 internal links, 7 external

    The homepage links to 177 pages on ziggyfamily.com and 7 external pages.

8 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Healthy, natural and made in France kibble and pâtés for cats and kittens. To take care of your cat, while delighting i…”.

  • One H1 headline

    Your main headline reads: “Natural Dry Food and Wet Food for cats”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Ziggy | Healthy, transparent and committed food for cats”.

  • Canonical URL set

    The canonical URL is https://ziggyfamily.com/en.

  • 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://ziggyfamily.com/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 (2,452 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix74
  • 1 linked page hidden from search

    https://ziggyfamily.com/en/collections/cat-discovery-sets is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://ziggyfamily.com/en/collections/friandises-chat and https://ziggyfamily.com/en/collections/cat-treats all use the title “Treats for cats – Ziggy”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://ziggyfamily.com/en/collections/friandises-chat and https://ziggyfamily.com/en/collections/cat-treats use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://ziggyfamily.com/en/collections/friandises-chat, whose canonical is https://ziggyfamily.com/en/collections/cat-treats. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://ziggyfamily.com/en/collections/friandises-chat, https://ziggyfamily.com/en/pages/verified-reviews-ziggy, https://ziggyfamily.com/en/pages/cat-feeding-calculator, https://ziggyfamily.com/en/collections/subscription-dry-food-wet-food-cats, https://ziggyfamily.com/en/pages/personnalized-cat-discovery-bundle and https://ziggyfamily.com/en/collections/food-supplements-cats and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://ziggyfamily.com/en/collections/subscription-dry-food-wet-food-cats has 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.

  • 2 pages slow to respond

    https://ziggyfamily.com/en/collections/friandises-chat and https://ziggyfamily.com/en/collections/subscription-dry-food-wet-food-cats took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343129958&tm=gtm002&Ver=2&mid=df21ecc2-286e-429a-bf2d-c3029fce43e3&bo=1&sid=53fa5ac0da7811f1bf0545e8c97397cc&vid=53fa8be0da7811f1bc90038d6ac18dc6&vids=1&msclkid=N&gtm_.

  • 3 JavaScript errors while loading

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    104 of 111 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 2,295 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SUBSCRIBE (15% 0FF)” and “CONTACT”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Shop all dry food”, “Shop all wet food” and “Shop all mousses”.

  • 4 short forms

    4 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, 1 customer or partner logo and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • 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
  • 9 trackers load before any consent

    9

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

  • 38 cookies set on arrival

    38

    Opening the homepage sets 38 cookies, 1 of them by other companies (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.

  • 49 other companies contacted

    Loading the homepage contacts 49 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 ziggyfamily.com, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Shopiens · Microsoft Clarity · Wisepops Popup Builder Cro · Gorgias Live Chat Helpdesk · Axeptio · loox.io · rechargecdn.com · referralprogramapp.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

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Bordeaux

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on ziggyfamily.com, including 13 speed 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