play.google.com
Egg Crack Pop - Apps on Google Play
1 failed · 8 warnings · 21 passed
Audited Fri, 31 Jul 2026 01:00:18 GMT · https://play.google.com/store/apps/details?id=eggorchard.crackpop.nest
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
Character encoding declaredlow impactlow effort
No character encoding declaration found
Without a declared character encoding, browsers have to guess how to decode your text; a wrong guess garbles apostrophes, accents, and currency symbols, and the guessing itself can delay rendering. Add <meta charset="utf-8"> as the very first element inside <head> — browsers only scan the opening bytes of the document for it. Also confirm your server isn't sending a conflicting charset in the Content-Type header, since a mismatch produces exactly the garbled text you're trying to prevent.
Meta descriptionhigh impactlow effort
Meta description is "Swap eggs, match three, pop the whole coop" (42 characters)
Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.
7 passing checks
- Title tag<title> is "Egg Crack Pop - Apps on Google Play" (35 characters)
- Canonical URLCanonical href is "https://play.google.com/store/apps/details?id=eggorchard.crackpop.nest&hl=en_US"
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- FaviconA <link rel="icon"> is present
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: NOODP
Content & Structure
22.8/25
Headings, copy depth, images, structured data, internal linking.
Image alt textmedium impactlow effort
22 of 25 images have alt text
Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.
Hreflang annotationslow impactlow effort
Invalid hreflang value(s): "es-419", "fil", "gsw", "sr-Latn"
Search engines silently skip hreflang entries with malformed codes, so users in those locales may be served the wrong language version — and no error report will ever tell you. Use an ISO 639-1 language code, optionally followed by an ISO 3166-1 region: "en", "en-US", "pt-BR", plus "x-default" for the fallback. Watch for the classic mistakes: "en-UK" should be "en-GB", and underscores like "en_US" are invalid — hreflang requires hyphens.
7 passing checks
- Single H1 heading1 h1 found: "Egg Crack Pop"
- Heading hierarchy6 headings in order without skipped levels
- Word count14178 words of visible text
- Structured data (JSON-LD)JSON-LD types found: SoftwareApplication
- HTML lang attribute<html lang="en-US">
- JavaScript-dependent contentvisible text ~2661 chars in the initial HTML
- Internal linking28 internal, 16 external links
Technical
20.5/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
Short redirect chainmedium impactlow effort
https://eggcrackpop.com/ (301) → https://play.google.com/store/apps/details?id=eggorchard.crackpop.nest
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
Reasonable HTML sizelow impactmedium effort
1.1 MB
A very large HTML document slows parsing on every visit and risks exceeding the portion of a file crawlers are willing to fetch — content past the cutoff may simply never be indexed. Slim it down: move large inline <script> and <style> blocks into external cacheable files, strip embedded JSON data blobs and base64-encoded images, and paginate or lazy-load very long listings. Check the most common culprit first: a framework serializing the entire page state or dataset into the document itself.
7 passing checks
- Served over HTTPSfinal URL uses https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte581 ms
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.