Programmable

Website review, no card needed

kallan.com.br logo

kallan.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202626 issues · 59 checks

This review found 26 issues worth fixing on kallan.com.br, 16 of them high impact, across 59 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

Site score

72C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
7.8 s1.2 sMay 9Oct 247.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.6 s
Jul 4, 20265.0 s
Jul 11, 20265.9 s
Jul 18, 20266.0 s
Jul 25, 20265.9 s
Aug 1, 20265.9 s
Aug 8, 20266.0 s
Aug 15, 20266.1 s
Aug 22, 20266.2 s
Aug 29, 20266.4 s
Sep 5, 20266.5 s
Sep 12, 20266.6 s
Sep 19, 20266.7 s
Sep 26, 20266.8 s
Oct 3, 20266.8 s
Oct 10, 20266.9 s
Oct 17, 20266.9 s
Oct 24, 20267.0 s
Real-visitor tap response (INP)75th percentile, phones
197 ms93 msMay 9Oct 24106 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026183 ms
May 16, 2026183 ms
May 23, 2026185 ms
May 30, 2026184 ms
Jun 6, 2026181 ms
Jun 13, 2026181 ms
Jun 20, 2026177 ms
Jun 27, 2026157 ms
Jul 4, 2026118 ms
Jul 11, 2026106 ms
Jul 18, 2026105 ms
Jul 25, 2026105 ms
Aug 1, 2026106 ms
Aug 8, 2026107 ms
Aug 15, 2026107 ms
Aug 22, 2026106 ms
Aug 29, 2026106 ms
Sep 5, 2026106 ms
Sep 12, 2026106 ms
Sep 19, 2026106 ms
Sep 26, 2026106 ms
Oct 3, 2026106 ms
Oct 10, 2026106 ms
Oct 17, 2026107 ms
Oct 24, 2026106 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

www.kallan.com.br (opens in a new tab)
Full-page screenshot of kallan.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kallan.com.br at 1.2 s1.2 s
  2. kallan.com.br at 2.4 s2.4 s
  3. kallan.com.br at 3.7 s3.7 s
  4. kallan.com.br at 4.9 s4.9 s
  5. kallan.com.br at 6.1 s6.1 s
  6. kallan.com.br at 7.3 s7.3 s
  7. kallan.com.br at 8.5 s8.5 s
  8. kallan.com.br at 9.7 s9.7 s

Speed

8 to fix55

  • Use efficient cache lifetimes

    6.2 s · 4.5 MB

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

  • Improve image delivery

    1.8 s · 6.1 MB

    14 images could be 6.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    6.1 s

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

  • Reduce unused CSS

    1.4 s · 441 KiB

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

  • Mobile performance score: 55

    55/100

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

  • Reduce unused JavaScript

    300 ms · 604 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (elfsight.com, Google Fonts and Instagram), adding 4.3 MB and 8 ms of main-thread time.

  • Instagram adds 0 ms

    0 ms

    Instagram costs a phone 0 ms of main-thread work and 4.2 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.

  • Minify CSS

    150 ms · 25 KiB

    25 KiB could be saved by minifying CSS.

  • Document request latency

    90 KiB

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

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

2 checks passed

  • Main-thread work: 0.6 s

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

  • Server response: 423 ms

    423 ms

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

Core Web Vitals

9 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: 7.0 s

    7.0 s

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

  • Real-user FCP: 6.7 s

    6.7 s

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

  • Real-user TTFB: 5.7 s

    5.7 s

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

  • Speed Index: 18.1 s

    18.1 s

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

  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (5.8 s).

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Time to Interactive: 8.7 s

    8.7 s

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

  • Largest content (LCP) got 256% slower for real visitors

    +256%

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

5 checks passed

  • Real-user INP: 105 ms

    105 ms

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

  • Tap response (INP) got 42% faster for real visitors

    -42%

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

  • Cumulative Layout Shift: 0.064

    0.064

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix33

  • Page weight: 8.5 MB in 92 requests

    8.5 MB

    Your homepage downloads 8.5 MB in 92 requests on a phone: images 6.7 MB (31), scripts 999 KiB (20) and stylesheets 616 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • About 2.4 g of CO₂ per visit

    2.40 g

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

Accessibility

2 to fixGoogle 9583

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

2 checks passed

  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 3 automated accessibility rules passed

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

SEO

2 to fixGoogle 10086

  • No H1 headline

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

  • No robots.txt

    There is no robots.txt at kallan.com.br/robots.txt, the first file search crawlers ask for.

  • 27 internal links, 12 external

    The homepage links to 27 pages on kallan.com.br and 12 external pages.

6 checks passed

  • Meta description: 157 characters

    Your meta description is 157 characters: “Kallan Calçados - Compre calçados femininos, masculinos e infantis. Tênis, sandálias, botas, bolsas e perfumes com conf…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Kallan Calçados - Tênis, Sandálias, Botas, Bolsas e Perfumes”.

  • Canonical URL set

    The canonical URL is https://www.kallan.com.br/.

  • Structured data in place

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kallan.com.br/sitemap.xml.

AI search readiness

100

  • No llms.txt

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

2 checks passed

  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

Best practices

Google 100100
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

4 to fix40

  • 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 386 words of copy

    The homepage carries about 386 words of visible text.

1 checks passed

  • Direct contact links

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

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 kallan.com.br, 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
Hosting
Servicos de Internet SA

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on kallan.com.br, including 17 speed issues, 2 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