maxi.rs

Readiness by lane

Green: maxi.rs. Thin bar: Food & Grocery Delivery peer median.

Priority fixes for maxi.rs

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 600 seconds, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   59% of Food & Grocery Delivery peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   40% of Food & Grocery Delivery peers do this.

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

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script 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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   43% of Food & Grocery Delivery peers do this.

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

4. Priority 4 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   63% of Food & Grocery Delivery peers do this.

   Guide: SEO Checklist for a New Website

What maxi.rs already does well

Practices fewer than half of Food & Grocery Delivery peers use.

• Nameservers spread across providersNameservers spread across more than one operator.12% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers
• Content Security Policy presentContent-Security-Policy present.37% of peers

What we saw

Homepage checked

https://www.maxi.rs/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 358-day validity, expiring 2027-01-13

CDN or edge

Akamai

Platform or framework

Next.js

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

425 KB, gzip

Images on homepage

118 (png 222, jpg 144, svg 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 Food & Grocery Delivery sites

• auchan.pt73
• chipotle.com74
• kaufland.ro74
• sparkdriverapp.com74
• swissmilk.ch75

Food & Grocery Delivery readiness benchmark