Website review, no card needed
alameda.mx website review
Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 68 checks
This review found 29 issues worth fixing on alameda.mx, 8 of them high impact, across 68 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
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Improve image delivery
1.2 s · 489 KiB8 images could be 489 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
300 ms · 70 KiBAbout 70 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.
Minify CSS
17 KiB17 KiB could be saved by minifying CSS.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 93 KiB and 0 ms of main-thread time.
Minify JavaScript
6 KiB6 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.
2 checks passed
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 116 ms of it running JavaScript. That is comfortably low.
Server response: 103 ms
103 msYour server sent the HTML in 103 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.3 s
5.3 sYour largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “22 LB AGENCIA ARTISTA”. Most of its time is resource load delay (2.6 s).
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.3 s
5.3 sThe page becomes fully interactive after 5.3 s. Good is under 3.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0.097
0.097The layout barely moves while loading (CLS 0.097, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
22-LB-AGENCIA-ARTISTA.jpg.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images far larger than shown
372 KiB2 images are downloaded at several times the size a phone draws them, for example ¿Cuales-son-los-dias-festivos-oficiales-en-Mexico.png.webp at 1,024 px wide, shown at 178 px. Resized copies would save about 372 KiB.
About 0.5 g of CO₂ per visit
0.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.47 g of CO₂e: 55.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.6 MB in 71 requests
1.6 MBYour homepage downloads 1.6 MB in 71 requests on a phone: images 1.2 MB (34), scripts 177 KiB (24) and fonts 126 KiB (3). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (50 elements)
All page content should be contained by landmarks: 50 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.
Headings skip levels
Headings skip levels (h3 → h6, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Article, BreadcrumbList, ImageObject and ItemList) but with 1 problem, for example “Organization: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
138 internal links, 0 external
The homepage links to 138 pages on alameda.mx and 0 external pages.
6 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Noticias de Actualidad, Lifestyle, Decoración, Mobiliario, Construcción... ⭐ Además de noticias relacionadas con la Mod…”.
One H1 headline
Your main headline reads: “Revista Alameda | Lifestyle, Decoración y Mucho Más”.
Title: 53 characters
Your title is a healthy 53 characters: “ℹ Revista Alameda | Lifestyle, Decoración y Mucho Más”.
Canonical URL set
The canonical URL is https://alameda.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://alameda.mx/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://alameda.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 (574 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages point its canonical at the homepage
https://alameda.mx/2026/08, https://alameda.mx/2026/06, https://alameda.mx/2026/05, https://alameda.mx/2026/04, https://alameda.mx/2026/03 and https://alameda.mx/2026/01 and 3 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
10 pages share a title
/, https://alameda.mx/2026/08, https://alameda.mx/2026/06, https://alameda.mx/2026/05, https://alameda.mx/2026/04 and https://alameda.mx/2026/03 and 4 others all use the title “ℹ Revista Alameda | Lifestyle, Decoración y Mucho Más”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://alameda.mx/actualidad, https://alameda.mx/decoracion-diy, https://alameda.mx/lifestyle, https://alameda.mx/moda-y-complementos, https://alameda.mx/viajes-turismo and https://alameda.mx/entretenimiento have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages share a meta description
https://alameda.mx/2026/08, https://alameda.mx/2026/06, https://alameda.mx/2026/05, https://alameda.mx/2026/04, https://alameda.mx/2026/03 and https://alameda.mx/2026/01 and 3 others use the same meta description. A description written for each page earns more clicks.
10 pages slow to respond
https://alameda.mx/moda-y-complementos, https://alameda.mx/2026/08, https://alameda.mx/2026/06, https://alameda.mx/2026/05, https://alameda.mx/2026/04 and https://alameda.mx/2026/03 and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 59 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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
22 small tap targets
22 of 55 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
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 468 words of copy
The homepage carries about 468 words of visible text.
1 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 alameda.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on alameda.mx, including 8 speed issues, 2 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.