mobiledokan.co

Readiness by lane

Green: mobiledokan.co. Thin bar: Ratings & Reviews peer median.

Priority fixes for mobiledokan.co

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 83 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.

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   37% of Ratings & Reviews 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 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 6 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.

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   51% of Ratings & Reviews peers do this.

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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

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

   On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.

   65% of Ratings & Reviews peers do this.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for mobiledokan.co, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   11% of Ratings & Reviews peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What mobiledokan.co already does well

Practices fewer than half of Ratings & Reviews peers use.

• Content Security Policy presentContent-Security-Policy present.23% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.31% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.37% of peers

What we saw

Homepage checked

https://www.mobiledokan.co/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-09

CDN or edge

Cloudflare

Platform or framework

WordPress

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

226 KB, br

Images on homepage

83 (png 4)

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 Ratings & Reviews sites

• allcafe.ru78
• desidime.com79
• gelbeseiten.de79
• judge.me79
• versus.com79

Ratings & Reviews readiness benchmark