Website review, no card needed
climaproyectos.com.mx website review
Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 84 checks
This review found 37 issues worth fixing on climaproyectos.com.mx, 17 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. 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
79C- #55,337 of 123,862 reviewed websitesbeats 50%
- #36,394 of 69,698 online storesbeats 42%
- #807 of 2,896 WooCommerce storesbeats 68%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.5 s |
| May 9, 2026 | 5.5 s |
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.5 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 5.7 s |
| Jun 20, 2026 | 5.7 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.6 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.7 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.8 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.7 s |
| Sep 12, 2026 | 5.6 s |
| Sep 19, 2026 | 5.6 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.6 s |
| Oct 17, 2026 | 5.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 196 ms |
| May 9, 2026 | 192 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 199 ms |
| Jun 20, 2026 | 197 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 201 ms |
| Jul 11, 2026 | 200 ms |
| Jul 18, 2026 | 200 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 214 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 245 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 249 ms |
| Sep 19, 2026 | 251 ms |
| Sep 26, 2026 | 256 ms |
| Oct 3, 2026 | 260 ms |
| Oct 17, 2026 | 249 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
Use efficient cache lifetimes
3.1 s · 10.7 MB13 files are served with short cache lifetimes, so returning visitors download them again (10.7 MB).
Improve image delivery
4.8 s · 3.1 MB9 images could be 3.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.8 s faster on a phone.
Render-blocking requests
1.7 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.7 s.
Reduce unused CSS
1.1 s · 152 KiBAbout 152 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 68
68/100Your mobile performance score is 68 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
1,799 HTML elements
The page has 1,799 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 76 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 29 ms of it running JavaScript. That is comfortably low.
Server response: 73 ms
73 msYour server sent the HTML in 73 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.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.3 s
5.3 sReal visitors see the first content after 5.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 16.0 s
16.0 sYour largest element takes 16.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “cover_residencial_web”.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Tap response (INP) got 31% slower for real visitors
+31%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 196 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.5 s to 5.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 171 ms
171 msReal visitors wait 171 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, 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
Page weight: 12.8 MB in 17 requests
12.8 MBYour homepage downloads 12.8 MB in 17 requests on a phone: media 8.6 MB (2), images 3.9 MB (10) and stylesheets 168 KiB (1). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (456 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
54 KiB1 image is downloaded at several times the size a phone draws it, for example bosch-logo-simple.svg at 10,417 px wide, shown at 57 px. Resized copies would save about 54 KiB.
3 images in older formats
3 images (288 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 3.6 g of CO₂ per visit
3.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
16 tap targets too small
16 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 (28 elements)
All page content should be contained by landmarks: 28 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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
44 links without text
44 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 69 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 4 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.
Structured data has 1 problem
Structured data found (FAQPage, HVACBusiness, ImageObject and Organization) but with 1 problem, for example “VideoObject: hasPart is an empty list”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
109 internal links, 34 external
The homepage links to 109 pages on climaproyectos.com.mx and 34 external pages.
6 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Climaproyectos: líder en aire acondicionado. Encuentra equipos Midea, York, Samsung y Carrier con entrega inmediata ¡De…”.
Title: 64 characters
Your title is a healthy 64 characters: “Climaproyectos | Distribuidor Mayorista #1 de Aire Acondicionado”.
Canonical URL set
The canonical URL is https://climaproyectos.com.mx/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://climaproyectos.com.mx/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (975 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://climaproyectos.com.mx/llms.txt (53 KiB, 155 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://climaproyectos.com.mx/tipos/aplicado and https://climaproyectos.com.mx/tipos/vrf have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://climaproyectos.com.mx/tipos/residencial, https://climaproyectos.com.mx/tipos/comercial, https://climaproyectos.com.mx/tipos/aplicado, https://climaproyectos.com.mx/tipos/vrf and https://climaproyectos.com.mx/tipos/outlet-de-equipos-hvac have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://climaproyectos.com.mx/tipos/outlet-de-equipos-hvac, https://climaproyectos.com.mx/climatizacion-de-centros-comerciales, https://climaproyectos.com.mx/climatizacion-de-complejos-residenciales, https://climaproyectos.com.mx/climatizacion-de-edificios-verticales, https://climaproyectos.com.mx/climatizacion-de-hospitales and https://climaproyectos.com.mx/aire-acondicionado-para-hoteles took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
5 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 777 words of copy
The homepage carries about 777 words of visible text.
6 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
8 other companies contacted
Loading the homepage contacts 8 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 climaproyectos.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
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on climaproyectos.com.mx, including 16 speed issues, 3 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.