Website readiness profile · Snapshot 23 October 2026

emojidb.org

emojidb.org's public homepage, certificate and DNS checked against 31 practices and compared with 492 Web Tools sites.

Readiness index: 55/100
Ahead of: 14%
Practices observed: 13/28
Popularity band: Top 5K

Measured 2026-10-23 11:51:23 UTC from one location. How we measure

Readiness by lane

Green: emojidb.org. Thin bar: Web Tools peer median.

Enable

49/100

Peers 84

Harden

43/100

Peers 55

Accelerate

100/100

Peers 69

Recover

0/100

Peers 6

Priority fixes for emojidb.org

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

Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
93% of Web Tools peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 2 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
73% of Web Tools peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
30% of Web Tools peers do this.
Guide: HTTPS and TLS Guide for Website Owners
Priority 4 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
74% of Web Tools peers do this.
Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What we saw

Homepage checked: https://emojidb.org/
Homepage response: HTTP 200
TLS: TLSv1.3, HTTP/2
Certificate: Google Trust Services, 90-day validity, expiring 2027-01-02
CDN or edge: Cloudflare
DNS operators: Cloudflare
Homepage HTML: 68 KB, br
Images on homepage: 0

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.

Cloudflare (cdn and edge platform)Cloudflare (dns operator)Google Trust Services (certificate authority)Service guide: Cloudflare

All 31 checks

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

Not observed 15

Observed 13

HTTP requests move to HTTPS
TLS 1.3 negotiated
Certificate has more than 14 days left
Certificate lifetime of 100 days or less
HTTP/2 negotiated
HTTP/3 advertised
HTML compressed
No render-blocking scripts in <head>
Reachable over IPv6
Meta description written
Mobile viewport configured
Page language declared
At most one redirect to the homepage

Not measured 3

Static files cached for 30 days or more
Modern image formats in use
Offscreen images lazy-loaded

Own emojidb.org?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Re-check emojidb.org now Add to owner workspace Request a correction or removal

Live status for this site: Status Is Down: emojidb.org. This profile covers configuration only.

Compare with other Web Tools sites

Web Tools readiness benchmark