Website review, no card needed
casasilva.cl website review
Visit site (opens in a new tab)Reviewed 1 November 202624 issues · 65 checks
This review found 24 issues worth fixing on casasilva.cl, 11 of them high impact, across 65 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75C- #81,350 of 124,300 reviewed websitesbeats 30%
- #51,598 of 69,848 online storesbeats 22%
- #1,422 of 2,910 WooCommerce storesbeats 45%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.4 s |
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.1 s |
| May 30, 2026 | 6.1 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 6.0 s |
| Jun 20, 2026 | 6.3 s |
| Jun 27, 2026 | 6.2 s |
| Jul 4, 2026 | 6.0 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.0 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 6.3 s |
| Aug 15, 2026 | 6.3 s |
| Aug 22, 2026 | 6.4 s |
| Aug 29, 2026 | 6.3 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.4 s |
| Sep 26, 2026 | 6.4 s |
| Oct 3, 2026 | 6.4 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.0 s |
| Oct 24, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 86 ms |
| May 16, 2026 | 87 ms |
| May 23, 2026 | 86 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 84 ms |
| Jun 20, 2026 | 86 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 87 ms |
| Aug 8, 2026 | 86 ms |
| Aug 15, 2026 | 87 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 88 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 86 ms |
| Sep 19, 2026 | 86 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 91 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 93 ms |
| Oct 24, 2026 | 93 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
How it loaded on a phone
1.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.8 s
7.8 s
Speed
Render-blocking requests
3.3 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Font display
750 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).
Reduce unused JavaScript
300 ms · 65 KiBAbout 65 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.
Reduce unused CSS
300 ms · 61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,661 HTML elements
The page has 1,661 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google/Doubleclick Ads), adding 148 KiB and 132 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 88 ms. During a long task the page ignores taps.
Improve image delivery
28 KiB2 images could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 679 ms of it running JavaScript. That is comfortably low.
Server response: 112 ms
112 msYour server sent the HTML in 112 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 8.1 s
8.1 sReal visitors wait 8.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.6 s
5.6 sReal visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.0 s
5.0 sReal visitors wait 5.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.3 s
13.3 sYour largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 86 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.4 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 38 ms
38 msScripts block the page for only 38 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.4 MB in 171 requests
3.4 MBYour homepage downloads 3.4 MB in 171 requests on a phone: images 2.5 MB (50), scripts 424 KiB (50) and fonts 338 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
22 links without text
22 links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 63 images in the HTML carry an alt attribute.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Casa Silva - Inicio”. Between 30 and 65 characters leaves room to say what you do and for whom.
217 internal links, 5 external
The homepage links to 217 pages on casasilva.cl and 5 external pages.
7 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “La familia Silva tiene sus orígenes en el Valle de Colchagua, y desde ahí, proyecta diariamente su trabajo al resto del…”.
One H1 headline
Your main headline reads: “V i ñ a C a s a S i l v a . M e j o r v i ñ a 2 0 2 2 . V i n o C h i l e n o”.
Canonical URL set
The canonical URL is https://www.casasilva.cl/.
Structured data in place
Structured data found: Article, ImageObject, LiquorStore, Organization and Person.
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://www.casasilva.cl/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.casasilva.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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Other pages
7 linked pages are broken
Your homepage links to https://www.casasilva.cl/sustentabilidad, https://www.casasilva.cl/blog, https://www.casasilva.cl/contacto, https://www.casasilva.cl/en, https://www.casasilva.cl/pt-br and https://www.casasilva.cl/producto/vino-blanco-casa-silva-lago-ranco-sauvignon-blanc and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page slow to respond
https://www.casasilva.cl/nuestros-terroirs took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
6 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
5 console errors
5 errors were logged to the browser console during Google's test (“Access to font at 'https://casasilva.cl/wp-content/uploads/2020/03/Alata-Regular.woff' from origin …”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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 552 words of copy
The homepage carries about 552 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
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 casasilva.cl, 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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- Combell
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on casasilva.cl, including 15 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.