Website review, no card needed
lamarina.com.mx website review
Visit site (opens in a new tab)Reviewed 26 October 202661 issues · 97 checks
This review found 61 issues worth fixing on lamarina.com.mx, 25 of them high impact, across 97 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
58FClosest 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 | 3.9 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.6 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 280 ms |
| May 16, 2026 | 302 ms |
| May 23, 2026 | 319 ms |
| May 30, 2026 | 341 ms |
| Jun 6, 2026 | 346 ms |
| Jun 13, 2026 | 341 ms |
| Jun 20, 2026 | 338 ms |
| Jun 27, 2026 | 330 ms |
| Jul 4, 2026 | 323 ms |
| Jul 11, 2026 | 318 ms |
| Jul 18, 2026 | 316 ms |
| Jul 25, 2026 | 324 ms |
| Aug 1, 2026 | 342 ms |
| Aug 8, 2026 | 364 ms |
| Aug 15, 2026 | 383 ms |
| Aug 22, 2026 | 397 ms |
| Aug 29, 2026 | 393 ms |
| Sep 5, 2026 | 383 ms |
| Sep 12, 2026 | 373 ms |
| Sep 19, 2026 | 356 ms |
| Sep 26, 2026 | 351 ms |
| Oct 3, 2026 | 346 ms |
| Oct 10, 2026 | 343 ms |
| Oct 17, 2026 | 340 ms |
| Oct 24, 2026 | 328 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.7 s
3.3 s
5.0 s
6.7 s
8.3 s
10.0 s
11.7 s
13.3 s
Speed
Render-blocking requests
3.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
vtexassets.com adds 2.7 s
2.7 svtexassets.com costs a phone 2.7 s of main-thread work and 2.9 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.
Google CDN adds 2.0 s
2.0 sGoogle CDN costs a phone 2.0 s of main-thread work and 1.4 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.
Main-thread work: 15.7 s
A phone's processor spends 15.7 s on main-thread work while loading, 9.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 534 KiB 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.
Mobile performance score: 24
24/100Your mobile performance score is 24 (desktop: 46). 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, Google CDN and Google Tag Manager and others), adding 5.3 MB and 7.2 s of main-thread time.
Reduce unused JavaScript
900 ms · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Improve image delivery
350 ms · 1.3 MB41 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Use efficient cache lifetimes
500 ms · 330 KiB27 files are served with short cache lifetimes, so returning visitors download them again (330 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 504 ms. During a long task the page ignores taps.
TikTok adds 428 ms
428 msTikTok costs a phone 428 ms of main-thread work and 156 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.
Reduce unused CSS
300 ms · 80 KiBAbout 80 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.
Legacy JavaScript
300 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Other Google APIs/SDKs adds 295 ms
295 msOther Google APIs/SDKs costs a phone 295 ms of main-thread work and 61 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.
2,381 HTML elements
The page has 2,381 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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 JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 44 ms
44 msYour server sent the HTML in 44 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: 14.6 s
14.6 sYour largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Celulares con 24 Mensualidades congeladas”.
Total Blocking Time: 4.9 s
4.9 sScripts block taps and scrolling for 4.9 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 34.3 s
34.3 sThe page becomes fully interactive after 34.3 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
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 INP: 440 ms
440 msReal visitors wait 440 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 881 ms
881 msReal visitors wait 881 ms for your server to start answering (75th percentile). Good is under 800 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 280 ms to 328 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.08
0.08The layout barely moves while loading (CLS 0.08, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 205 requests
6.5 MBYour homepage downloads 6.5 MB in 205 requests on a phone: scripts 3.1 MB (62), images 1.9 MB (77) and other files 735 KiB (48). Under 2 MB keeps phones on slow connections fast.
17 images below the first screen load straight away
17 images further down the page (982 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images far larger than shown
127 KiB5 images are downloaded at several times the size a phone draws them, for example f0f377e6-12a9-4182-9740-8badd43e7288___88b606f025c9dc511570d at 580 px wide, shown at 164 px. Resized copies would save about 127 KiB.
1 image in older formats
1 image (63 KiB) is 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.8 g of CO₂ per visit
1.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.85 g of CO₂e: 221.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
11 buttons without a name
11 buttons have no accessible name, so screen readers announce just “button”.
37 tap targets too small
37 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.
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.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 failed. 2 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.
Title is short (26 characters)
Your title is only 26 characters: “La Marina va con tu estilo”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
216 internal links, 21 external
The homepage links to 216 pages on lamarina.com.mx and 21 external pages.
4 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “La Marina tienda en línea | Compra tecnología, línea blanca, mueblería y mucho más para tu hogar. Llena a toda tu famil…”.
Canonical URL set
The canonical URL is https://www.lamarina.com.mx/.
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.lamarina.com.mx/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.lamarina.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.
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 (565 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages are broken
Your homepage links to https://www.lamarina.com.mx/telefonia/equipos/la-marina, https://www.lamarina.com.mx/electronica/audio-y-video/pantallas/la-marina, https://www.lamarina.com.mx/computo-y-videojuegos/equipos-computo/la-marina and https://www.lamarina.com.mx/electronica/audio-y-video/bocinas/la-marina, which answer with an error. Visitors hit a dead end and search engines drop them.
2 linked pages hidden from search
https://www.lamarina.com.mx/mundo-gamer and https://www.lamarina.com.mx/audifonos are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
9 pages share a meta description
https://www.lamarina.com.mx/wishlist, https://www.lamarina.com.mx/promociones, https://www.lamarina.com.mx/lo-mas-nuevo-lm, https://www.lamarina.com.mx/exclusivo-en-linea, https://www.lamarina.com.mx/mundo-gamer and https://www.lamarina.com.mx/contacto and 3 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.lamarina.com.mx/promociones, whose canonical is https://www.lamarina.com.mx/promociones-legales. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.lamarina.com.mx/wishlist, https://www.lamarina.com.mx/exclusivo-en-linea, https://www.lamarina.com.mx/electronica/audio-y-video/pantallas, https://www.lamarina.com.mx/mundo-gamer, https://www.lamarina.com.mx/contacto and https://www.lamarina.com.mx/envios-devoluciones-cancelaciones and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.lamarina.com.mx/lo-mas-nuevo-lm, https://www.lamarina.com.mx/exclusivo-en-linea, https://www.lamarina.com.mx/electronica/audio-y-video/pantallas, https://www.lamarina.com.mx/mundo-gamer and https://www.lamarina.com.mx/audifonos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 11 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
3 broken images
3 images failed to load on a phone, for example https://www.lamarina.com.mx/.
29 small tap targets
29 of 120 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 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 289 words of copy
The homepage carries about 289 words of visible text.
3 checks passed
1 short form
A short form (5 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
30 other companies contacted
Loading the homepage contacts 30 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 lamarina.com.mx, 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 Tag Manager
- Hosting
- CloudFront
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 61 issues on lamarina.com.mx, including 27 speed issues, 5 SEO issues 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.