Website review, no card needed
tumundototal.com website review
Visit site (opens in a new tab)Reviewed 26 October 202652 issues · 86 checks
This review found 52 issues worth fixing on tumundototal.com, 17 of them high impact, across 86 checks. The most urgent: mobile performance score: 36. 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.2 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 334 ms |
| May 16, 2026 | 331 ms |
| May 23, 2026 | 328 ms |
| May 30, 2026 | 327 ms |
| Jun 6, 2026 | 326 ms |
| Jun 13, 2026 | 324 ms |
| Jun 20, 2026 | 328 ms |
| Jun 27, 2026 | 332 ms |
| Jul 4, 2026 | 339 ms |
| Jul 11, 2026 | 344 ms |
| Jul 18, 2026 | 341 ms |
| Jul 25, 2026 | 340 ms |
| Aug 1, 2026 | 338 ms |
| Aug 8, 2026 | 328 ms |
| Aug 15, 2026 | 315 ms |
| Aug 22, 2026 | 301 ms |
| Aug 29, 2026 | 290 ms |
| Sep 5, 2026 | 285 ms |
| Sep 12, 2026 | 284 ms |
| Sep 19, 2026 | 289 ms |
| Sep 26, 2026 | 291 ms |
| Oct 3, 2026 | 294 ms |
| Oct 10, 2026 | 295 ms |
| Oct 17, 2026 | 296 ms |
| Oct 24, 2026 | 296 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.8 s
1.5 s
2.3 s
3.0 s
3.8 s
4.6 s
5.3 s
6.1 s
Speed
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (vtexassets.com, tikket.net and Google Tag Manager and others), adding 4.1 MB and 1.7 s of main-thread time.
Use efficient cache lifetimes
600 ms · 785 KiB20 files are served with short cache lifetimes, so returning visitors download them again (785 KiB).
vtexassets.com adds 740 ms
740 msvtexassets.com costs a phone 740 ms of main-thread work and 2.8 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.
Reduce initial server response time
620 msReduce initial server response time. Google estimates savings of 620 ms on a phone.
Document request latency
600 msThe HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused JavaScript
557 KiBAbout 557 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
380 ms · 171 KiBAbout 171 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 380 ms faster on a phone.
tikket.net adds 350 ms
350 mstikket.net costs a phone 350 ms of main-thread work and 535 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: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Google Tag Manager adds 263 ms
263 msGoogle Tag Manager costs a phone 263 ms of main-thread work and 316 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.
Server response: 720 ms
720 msYour server takes 720 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Improve image delivery
226 KiB4 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 206 ms. During a long task the page ignores taps.
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
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.50
0.50For real visitors the layout shifts by 0.50 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.4 s
10.4 sYour largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Freidora de Aire 3.8 Litros 1350W”.
Time to Interactive: 23.0 s
23.0 sThe page becomes fully interactive after 23.0 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.389
0.389The layout shifts by 0.389 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 291 ms
291 msReal visitors wait 291 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 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.
Total Blocking Time: 342 ms
342 msScripts block taps and scrolling for 342 ms in total while the page loads. Good is under 200 ms.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 334 ms to 296 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
1 image over 500 KB
4f439f27-ff73-4b39-9a22-cbf0b84384a1___6da3a7cf968b594c9068a weighs 510 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.9 MB in 146 requests
3.9 MBYour homepage downloads 3.9 MB in 146 requests on a phone: scripts 1.7 MB (70), images 1.4 MB (25) and other files 411 KiB (37). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
13 KiB1 image is downloaded at several times the size a phone draws it, for example 266283-500-auto at 500 px wide, shown at 153 px. Resized copies would save about 13 KiB.
2 images in older formats
2 images (116 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.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 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.
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 12 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 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Mundo Total | Tienda online de electrodomésticos, moda, belleza, hogar y tecnología”.
Structured data has 1 problem
Structured data found (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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
18 internal links, 1 external
The homepage links to 18 pages on tumundototal.com and 1 external page.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Compra en Mundo Total, tu tienda online de hogar, tecnología, moda y belleza. Disfruta de envío rápido, promociones exc…”.
One H1 headline
Your main headline reads: “Mundo Total: Tu Destino Online para Hogar, Tecnología, Moda y Belleza en Venezuela”.
Canonical URL set
The canonical URL is https://www.tumundototal.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.tumundototal.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.tumundototal.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
10 pages without a title
https://www.tumundototal.com/ofertas, https://www.tumundototal.com/hisense, https://www.tumundototal.com/admiral, https://www.tumundototal.com/as-electronic, https://www.tumundototal.com/kimbeauty and https://www.tumundototal.com/premier and 4 others have no <title>, so Google invents the link text in results.
10 pages without a meta description
https://www.tumundototal.com/ofertas, https://www.tumundototal.com/hisense, https://www.tumundototal.com/admiral, https://www.tumundototal.com/as-electronic, https://www.tumundototal.com/kimbeauty and https://www.tumundototal.com/premier and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.tumundototal.com/ofertas, https://www.tumundototal.com/hisense, https://www.tumundototal.com/admiral, https://www.tumundototal.com/as-electronic, https://www.tumundototal.com/kimbeauty and https://www.tumundototal.com/premier and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.tumundototal.com/ofertas, https://www.tumundototal.com/premier and https://www.tumundototal.com/renvill took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 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
18 small tap targets
18 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.
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 73 words
The homepage has only about 73 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.
17 cookies set on arrival
17Opening the homepage sets 17 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.
34 other companies contacted
Loading the homepage contacts 34 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 tumundototal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on tumundototal.com, including 27 speed issues, 3 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.