Website review, no card needed
assetplan.cl website review
Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 85 checks
This review found 39 issues worth fixing on assetplan.cl, 17 of them high impact, across 85 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 338 ms |
| May 16, 2026 | 352 ms |
| May 23, 2026 | 362 ms |
| May 30, 2026 | 351 ms |
| Jun 6, 2026 | 345 ms |
| Jun 13, 2026 | 346 ms |
| Jun 20, 2026 | 347 ms |
| Jun 27, 2026 | 355 ms |
| Jul 4, 2026 | 367 ms |
| Jul 11, 2026 | 376 ms |
| Jul 18, 2026 | 390 ms |
| Jul 25, 2026 | 409 ms |
| Aug 1, 2026 | 417 ms |
| Aug 8, 2026 | 434 ms |
| Aug 15, 2026 | 444 ms |
| Aug 22, 2026 | 453 ms |
| Aug 29, 2026 | 460 ms |
| Sep 5, 2026 | 457 ms |
| Sep 12, 2026 | 455 ms |
| Sep 19, 2026 | 450 ms |
| Sep 26, 2026 | 441 ms |
| Oct 3, 2026 | 420 ms |
| Oct 10, 2026 | 394 ms |
| Oct 17, 2026 | 384 ms |
| Oct 24, 2026 | 379 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
4.5 s · 1.3 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Reduce unused JavaScript
3.9 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 1.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.
Mobile performance score: 32
32/100Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.6 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 (Google Tag Manager, Facebook and TikTok and others), adding 1.8 MB and 1.9 s of main-thread time.
Improve image delivery
700 ms · 477 KiB18 images could be 477 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 483 ms. During a long task the page ignores taps.
Facebook adds 340 ms
340 msFacebook costs a phone 340 ms of main-thread work and 255 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.
Render-blocking requests
350 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Legacy JavaScript
250 ms · 60 KiBPolyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 48 KiBAbout 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.6 s
18.6 sYour largest element takes 18.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner principal”.
Time to Interactive: 24.8 s
24.8 sThe page becomes fully interactive after 24.8 s. Good is under 3.8 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 293 ms
293 msReal visitors wait 293 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 338 ms to 379 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 797 ms
797 msReal visitors wait 797 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 111 requests
3.9 MBYour homepage downloads 3.9 MB in 111 requests on a phone: scripts 2.4 MB (37), images 692 KiB (29) and fonts 681 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
73 KiB1 image is downloaded at several times the size a phone draws it, for example banner-home.webp at 2,560 px wide, shown at 390 px. Resized copies would save about 73 KiB.
12 images below the first screen load straight away
12 images further down the page (345 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (163 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 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 132.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
36 tap targets too small
36 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (78 elements)
All page content should be contained by landmarks: 78 elements on the page fail this check, rated moderate by axe-core.
89 form fields without a label
89 form fields have no label, so screen readers announce an empty box and autofill guesses.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (89 characters)
Your title is 89 characters, so Google will cut it off around 60: “Arriendo y gestión inmobiliaria | Arrienda 100% online | Assetplan | Arrienda 100% Online”.
94 internal links, 29 external
The homepage links to 94 pages on assetplan.cl and 29 external pages.
7 checks passed
Meta description: 89 characters
Your meta description is 89 characters: “Arriendo y gestión inmobiliaria | Arrienda 100% online | Assetplan | Arrienda 100% Online”.
One H1 headline
Your main headline reads: “¡Tremendo arriendo!”.
Canonical URL set
The canonical URL is https://www.assetplan.cl/.
Structured data in place
Structured data found: Organization 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://www.assetplan.cl/sitemap.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (505 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.assetplan.cl/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.assetplan.cl/terminos-y-condiciones and https://www.assetplan.cl/politica-de-privacidad are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a meta description
https://www.assetplan.cl/beneficios-para-arrendatarios and https://www.assetplan.cl/multifamily use the same meta description. A description written for each page earns more clicks.
2 pages with very little text
https://www.assetplan.cl/paga-tu-arriendo and https://www.assetplan.cl/arriendo/departamento have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://www.assetplan.cl/.
17 small tap targets
17 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
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.
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.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 302 words of copy
The homepage carries about 302 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
34 other companies contacted
Loading the homepage contacts 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 assetplan.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on assetplan.cl, including 18 speed issues, 1 SEO issue 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.