Website review, no card needed
desarrollosecopsa.com website review
Visit site (opens in a new tab)Reviewed 24 October 202648 issues · 92 checks
This review found 48 issues worth fixing on desarrollosecopsa.com, 22 of them high impact, across 92 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.0 s |
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.5 s |
| Jul 4, 2026 | 5.5 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 6.0 s |
| Aug 1, 2026 | 6.2 s |
| Aug 8, 2026 | 6.4 s |
| Aug 15, 2026 | 6.3 s |
| Aug 22, 2026 | 6.2 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 111 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 115 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 173 ms |
| Jul 11, 2026 | 168 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 165 ms |
| Aug 15, 2026 | 174 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 190 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 161 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 17, 2026 | 133 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.3 s
2.7 s
4.0 s
5.3 s
6.6 s
8.0 s
9.3 s
10.6 s
Speed
Use efficient cache lifetimes
27.4 s · 20.9 MB149 files are served with short cache lifetimes, so returning visitors download them again (20.9 MB).
Improve image delivery
18.7 s · 20.0 MB11 images could be 20.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 18.7 s faster on a phone.
Reduce unused JavaScript
6.0 s · 2.4 MBAbout 2.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.
Render-blocking requests
8.0 s67 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.0 s.
Minify JavaScript
2.4 s · 519 KiB519 KiB could be saved by minifying JavaScript.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.0 s
A phone's processor spends 8.0 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Google CDN and Google Maps and others), adding 2.5 MB and 1.2 s of main-thread time.
Reduce unused CSS
750 ms · 146 KiBAbout 146 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 448 ms. During a long task the page ignores taps.
Facebook adds 378 ms
378 msFacebook costs a phone 378 ms of main-thread work and 309 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.
leadconnectorhq.com adds 177 ms
177 msleadconnectorhq.com costs a phone 177 ms of main-thread work and 1.0 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.
Google CDN adds 218 ms
218 msGoogle CDN costs a phone 218 ms of main-thread work and 351 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.
Google Maps adds 193 ms
193 msGoogle Maps costs a phone 193 ms of main-thread work and 389 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.
1,924 HTML elements
The page has 1,924 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 127 ms
127 msGoogle Tag Manager costs a phone 127 ms of main-thread work and 354 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.
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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 CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.5 s
8.5 sThe first text or image appears after 8.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 44.4 s
44.4 sYour largest element takes 44.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Herov2”.
Speed Index: 37.9 s
37.9 sVisually, the page fills in at 37.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 125.7 s
125.7 sThe page becomes fully interactive after 125.7 s. Good is under 3.8 s.
Total Blocking Time: 1.9 s
1.9 sScripts block taps and scrolling for 1.9 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 111 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
4 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 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.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.0 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 35.5 MB in 314 requests
35.5 MBYour homepage downloads 35.5 MB in 314 requests on a phone: images 27.9 MB (43), scripts 5.0 MB (133) and other files 1.2 MB (42). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (171 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.
3 images below the first screen load straight away
3 images further down the page (193 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 10.1 g of CO₂ per visit
10.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.07 g of CO₂e: 1208.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
6 links without text
6 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 50 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (25 characters)
Your title is only 25 characters: “Home - ECOPSA Desarrollos”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
87 internal links, 12 external
The homepage links to 87 pages on desarrollosecopsa.com and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Inversiones inmobiliarias seguras en el Sureste de México”.
Canonical URL set
The canonical URL is https://desarrollosecopsa.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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://desarrollosecopsa.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://desarrollosecopsa.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.
3 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,485 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://desarrollosecopsa.com/ecopsa-capital, https://desarrollosecopsa.com/desarrollos-residenciales, https://desarrollosecopsa.com/punta-misne, https://desarrollosecopsa.com/zuluz_terrenos_residenciales_en_merida, https://desarrollosecopsa.com/makaro and https://desarrollosecopsa.com/cabo-coral-terrenos and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://desarrollosecopsa.com/empresa, https://desarrollosecopsa.com/desarrollos-residenciales, https://desarrollosecopsa.com/makaro, https://desarrollosecopsa.com/cabo-coral-terrenos, https://desarrollosecopsa.com/desarrollos-semiurbanizados and https://desarrollosecopsa.com/departamentos and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 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
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
19 of 22 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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 741 words of copy
The homepage carries about 741 words of visible text.
2 checks passed
5 short forms
5 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
22 other companies contacted
Loading the homepage contacts 22 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 desarrollosecopsa.com, 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 © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on desarrollosecopsa.com, including 27 speed issues, 3 SEO issues and 6 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.