Website review, no card needed

lindocat.it logo

lindocat.it website review

Visit site (opens in a new tab)Reviewed 17 November 202643 issues · 90 checks

This review found 43 issues worth fixing on lindocat.it, 21 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
5.3 s4.5 sMay 30Nov 144.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.0 s
Jun 6, 20265.0 s
Jul 18, 20265.1 s
Jul 25, 20265.2 s
Aug 8, 20264.8 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20264.9 s
Sep 12, 20264.9 s
Sep 19, 20265.0 s
Sep 26, 20264.8 s
Oct 3, 20264.7 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.6 s
Oct 31, 20264.7 s
Nov 7, 20264.8 s
Nov 14, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
125 ms101 msMay 30Nov 14115 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026122 ms
Jul 18, 2026113 ms
Jul 25, 2026111 ms
Aug 1, 2026104 ms
Aug 8, 2026106 ms
Aug 22, 2026110 ms
Aug 29, 2026111 ms
Sep 5, 2026115 ms
Sep 12, 2026117 ms
Sep 26, 2026117 ms
Oct 3, 2026117 ms
Oct 10, 2026118 ms
Oct 24, 2026115 ms
Oct 31, 2026116 ms
Nov 7, 2026116 ms
Nov 14, 2026115 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 lindocat.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lindocat.it at 1.7 s1.7 s
  2. lindocat.it at 3.5 s3.5 s
  3. lindocat.it at 5.2 s5.2 s
  4. lindocat.it at 6.9 s6.9 s
  5. lindocat.it at 8.7 s8.7 s
  6. lindocat.it at 10.4 s10.4 s
  7. lindocat.it at 12.1 s12.1 s
  8. lindocat.it at 13.9 s13.9 s

Speed

13 to fix41
  • Use efficient cache lifetimes

    24.4 s · 10.2 MB

    148 files are served with short cache lifetimes, so returning visitors download them again (10.2 MB).

  • Render-blocking requests

    12.6 s

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

  • Reduce unused CSS

    8.0 s · 1.6 MB

    About 1.6 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.0 s faster on a phone.

  • Reduce unused JavaScript

    7.7 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.7 s faster on a phone.

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.1 s

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

  • Improve image delivery

    3.4 MB

    11 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and iubenda and others), adding 1.3 MB and 839 ms of main-thread time.

  • Legacy JavaScript

    550 ms · 57 KiB

    Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.

  • Google CDN adds 440 ms

    440 ms

    Google CDN costs a phone 440 ms of main-thread work and 742 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

    450 ms

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

  • 13 long tasks on the main thread

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

  • Google Tag Manager adds 237 ms

    237 ms

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

  • Document request latency

    162 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    14 KiB

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

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

    372 ms

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

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 3.6 s

    3.6 s

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

  • First Contentful Paint: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 45.3 s

    45.3 s

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

  • Speed Index: 31.7 s

    31.7 s

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

  • Time to Interactive: 46.5 s

    46.5 s

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

  • Total Blocking Time: 574 ms

    574 ms

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

3 checks passed
  • Real-user INP: 115 ms

    115 ms

    Real visitors wait 115 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.

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

5 to fix38
  • Page weight: 12.1 MB in 170 requests

    12.1 MB

    Your homepage downloads 12.1 MB in 170 requests on a phone: images 6.5 MB (41), scripts 2.6 MB (58) and stylesheets 1.9 MB (53). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.

  • 15 images in older formats

    15 images (6.0 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.

  • 3 images below the first screen load straight away

    3 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    Lindocat_pack-Super-Premium_ITA-desktop_L.png 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).

  • About 3.4 g of CO₂ per visit

    3.43 g

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

1 checks passed
  • 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 8291
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 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 (41 elements)

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

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

  • 13 links without text

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

  • 2 tap targets too small

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 50 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 77 internal links, 15 external

    The homepage links to 77 pages on lindocat.it and 15 external pages.

6 checks passed
  • Meta description: 119 characters

    Your meta description is 119 characters: “La lettiera ideale per chi cerca un prodotto dalle performance straordinarie. Entra e scopri tutti i prodotti Lindocat!”.

  • Title: 43 characters

    Your title is a healthy 43 characters: “Lindocat - La scelta dei gatti più esigenti”.

  • Canonical URL set

    The canonical URL is https://www.lindocat.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.lindocat.it/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lindocat.it/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.

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.

  • 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,216 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 10 pages without a meta description

    https://www.lindocat.it/categoria-prodotto/agglomeranti, https://www.lindocat.it/categoria-prodotto/assorbenti, https://www.lindocat.it/categoria-prodotto/vegetali, https://www.lindocat.it/categoria-prodotto/lindocat-advanced, https://www.lindocat.it/prodotto/probiotic and https://www.lindocat.it/prodotto/superpremium-profumata and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages slow to respond

    https://www.lindocat.it/categoria-prodotto/agglomeranti, https://www.lindocat.it/categoria-prodotto/assorbenti, https://www.lindocat.it/categoria-prodotto/vegetali, https://www.lindocat.it/categoria-prodotto/lindocat-advanced, https://www.lindocat.it/prodotto/probiotic and https://www.lindocat.it/prodotto/superpremium-profumata and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://www.lindocat.it/.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    26 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 782 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Download”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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

  • 10 cookies set on arrival

    10

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

  • 10 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 lindocat.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Tag Manager
Hosting
Leonet As It Uan Company S.R.L.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on lindocat.it, including 23 speed issues, 3 SEO issues 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