Website review, no card needed
indurama.com website review
Visit site (opens in a new tab)Reviewed 3 November 202655 issues · 92 checks
This review found 55 issues worth fixing on indurama.com, 20 of them high impact, across 92 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 185 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 185 ms |
| Jun 13, 2026 | 184 ms |
| Jun 20, 2026 | 185 ms |
| Jun 27, 2026 | 185 ms |
| Jul 4, 2026 | 185 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 184 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 186 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 184 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 188 ms |
| Oct 3, 2026 | 188 ms |
| Oct 10, 2026 | 189 ms |
| Oct 17, 2026 | 192 ms |
| Oct 24, 2026 | 190 ms |
| Oct 31, 2026 | 187 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
3.0 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Document request latency
1.0 sThe HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce initial server response time
1.0 sReduce initial server response time. Google estimates savings of 1.0 s on a phone.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Google CDN and others), adding 3.3 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
150 ms · 925 KiBAbout 925 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
vtexassets.com adds 572 ms
572 msvtexassets.com costs a phone 572 ms of main-thread work and 1.6 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.
Use efficient cache lifetimes
662 KiB29 files are served with short cache lifetimes, so returning visitors download them again (662 KiB).
Improve image delivery
545 KiB10 images could be 545 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 337 ms
337 msGoogle Tag Manager costs a phone 337 ms of main-thread work and 516 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.
Google CDN adds 286 ms
286 msGoogle CDN costs a phone 286 ms of main-thread work and 737 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Server response: 1.1 s
1.1 sYour server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Reduce unused CSS
290 ms · 60 KiBAbout 60 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Legacy JavaScript
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
Minify JavaScript
37 KiB37 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.
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 CLS: 0.38
0.38For real visitors the layout shifts by 0.38 (75th percentile). Good is under 0.1.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “refrigeración, refrigerador, refrigeradora empotrables , el…”.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.229
0.229The layout shifts by 0.229 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 382 ms
382 msScripts block taps and scrolling for 382 ms in total while the page loads. Good is under 200 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) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 185 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.9 MB in 143 requests
3.9 MBYour homepage downloads 3.9 MB in 143 requests on a phone: scripts 2.2 MB (50), images 939 KiB (29) and other files 365 KiB (24). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (216 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (110 KiB) 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.
About 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 133.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
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.
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 41 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 11 failed. 6 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.
Meta description is short (38 characters)
Your meta description is only 38 characters: “Tienda de electrodomésticos | Indurama”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (ItemList 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
48 internal links, 9 external
The homepage links to 48 pages on indurama.com and 9 external pages.
4 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Tienda de electrodomésticos | Indurama”.
Canonical URL set
The canonical URL is https://www.indurama.com/.
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.indurama.com/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://www.indurama.com/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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
2 pages without a title
https://www.indurama.com/electrohogar and https://www.indurama.com/electrohogar/cocinas-y-empotrables have no <title>, so Google invents the link text in results.
2 pages without a meta description
https://www.indurama.com/electrohogar and https://www.indurama.com/electrohogar/cocinas-y-empotrables have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.indurama.com/electrohogar, https://www.indurama.com/outlet and https://www.indurama.com/electrohogar/cocinas-y-empotrables have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.indurama.com/ofertas, https://www.indurama.com/electrohogar, https://www.indurama.com/electrohogar/cocinas-y-empotrables, https://www.indurama.com/electrohogar/electromenores-de-cocina and https://www.indurama.com/electrohogar/cuidado-del-hogar/aspiradoras took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
9 small tap targets
9 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 125 words
The homepage has only about 125 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.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
21 other companies contacted
Loading the homepage contacts 21 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 indurama.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on indurama.com, including 26 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.