Website review, no card needed
casarica.com.py website review
Visit site (opens in a new tab)Reviewed 25 October 202656 issues · 100 checks
This review found 56 issues worth fixing on casarica.com.py, 27 of them high impact, across 100 checks. The most urgent: improve image delivery. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 108 ms |
| May 9, 2026 | 109 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 119 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 121 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 126 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 130 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
0.7 s
1.4 s
2.1 s
2.8 s
3.4 s
4.1 s
4.8 s
5.5 s
Speed
Improve image delivery
2.5 s · 3.0 MB58 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 22
22/100Your mobile performance score is 22 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,532 HTML elements
The page has 6,532 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
860 ms · 556 KiBAbout 556 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 860 ms faster on a phone.
Reduce unused CSS
970 ms · 150 KiBAbout 150 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 970 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.1 MB and 785 ms of main-thread time.
Google Tag Manager adds 543 ms
543 msGoogle Tag Manager costs a phone 543 ms of main-thread work and 801 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 335 ms. During a long task the page ignores taps.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Use efficient cache lifetimes
213 KiB9 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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: 69 ms
69 msYour server sent the HTML in 69 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.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.5 s
26.5 sThe page becomes fully interactive after 26.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.014
1.014The layout shifts by 1.014 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 647 ms
647 msScripts block taps and scrolling for 647 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 926 ms
926 msReal visitors wait 926 ms for your server to start answering (75th percentile). Good is under 800 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 108 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 131 ms
131 msReal visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 11.3 MB in 189 requests
11.3 MBYour homepage downloads 11.3 MB in 189 requests on a phone: images 9.7 MB (147), scripts 1.2 MB (12) and stylesheets 177 KiB (6). Under 2 MB keeps phones on slow connections fast.
40 images in older formats
40 images (4.6 MB) 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.
2 images far larger than shown
161 KiB2 images are downloaded at several times the size a phone draws them, for example dia-itau_3.gif at 1,920 px wide, shown at 390 px. Resized copies would save about 161 KiB.
About 3.2 g of CO₂ per visit
3.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.20 g of CO₂e: 384.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Certain ARIA roles must contain particular children (7 elements)
Certain ARIA roles must contain particular children: 7 elements on the page fail this check, rated critical by axe-core.
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
19 elements hidden from screen readers can still receive keyboard focus.
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (12 elements)
Interactive controls must not be nested: 12 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (7 elements)
ARIA input fields must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
52 images without alt text
52 images have no alt text, which hurts accessibility and image search.
132 form fields without a label
132 form fields have no label, so screen readers announce an empty box and autofill guesses.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (10 elements)
Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 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.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 71 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 20 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
131 links crawlers can't follow
131 links have no real href, so search engines can't follow them.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
1,023 internal links, 13 external
The homepage links to 1,023 pages on casarica.com.py and 13 external pages.
4 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Supermercados CASA RICA: hacé tus compras online sin salir de casa en nuestro super gourmet online con el mejor Deliver…”.
Title: 53 characters
Your title is a healthy 53 characters: “Casa Rica | Supermercados: #1 Compras ONLINE Paraguay”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://casarica.com.py/sitemap.xml.
AI search readiness
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://casarica.com.py/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.
Text is in the HTML
Your server sends the page's text in the HTML (3,398 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://casarica.com.py/productos-exclusivos, https://casarica.com.py/catalogo/carnes-y-platos-de-fondo-c332, https://casarica.com.py/catalogo/empanadas-c325, https://casarica.com.py/catalogo/entradas-y-ensaladas-c326 and https://casarica.com.py/catalogo/pastas-c331 all use the title “CATÁLOGO DE PRODUCTOS”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://casarica.com.py/mapa-de-cobertura, https://casarica.com.py/preguntas-frecuentes, https://casarica.com.py/horarios, https://casarica.com.py/carrito, https://casarica.com.py/productos-exclusivos and https://casarica.com.py/sabores-de-asia and 8 others use the same meta description. A description written for each page earns more clicks.
11 pages without an H1
https://casarica.com.py/carrito, https://casarica.com.py/productos-exclusivos, https://casarica.com.py/sabores-de-asia, https://casarica.com.py/giftcard, https://casarica.com.py/productos-eco and https://casarica.com.py/oktoberfest and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://casarica.com.py/productos-exclusivos took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 199 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
366 of 441 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 1,448 words of copy
The homepage carries about 1,448 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contactános”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
15 other companies contacted
Loading the homepage contacts 15 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 casarica.com.py, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- 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 56 issues on casarica.com.py, including 21 speed issues, 5 SEO issues and 2 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.