infocasas.com.uy

Readiness by lane

Green: infocasas.com.uy. Thin bar: Real Estate & Property Listings peer median.

Priority fixes for infocasas.com.uy

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   89% of Real Estate & Property Listings peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   43% of Real Estate & Property Listings peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 48 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Next.js: The next/image component serves optimized formats automatically.

   50% of Real Estate & Property Listings peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 48 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   65% of Real Estate & Property Listings peers do this.

   Guide: Lazy Loading Without Broken Pages

What infocasas.com.uy already does well

Practices fewer than half of Real Estate & Property Listings peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.49% of peers

What we saw

Homepage checked

https://www.infocasas.com.uy/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2026-12-18

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

232 KB, gzip

Images on homepage

48 (png 38, jpg 24)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Real Estate & Property Listings sites

• entree.nu60
• era.pt60
• flexmls.com60
• remax.com.ar60
• renthub.in.th60

Real Estate & Property Listings readiness benchmark