Website review, no card needed

steward.cl logo

steward.cl website review

Visit site (opens in a new tab)Reviewed 23 October 202642 issues · 77 checks

This review found 42 issues worth fixing on steward.cl, 19 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
4.6 s2.6 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.2 s
May 16, 20264.2 s
May 23, 20264.2 s
May 30, 20264.2 s
Jun 6, 20264.4 s
Jun 13, 20264.3 s
Jun 20, 20264.3 s
Jun 27, 20264.3 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20263.9 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.4 s
Aug 29, 20263.3 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
199 ms155 msMay 2Oct 17194 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026161 ms
May 9, 2026161 ms
May 16, 2026160 ms
May 23, 2026161 ms
May 30, 2026164 ms
Jun 6, 2026163 ms
Jun 13, 2026165 ms
Jun 20, 2026167 ms
Jun 27, 2026166 ms
Jul 4, 2026172 ms
Jul 11, 2026176 ms
Jul 18, 2026172 ms
Jul 25, 2026173 ms
Aug 1, 2026174 ms
Aug 8, 2026173 ms
Aug 15, 2026177 ms
Aug 22, 2026179 ms
Aug 29, 2026184 ms
Sep 5, 2026187 ms
Sep 12, 2026186 ms
Sep 19, 2026186 ms
Sep 26, 2026184 ms
Oct 3, 2026187 ms
Oct 10, 2026193 ms
Oct 17, 2026194 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 steward.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix38
  • Improve image delivery

    4.0 s · 1.3 MB

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

  • Render-blocking requests

    3.6 s

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

  • Reduce unused JavaScript

    2.3 s · 422 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 263 KiB

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

  • Reduce unused CSS

    1.1 s · 79 KiB

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

  • Mobile performance score: 38

    38/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 710 KiB and 601 ms of main-thread time.

  • 11 long tasks on the main thread

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

  • Google Tag Manager adds 311 ms

    311 ms

    Google Tag Manager costs a phone 311 ms of main-thread work and 348 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,929 HTML elements

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

  • Main-thread work: 2.7 s

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

  • Legacy JavaScript

    200 ms · 23 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 63 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 41 ms

    41 ms

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

Core Web Vitals

12 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.26

    0.26

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 15.8 s

    15.8 s

    Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Muebles para Restaurantes, Cafeterias y Hoteles”.

  • First Contentful Paint: 7.3 s

    7.3 s

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

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Total Blocking Time: 843 ms

    843 ms

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

  • Real-user LCP: 4.0 s

    4.0 s

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

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

    +20%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • 1 image without width and height

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

3 checks passed
  • Real-user INP: 198 ms

    198 ms

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

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

    -33%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.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

3 to fix58
  • 15 images far larger than shown

    904 KiB

    15 images are downloaded at several times the size a phone draws them, for example 4.webp at 1,250 px wide, shown at 390 px. Resized copies would save about 904 KiB.

  • Page weight: 3.1 MB in 96 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 96 requests on a phone: images 1.7 MB (35), scripts 907 KiB (9) and fonts 302 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    4.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (58 KiB) is 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.

  • About 0.9 g of CO₂ per visit

    0.87 g

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

Accessibility

5 to fixGoogle 9293
  • 13 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • 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 83 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • Structured data has 1 problem

    Structured data found (Organization, WebPage and 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 XML sitemap

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

  • 2 links crawlers can't follow

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

  • 518 internal links, 16 external

    The homepage links to 518 pages on steward.cl and 16 external pages.

5 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Descubre equipamiento gastronómico profesional para hoteles, restaurantes y cafeterías. Soluciones HORECA con despacho …”.

  • One H1 headline

    Your main headline reads: “Equipamiento gastronómico profesional”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Equipamiento Gastronómico | Despacho a todo Chile | Steward”.

  • Canonical URL set

    The canonical URL is https://steward.cl/.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • 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
  • 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.

  • llms.txt published

    The site publishes https://steward.cl/llms.txt (195 KiB, 1,522 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 10093
  • 14 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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

  • Only about 141 words

    The homepage has only about 141 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.

3 checks passed
  • 7 short forms

    7 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 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, Meta Pixel and Microsoft Clarity (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.

  • 7 cookies set on arrival

    7

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 steward.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 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 42 issues on steward.cl, including 23 speed issues, 4 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