tilda.cc

Readiness by lane

Green: tilda.cc. Thin bar: Website Builders peer median.

Priority fixes for tilda.cc

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

1. Priority 1 · Accelerate

   Modern image formats in use

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

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   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.

   62% of Website Builders peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

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 Tilda: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   26% of Website Builders peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 23 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.

   61% of Website Builders peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   34% of Website Builders peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What tilda.cc already does well

Practices fewer than half of Website Builders peers use.

• Framing restrictedFraming controls present.42% of peers

What we saw

Homepage checked

https://tilda.cc/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Key-Systems GmbH, 198-day validity, expiring 2027-04-29

Platform or framework

Tilda

DNS operators

Amazon Route 53

DMARC policy

p=quarantine

Homepage HTML

460 KB, gzip

Images on homepage

23 (png 15, svg 7, jpg 1)

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 Website Builders sites

• bio.site62
• carrd.com62
• straw.page62
• taplink.cc58
• weebly.com59

Website Builders readiness benchmark