SEOWebsiteTool
73Grade C

chuhesinhnhatkk.vn

Chú Hề KK | Dịch vụ chú hề sinh nhật, thôi nôi tại TP.HCM

2 failed · 7 warnings · 18 passed

Audited Sun, 12 Jul 2026 18:15:46 GMT · https://www.chuhesinhnhatkk.vn/

Meta & Head

21.5/25

Title, description, canonical, social tags — what search engines read first.

  • Meta descriptionhigh impactlow effort

    Meta description is "Chú Hề KK cung cấp dịch vụ chú hề sinh nhật, thôi nôi, hoạt náo, tạo hình bong bóng nghệ thuật và team building thiếu nhi tại TP.HCM, Dĩ An, Bình Dương, Đồng Nai." (162 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.

  • Canonical URLmedium impactlow effort

    Canonical href is "https://chuhesinhnhatkk.vn/" (host chuhesinhnhatkk.vn does not match page host www.chuhesinhnhatkk.vn)

    This canonical tells search engines that another host owns the content, so they will typically index that URL and drop this one from results entirely. Unless this is deliberate syndication, update the href to this page's own URL on its own host — and make sure www vs non-www matches your preferred domain. The usual cause is a template copied between environments, so check that a staging or legacy domain isn't hard-coded in the site layout.

7 passing checks
  • Title tag<title> is "Chú Hề KK | Dịch vụ chú hề sinh nhật, thôi nôi tại TP.HCM" (57 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
  • Character encoding declaredCharacter encoding is declared
  • 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: index,follow,max-image-preview:large

Content & Structure

12.5/25

Headings, copy depth, images, structured data, internal linking.

  • Single H1 headinghigh impactlow effort

    0 h1 headings found

    The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.

  • Internal linkingmedium impactmedium effort

    0 internal, 0 external links

    Search engines discover and rank your pages by following internal links; a page with none is a dead end for crawlers and visitors alike. Add contextual links to related pages on your own site — navigation, related-content sections, and in-body links all count. Aim for at least a handful of relevant internal links per page.

  • Word counthigh impactlow effort

    368 words of visible text

    With only a few hundred words, this page gives search engines little to index and often loses to more thorough competitors targeting the same query. Expand it toward 600+ words of genuinely useful material: answer the questions visitors arrive with, and add examples, specifics, an FAQ section, or step-by-step detail. Don't pad with fluff or repeat keywords to hit a number — length should be a byproduct of covering the topic properly, never the goal itself.

3 passing checks
  • Structured data (JSON-LD)JSON-LD types found: EntertainmentBusiness, Service, FAQPage
  • HTML lang attribute<html lang="vi">
  • JavaScript-dependent contentvisible text ~218 chars in the initial HTML

Technical

21/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • Fast time to first bytehigh impactmedium effort

    1153 ms

    Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.

  • Short redirect chainmedium impactlow effort

    https://chuhesinhnhatkk.vn/ (308) → https://www.chuhesinhnhatkk.vn/

    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.

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

  • Missing pages return 404low impactlow effort

    missing paths return a non-404 status (soft 404)

    URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.

8 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • robots.txt present and permissiverobots.txt exists and allows crawling
  • XML sitemap availablesitemap.xml exists and is valid XML
  • Reasonable HTML size6.6 KB
  • 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.

SEO score badge for chuhesinhnhatkk.vn

More “c” sitesRecent audits

chuhesinhnhatkk.vn — SEO Score 73/100 (Grade C) | SEO Website Tool