Website review, no card needed

kukuli.com.pe logo

kukuli.com.pe website review

Visit site (opens in a new tab)Reviewed 19 October 202651 issues · 92 checks

This review found 51 issues worth fixing on kukuli.com.pe, 23 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
3.7 s3.0 sApr 25Oct 103.6 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.3 s
May 2, 20263.3 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.3 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.5 s
Oct 10, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
377 ms342 msApr 25Oct 10357 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026373 ms
May 2, 2026363 ms
May 9, 2026367 ms
May 16, 2026366 ms
May 23, 2026362 ms
May 30, 2026371 ms
Jun 6, 2026365 ms
Jun 13, 2026366 ms
Jun 20, 2026370 ms
Jun 27, 2026364 ms
Jul 4, 2026363 ms
Jul 11, 2026359 ms
Jul 18, 2026356 ms
Jul 25, 2026349 ms
Aug 1, 2026348 ms
Aug 8, 2026346 ms
Aug 15, 2026349 ms
Aug 22, 2026355 ms
Aug 29, 2026354 ms
Sep 5, 2026352 ms
Sep 12, 2026353 ms
Sep 19, 2026352 ms
Sep 26, 2026356 ms
Oct 3, 2026361 ms
Oct 10, 2026357 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 kukuli.com.pe (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix44
  • Reduce unused JavaScript

    5.8 s · 829 KiB

    About 829 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

  • Improve image delivery

    3.0 s · 650 KiB

    1 image could be 650 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 44

    44/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 2.8 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    900 ms · 252 KiB

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

  • vtexassets.com adds 532 ms

    532 ms

    vtexassets.com costs a phone 532 ms of main-thread work and 1.4 MB 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 352 ms

    352 ms

    Google Tag Manager costs a phone 352 ms of main-thread work and 490 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 CDN adds 326 ms

    326 ms

    Google CDN costs a phone 326 ms of main-thread work and 736 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.

  • Main-thread work: 2.8 s

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

  • Reduce unused CSS

    250 ms · 33 KiB

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

  • Legacy JavaScript

    150 ms · 47 KiB

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

  • 14 long tasks on the main thread

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 44 ms

    44 ms

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

Core Web Vitals

12 to fix0
  • 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.36

    0.36

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

  • First Contentful Paint: 9.7 s

    9.7 s

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

  • Largest Contentful Paint: 21.6 s

    21.6 s

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

  • Time to Interactive: 22.2 s

    22.2 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • 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 INP: 342 ms

    342 ms

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 465 ms

    465 ms

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

  • 22 images without width and height

    22 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-10-10, real Chrome visitors' tap response (inp) went from 373 ms to 357 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

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

1 checks passed
  • Cumulative Layout Shift: 0.007

    0.007

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

Images and page weight

3 to fix50
  • 1 image over 500 KB

    d491954a-7200-44d2-844b-f739cc5ac0f0___4bd49f1a0a75b98b8adf5 weighs 677 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    631 KiB

    1 image is downloaded at several times the size a phone draws it, for example d491954a-7200-44d2-844b-f739cc5ac0f0___4bd49f1a0a75b98b8adf5 at 4,489 px wide, shown at 390 px. Resized copies would save about 631 KiB.

  • Page weight: 3.4 MB in 141 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 141 requests on a phone: scripts 2.0 MB (46), images 733 KiB (30) and other files 365 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.97 g

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

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

Accessibility

11 to fixGoogle 7282
  • 2 buttons without a name

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

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 4 text elements with low contrast

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

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

  • All page content should be contained by landmarks (4 elements)

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

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

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

  • 7 links without text

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

  • 1 form field without a label

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

    No Open Graph image, 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.

  • 22 internal links, 6 external

    The homepage links to 22 pages on kukuli.com.pe and 6 external pages.

5 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Compra ropa de bebé, niños y niñas en Kukuli, junto a accesorios para bebés 100% seguros y de la mejor calidad. Envíos …”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Tienda de ropa para Bebés, Niños y Niñas | Kukuli Perú”.

  • Canonical URL set

    The canonical URL is https://www.kukuli.com.pe/.

  • 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.kukuli.com.pe/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.kukuli.com.pe/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.

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

Other pages

5 to fix67
  • 2 pages without a title

    https://www.kukuli.com.pe/bebes/bebitas and https://www.kukuli.com.pe/infantil/nina have no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://www.kukuli.com.pe/ofertas%20de%20invierno and https://www.kukuli.com.pe/politica-de-privacidad are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.kukuli.com.pe/bebes/bebitas and https://www.kukuli.com.pe/infantil/nina have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://www.kukuli.com.pe/ofertas%20de%20invierno, https://www.kukuli.com.pe/conocenos, https://www.kukuli.com.pe/nuestras-tiendas, https://www.kukuli.com.pe/consultas, https://www.kukuli.com.pe/trabaja-con-nosotros and https://www.kukuli.com.pe/terminos-y-condiciones and 3 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://www.kukuli.com.pe/bebes/bebitas, https://www.kukuli.com.pe/infantil/ninos, https://www.kukuli.com.pe/infantil/nina, https://www.kukuli.com.pe/accesorios, https://www.kukuli.com.pe/mundo-bebe and https://www.kukuli.com.pe/ofertas%20de%20invierno and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.kukuli.com.pe/nuestras-tiendas 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.

  • 4 pages slow to respond

    https://www.kukuli.com.pe/bebes/bebitas, https://www.kukuli.com.pe/bebes/bebitos, https://www.kukuli.com.pe/infantil/ninos and https://www.kukuli.com.pe/infantil/nina took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

Best practices

2 to fixGoogle 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://www.kukuli.com.pe/.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 78 words

    The homepage has only about 78 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 14 cookies set on arrival

    14

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

  • 26 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

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

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager | Hotjar

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on kukuli.com.pe, including 22 speed issues, 3 SEO issues and 4 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