Website review, no card needed

kiwoko.com logo

kiwoko.com website review

Visit site (opens in a new tab)Reviewed 26 October 202639 issues · 85 checks

This review found 39 issues worth fixing on kiwoko.com, 15 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s2.0 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.0 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.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.2 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
189 ms164 msMay 9Oct 24185 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026168 ms
May 16, 2026167 ms
May 23, 2026167 ms
May 30, 2026168 ms
Jun 6, 2026169 ms
Jun 13, 2026171 ms
Jun 20, 2026171 ms
Jun 27, 2026173 ms
Jul 4, 2026177 ms
Jul 11, 2026179 ms
Jul 18, 2026180 ms
Jul 25, 2026180 ms
Aug 1, 2026180 ms
Aug 8, 2026182 ms
Aug 15, 2026184 ms
Aug 22, 2026185 ms
Aug 29, 2026185 ms
Sep 5, 2026185 ms
Sep 12, 2026184 ms
Sep 19, 2026184 ms
Sep 26, 2026186 ms
Oct 3, 2026186 ms
Oct 10, 2026186 ms
Oct 17, 2026186 ms
Oct 24, 2026185 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 kiwoko.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kiwoko.com at 0.5 s0.5 s
  2. kiwoko.com at 1.0 s1.0 s
  3. kiwoko.com at 1.5 s1.5 s
  4. kiwoko.com at 1.9 s1.9 s
  5. kiwoko.com at 2.4 s2.4 s
  6. kiwoko.com at 2.9 s2.9 s
  7. kiwoko.com at 3.4 s3.4 s
  8. kiwoko.com at 3.9 s3.9 s

Speed

7 to fix44
  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 44

    44/100

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

  • Improve image delivery

    450 ms · 963 KiB

    29 images could be 963 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    900 ms · 104 KiB

    About 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Reduce unused JavaScript

    570 ms · 354 KiB

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

  • Google Tag Manager adds 350 ms

    350 ms

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

  • 2,365 HTML elements

    The page has 2,365 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 (Google Tag Manager, Optanon and Unpkg and others), adding 829 KiB and 463 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 152 KiB

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

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 138 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

    48 KiB

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

11 to fix33
  • 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 CLS: 0.31

    0.31

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

  • Largest Contentful Paint: 10.4 s

    10.4 s

    Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “15% descuento en compras superiores a 69€ y 10% descuento e…”.

  • Time to Interactive: 12.4 s

    12.4 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Cumulative Layout Shift: 0.414

    0.414

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 58 images without width and height

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

  • Speed Index: 4.1 s

    4.1 s

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

2 checks passed
  • Real-user INP: 188 ms

    188 ms

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

  • Total Blocking Time: 161 ms

    161 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.7 MB in 100 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 100 requests on a phone: images 1.5 MB (59), scripts 916 KiB (17) and fonts 214 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 19 images in older formats

    19 images (1.1 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.

  • 19 images below the first screen load straight away

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

  • 1 image far larger than shown

    89 KiB

    1 image is downloaded at several times the size a phone draws it, for example Nulo_Logo_cmyk.png at 2,332 px wide, shown at 117 px. Resized copies would save about 89 KiB.

  • About 0.8 g of CO₂ per visit

    0.78 g

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

Accessibility

8 to fixGoogle 8489
  • 7 buttons without a name

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

  • 13 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • 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 (h1 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Structured data has 2 problems

    Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: url is not an absolute URL ("www.kiwoko.com")”.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 328 internal links, 22 external

    The homepage links to 328 pages on kiwoko.com and 22 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “5€ DTO. Comida, accesorios e higiene para perros/gatos (>49€). Cupón: DEVUELTA. Entrega 24/48h. Antiparasitarios excl. …”.

  • One H1 headline

    Your main headline reads: “Tienda de mascotas online”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Kiwoko Mundo Animal | Tienda de animales online”.

  • Canonical URL set

    The canonical URL is https://www.kiwoko.com/.

  • 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.kiwoko.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.kiwoko.com/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, sameAs (social profiles) and contact details; logo and description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.kiwoko.com/perros/comida-para-perros/dieta-barf and https://www.kiwoko.com/perros/especial-senior are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.kiwoko.com/carrito and https://www.kiwoko.com/on/demandware.store/Sites-KiwokoES-Site/default/Order-Tracking all use the title “Sites-KiwokoES-Site”. 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://www.kiwoko.com/carrito and https://www.kiwoko.com/on/demandware.store/Sites-KiwokoES-Site/default/Order-Tracking use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=343038827&Ver=2&mid=6706d581-36e5-4563-bd7f-19882d7c4c2c&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Kiwoko%20Mundo%20Animal%20%7C%20Tienda%20de%20animales.

  • 201 small tap targets

    201 of 265 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

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 1,704 words of copy

    The homepage carries about 1,704 words of visible text.

4 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 68 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 3 of them by other companies (measured from a US location before any click).

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on kiwoko.com, including 18 speed issues, 2 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