viceversaoriginal.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

media-amazon.com costs a phone 1.2 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

43 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

8 third-party services load with your homepage (media-amazon.com, cloudfront.net and Amazon Ads and others), adding 4.7 MB and 1.2 s of main-thread time.

About 238 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

15 images could be 325 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

cloudfront.net costs a phone 29 ms of main-thread work and 450 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 311 requests on a phone: scripts 2.4 MB (80), images 1.6 MB (119) and fonts 426 KiB (17). Under 2 MB keeps phones on slow connections fast.

5 images (187 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.

4 images further down the page (151 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

[role] values are not valid (1 element).

All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 24 characters: “Amazon.com.mx: VICEVERSA”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 169 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://www.amazon.com.mx/sitemap.xml, so Google discovers your pages only by following links.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link has no real href, so search engines can't follow it.

The homepage links to 63 pages on viceversaoriginal.com and 11 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

There is no https://www.amazon.com.mx/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Your homepage links to https://www.amazon.com.mx/gp/site-directory, https://www.amazon.com.mx/gp/browse.html, https://www.amazon.com.mx/Tarjetas-de-Regalo-Amazon/b, https://www.amazon.com.mx/computadoras-y-tablets/b, https://www.amazon.com.mx/Herramientas-Mejoras-del-Hogar/b and https://www.amazon.com.mx/stores/page/b/node=6507977011, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.amazon.com.mx/dsv/recharge/welcome has no <title>, so Google invents the link text in results.

https://www.amazon.com.mx/ref=nav_logo declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://www.amazon.com.mx/prime and https://www.amazon.com.mx/dsv/recharge/welcome have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.amazon.com.mx/ref=nav_logo, https://www.amazon.com.mx/deals, https://www.amazon.com.mx/music/unlimited and https://www.amazon.com.mx/fmc/everyday-essentials have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.amazon.com.mx/prime, https://www.amazon.com.mx/dsv/recharge/welcome, https://www.amazon.com.mx/gp/bestsellers and https://www.amazon.com.mx/fmc/everyday-essentials took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 218 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Amazon Ads (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.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.