Website review, no card needed

plantket.cl logo

plantket.cl website review

Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 88 checks

This review found 44 issues worth fixing on plantket.cl, 14 of them high impact, across 88 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.3 s2.6 sMay 30Nov 142.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20262.8 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20262.8 s
Nov 7, 20262.8 s
Nov 14, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
134 ms90 msMay 30Nov 14123 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026129 ms
Jun 6, 2026119 ms
Jun 13, 2026111 ms
Jun 20, 2026107 ms
Jun 27, 2026107 ms
Jul 4, 2026105 ms
Jul 11, 2026103 ms
Jul 18, 2026101 ms
Jul 25, 202697 ms
Aug 1, 2026100 ms
Aug 8, 2026101 ms
Aug 15, 2026102 ms
Aug 22, 2026100 ms
Aug 29, 202697 ms
Sep 5, 202695 ms
Sep 12, 202696 ms
Sep 19, 202697 ms
Sep 26, 202697 ms
Oct 3, 202699 ms
Oct 10, 2026102 ms
Oct 17, 202698 ms
Oct 24, 2026100 ms
Oct 31, 2026105 ms
Nov 7, 2026111 ms
Nov 14, 2026123 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 plantket.cl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. plantket.cl at 0.5 s0.5 s
  2. plantket.cl at 1.0 s1.0 s
  3. plantket.cl at 1.4 s1.4 s
  4. plantket.cl at 1.9 s1.9 s
  5. plantket.cl at 2.4 s2.4 s
  6. plantket.cl at 2.9 s2.9 s
  7. plantket.cl at 3.3 s3.3 s
  8. plantket.cl at 3.8 s3.8 s

Speed

9 to fix61
  • Reduce unused JavaScript

    3.8 s · 800 KiB

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

  • Improve image delivery

    3.1 s · 752 KiB

    8 images could be 752 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.4 s · 442 KiB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.2 s · 143 KiB

    About 143 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • 3,064 HTML elements

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

  • Mobile performance score: 61

    61/100

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

  • Minify CSS

    750 ms · 104 KiB

    104 KiB could be saved by minifying CSS.

  • Main-thread work: 2.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Hotjar and Google Tag Manager and others), adding 534 KiB and 228 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 29 KiB

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

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 15 KiB

    15 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 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.

  • Largest Contentful Paint: 19.5 s

    19.5 s

    Your largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Despacho de plantas gratis”.

  • Time to Interactive: 19.5 s

    19.5 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Real-user INP: 219 ms

    219 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 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.

  • Speed Index: 5.7 s

    5.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 286 ms

    286 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user CLS: 0.06

    0.06

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.8 MB in 102 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 102 requests on a phone: scripts 1.6 MB (43), images 818 KiB (17) and fonts 232 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example herramientas.jpg at 1,600 px wide, shown at 366 px. Resized copies would save about 61 KiB.

  • 3 images in older formats

    3 images (188 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.

  • 3 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.80 g

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

Accessibility

7 to fixGoogle 7990
  • 59 text elements with low contrast

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • 1 image without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

  • 50 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 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 8594
  • Structured data has 2 problems

    Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • 9 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 301 internal links, 9 external

    The homepage links to 301 pages on plantket.cl and 9 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Plantket: marketplace de plantas a domicilio en Santiago y Valparaíso. Plantas de interior, exterior, nativas y frutale…”.

  • One H1 headline

    Your main headline reads: “Plantas a domicilio en Santiago y Valparaíso | Plantket”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Plantas a domicilio en Santiago y Valparaíso | Plantket”.

  • Canonical URL set

    The canonical URL is https://plantket.cl/plantket-cl/.

  • 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://plantket.cl/plantket-cl/sitemap-1-with-images.xml.

AI search readiness

2 to fix70
  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Claude search (Claude-SearchBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

2 checks passed
  • Text is in the HTML

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

  • llms.txt published

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

Other pages

5 to fix76
  • 3 pages share a title

    https://plantket.cl/plantket-cl, https://plantket.cl/plantket-cl/index.php and https://plantket.cl/plantket-cl/carrito all use the title “Plantas a domicilio en Santiago y Valparaíso | Plantket”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://plantket.cl/plantket-cl/module/kbgiftcard/giftcards has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://plantket.cl/plantket-cl/index.php and https://plantket.cl/plantket-cl/carrito use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://plantket.cl/plantket-cl/index.php, whose canonical is https://plantket.cl/plantket-cl. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://plantket.cl/plantket-cl/module/kbgiftcard/giftcards has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://plantket.cl/plantket-cl/productos-rebajados, https://plantket.cl/plantket-cl/mas-vendidos, https://plantket.cl/plantket-cl/36-macetas, https://plantket.cl/plantket-cl/58-maquinas-y-herramientas and https://plantket.cl/plantket-cl/12-plantas-de-interior took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 63 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 84 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 586 words of copy

    The homepage carries about 586 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 9 cookies set on arrival

    9

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 plantket.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
PrestaShop
Analytics
Google Tag Manager | Hotjar
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on plantket.cl, including 20 speed issues, 2 SEO issues and 3 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