Website review, no card needed

tetejo.cl logo

tetejo.cl website review

Visit site (opens in a new tab)Reviewed 12 November 202634 issues · 58 checks

This review found 34 issues worth fixing on tetejo.cl, 8 of them high impact, across 58 checks. The most urgent: no call to action on the first screen. 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
1.5 s1.1 sMay 23Jul 41.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.3 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
417 ms70 msMay 23Jul 4377 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026110 ms
May 30, 2026157 ms
Jun 6, 2026272 ms
Jun 13, 2026345 ms
Jun 20, 2026359 ms
Jun 27, 2026360 ms
Jul 4, 2026377 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 tetejo.cl (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix55
  • Mobile performance score: 55

    55/100

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

  • Reduce initial server response time

    715 ms

    Reduce initial server response time. Google estimates savings of 715 ms on a phone.

  • Document request latency

    700 ms

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

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • Server response: 815 ms

    815 ms

    Your server takes 815 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 105 KiB and 0 ms of main-thread time.

  • 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
  • Main-thread work: 0.2 s

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

Core Web Vitals

6 to fix67
  • First Contentful Paint: 17.6 s

    17.6 s

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

  • Largest Contentful Paint: 19.0 s

    19.0 s

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

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 19.0 s

    19.0 s

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

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

    +176%

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Cumulative Layout Shift: 0.016

    0.016

    The layout barely moves while loading (CLS 0.016, 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 fix67
  • Page weight: 3.1 MB in 5 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 5 requests on a phone: HTML 3.0 MB (1), fonts 104 KiB (3) and stylesheets 2 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

Accessibility

4 to fixGoogle 9690
  • All page content should be contained by landmarks (10 elements)

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

  • 6 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 16 automated accessibility rules passed

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

SEO

10 to fixGoogle 8262
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Lanas decalidadpara Chile” and “Lanas decalidadpara España”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 25 links crawlers can't follow

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

  • 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 XML sitemap

    No XML sitemap at https://tetejo.cl/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at tetejo.cl/robots.txt, the first file search crawlers ask for.

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

1 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “Tetejo · Lanas & Accesorios · Catálogo 2026”.

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://tetejo.cl/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

    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.

Best practices

2 to fixGoogle 10074
  • 1 broken image

    1 image failed to load on a phone, for example https://tetejo.cl/.

  • 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 (Not Found)”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 23 words

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

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

2 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: a star rating and 37 trust badges.

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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on tetejo.cl, including 11 speed issues, 10 SEO issues and 5 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