SEO report for www.dothome.co.kr

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to dothome.co.kr…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap found at https://www.dothome.co.kr/sitemap.xml with 33 URLs.

  Declared in robots.txt.

  This page is listed in it.

  No lastmod dates – add accurate ones so search engines know what changed.

• ✓

  Canonical URLhigh

  Canonical: https://www.dothome.co.kr

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://dothome.co.kr/ → https://www.dothome.co.kr/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  dothome.co.kr redirects to www.dothome.co.kr.

Search snippet & sharing 67%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “무료홈페이지 | 무료호스팅 | 닷홈”

  About 177px of Google's ~580px desktop width – short; use the space.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• !

  Meta descriptionhigh

  72 characters, ~490px of ~990px.

  Short – sell the click with a benefit and a call to action.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

  Fix: Write a 140–155 character description that answers the searcher's question and invites the click.

  Write one free with the AI title & description writer

  Read the guide: how to write meta descriptions

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  No twitter:card tag.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="ko"

Content quality 58%

Is there enough clear, useful text that matches what the page targets?

• ✓

  Word countmedium

  854 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• i

  Readabilitymedium

  Reading-ease scores only work for English; this page is lang="ko".

• ✓

  Topic focushigh

  2 of 2 title keywords appear in the main content.

• !

  H1 headingcritical

  4 H1 headings – one clear H1 is best practice.

  Fix: Use one H1 that states the page topic with its main keyword.

• ✗

  Heading structuremedium

  11 headings for 854 words.

  4 skipped level(s), e.g. H2 → H4.

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  4% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 44%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✗

  llms.txtlow

  No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

  Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• !

  Question-led contentmedium

  1 heading(s) phrased as questions, e.g. “문의사항이 있으신가요?”.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✗

  Entity clarityhigh

  No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Freshness signalsmedium

  No published/updated date found.

  Fix: Show a 'last updated' date and add dateModified to your structured data.

• ✗

  Trust pages (E-E-A-T)medium

  No links found to about, contact or privacy pages.

  Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 50%

Machine-readable facts for rich results and AI.

• !

  JSON-LD present & validhigh

  1 JSON-LD block(s): no @type.

  Block 1: invalid JSON

  Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

  Make valid code with the free schema generator

  Read the guide: schema markup

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  248 internal and 15 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “닷홈빌더 신청 new”, “이미지호스팅”, “웹호스팅”, “상품 문의”.

  9 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

  1 link(s) point to a redirect – link to the final address instead.

Performance 27%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• !

  Server response (TTFB)high

  1668 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• ✓

  HTML sizemedium

  102 kB of HTML.

• i

  Compressionmedium

  Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

• ✗

  Render-blocking resourceshigh

  19 blocking script(s) and 11 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  45 script tag(s); files loaded from 7 other domain(s): stackpath.bootstrapcdn.com, cdnjs.cloudflare.com, googletagmanager.com, wcs.naver.net, log1.toup.net, googleadservices.com….

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  36 image(s).

  36 without width/height – can cause layout shift (CLS).

  33 image(s) after the first three aren't lazy-loaded.

  0 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✗

  Cachinglow

  No Cache-Control header.

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• i

  HTTP/3low

  Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 75%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✗

  HSTSmedium

  No Strict-Transport-Security header.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: none.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✓

  Server fingerprintlow

  No X-Powered-By header (server: cloudflare).

Mobile & accessibility 38%

Usable on phones and by everyone – Google indexes the mobile version.

• !

  Mobile viewportcritical

  viewport: width=device-width,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0 – blocks pinch-zoom

  Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  Read the guide: mobile-friendly websites

• ✗

  Image alt textmedium

  26 of 36 images have no alt attribute.

  Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

  Read the guide: image SEO

• ✗

  Form labelsmedium

  1 of 4 form field(s) have no label.

  Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

• ✗

  Link nameslow

  9 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✓

  Tap-to-contactmedium

  One-tap contact: email.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist