yejibugo.co.kr SEO report

예지부고 - 품격있는 모바일 부고장

Visit website
70/ 100

OVERALL SEO SCORE

Review your next improvements

Checks are based on public HTML and responses. Review the evidence and recommended actions below.

Passed21
Needs review10
Not checked0
Analyzed Checks 31

Screenshot

PagePeeker
yejibugo.co.kr
yejibugo.co.kr Screenshot

NEXT STEPS

Recommended next steps

Up to four findings, ordered by check weight.

Detailed findings

Review the observed values, context and actions for each check.

02

Content and images

5 checks

Headings

Needs review
H1 0 / H2 0 / H3 2

Headings organize a page into a main topic and supporting sections. This tool checks for one H1 and shows the saved H2-H6 structure.

Recommended action

Use H1 for the main subject and H2/H3 for logical subsections, rather than selecting levels for visual size alone.

Targets and suggested changes

Targethttps://yejibugo.co.kr/

Body h1 elements

If multiple H1s are shown, choose the main topic and use suitable subsection levels for the others. If absent, add the main heading near the start of content.

View evidence and example changes
Observed content
0
Example - adapt to the actual content and environment
<h1>Main topic of this page</h1>

Image alt

Passed
10 images; 10 with non-empty alt; 0 empty or missing

Alternative text conveys an image’s meaning. The count includes images with non-empty alt text.

Keep in mind

Describe informative images in context. Empty alt="" can be appropriate for decorative images, so inspect their purpose before changing them.

Language

Passed
ko

The html lang attribute identifies the document’s primary language and helps assistive software select pronunciation.

Keep in mind

Match lang to the main content and mark passages written in another language as appropriate.

Charset

Passed
UTF-8

The encoding declaration tells clients how to decode text. It must match the actual response bytes.

Keep in mind

Keep the HTTP or HTML charset declaration consistent with the file encoding; use UTF-8 for UTF-8 content.

Text/HTML ratio

Needs review
3.66%

Tool reference range 15-70%; not an official ranking threshold.

This compares visible text length with HTML length. It cannot determine content quality or rankings on its own.

Recommended action

Do not add filler text to target a ratio. Check for useful HTML content and unnecessary markup.

Targets and suggested changes

Targethttps://yejibugo.co.kr/

main / body

Check whether main content exists in the initial HTML. Consider server rendering for missing core text; do not add filler to target a ratio.

View evidence and example changes
Observed content
3.66%

Heading structure

Saved headings, up to 50 per level. Expand the H2-H6 lists when needed.

H10
H20
H32
H40
H50
H60
H1

No H1 heading was found.

H2 0View headings

No headings at this level.

H3 2View headings
  1. 상주 본인 인증
  2. 조문객 접속 현황 (예시)
Images and alternative text10 saved

Up to 100 images are saved. Review an image’s purpose when its alt text is empty.

URLImage alt
https://yejibugo.co.kr/assets/images/logo.png예지부고 로고
https://yejibugo.co.kr/assets/images/ico_kakao_main.png카카오톡
https://yejibugo.co.kr/assets/images/cover.jpg예지부고 브랜드 홍보 CF 영상
https://yejibugo.co.kr/assets/images/chart_login.png통계 차트
https://yejibugo.co.kr/assets/images/ico_main_review2.png리뷰
https://yejibugo.co.kr/assets/images/ico_main_review1.png리뷰
https://yejibugo.co.kr/assets/images/ico_main_review1.png리뷰
https://yejibugo.co.kr/assets/images/ico_make.png만들기
https://yejibugo.co.kr/assets/images/logo.png예지부고
https://yejibugo.co.kr/assets/images/sangju_manage.jpg상주 관리자 미리보기
KeywordsFrequency and metadata

Word occurrence counts from extracted content, not search demand or keyword rankings.

부고장21 확인7 고인의5 품격을5 예지부고4 문자4 전송4 통계4 모바일3 만들기3 edit3 square3 관리3 카톡3 통계를3 실시간3 회원가입없이3 제작3 상주3 부고장을3

Meta keywords · 모바일부고장, 무료모바일부고장, 부고장만들기, 부고문자, 카톡부고장, 모바일부고, 장례식장부고, 예지부고

Meta keywords do not contribute to this tool’s score.

04

Mobile experience

5 checks

Viewport

Passed
width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no

Viewport metadata enables device-width layouts. It is not a test of real mobile layout or touch targets.

Keep in mind

Check width=device-width, then inspect overflow, zoom, forms and buttons on a small screen.

Favicon

Passed
The current check passed.

This detects a link declaration for a browser icon, rather than verifying its rendered appearance.

Keep in mind

Check that the icon file loads and remains recognizable on light and dark browser surfaces.

Apple touch icon

Passed
The current check passed.

This detects a touch icon declaration for saved home-screen shortcuts.

Keep in mind

Review the icon’s dimensions, padding and background, then inspect it on an actual device.

Modern images

Needs review
0/10

This detects WebP/AVIF from img src/srcset extensions and picture source types. Images whose format cannot be inferred from HTML, such as extensionless CDN URLs, may not be reflected in the count.

Recommended action

Compare quality and file size, and inspect the actual delivered format in browser developer tools.

Targets and suggested changes

Targethttps://yejibugo.co.kr/assets/images/logo.png

HTML response line 242 · /html/body/div[1]/div[1]/div/div[1]/div[2]/a/img

Convert this file to WebP/AVIF and use the actual converted URL. Do not merely rename its extension. Keep it if the CDN already serves a modern format.

View evidence and example changes
Observed content
<img width="90" src="/assets/images/logo.png" alt="예지부고 로고">
Example - adapt to the actual content and environment
<picture>
  <source srcset="[converted-image.webp]" type="image/webp">
  <img src="https://yejibugo.co.kr/assets/images/logo.png" alt="예지부고 로고">
</picture>

Targethttps://yejibugo.co.kr/assets/images/ico_kakao_main.png

HTML response line 322 · /html/body/div[1]/div[3]/div[12]/div[1]/img

Convert this file to WebP/AVIF and use the actual converted URL. Do not merely rename its extension. Keep it if the CDN already serves a modern format.

View evidence and example changes
Observed content
<img width="35" src="/assets/images/ico_kakao_main.png" alt="카카오톡">
Example - adapt to the actual content and environment
<picture>
  <source srcset="[converted-image.webp]" type="image/webp">
  <img src="https://yejibugo.co.kr/assets/images/ico_kakao_main.png" alt="카카오톡">
</picture>

Targethttps://yejibugo.co.kr/assets/images/cover.jpg

HTML response line 355 · /html/body/div[1]/div[3]/div[18]/div/img

Convert this file to WebP/AVIF and use the actual converted URL. Do not merely rename its extension. Keep it if the CDN already serves a modern format.

View evidence and example changes
Observed content
<img src="/assets/images/cover.jpg" alt="예지부고 브랜드 홍보 CF 영상" class="video-thumbnail">
Example - adapt to the actual content and environment
<picture>
  <source srcset="[converted-image.webp]" type="image/webp">
  <img src="https://yejibugo.co.kr/assets/images/cover.jpg" alt="예지부고 브랜드 홍보 CF 영상">
</picture>

Targethttps://yejibugo.co.kr/assets/images/chart_login.png

HTML response line 422 · /html/body/div[1]/div[3]/div[33]/img

Convert this file to WebP/AVIF and use the actual converted URL. Do not merely rename its extension. Keep it if the CDN already serves a modern format.

View evidence and example changes
Observed content
<img width="100%" src="/assets/images/chart_login.png" alt="통계 차트">
Example - adapt to the actual content and environment
<picture>
  <source srcset="[converted-image.webp]" type="image/webp">
  <img src="https://yejibugo.co.kr/assets/images/chart_login.png" alt="통계 차트">
</picture>

Targethttps://yejibugo.co.kr/assets/images/ico_main_review2.png

HTML response line 436 · /html/body/div[1]/div[3]/div[38]/div[1]/img

Convert this file to WebP/AVIF and use the actual converted URL. Do not merely rename its extension. Keep it if the CDN already serves a modern format.

View evidence and example changes
Observed content
<img width="30" src="/assets/images/ico_main_review2.png" alt="리뷰">
Example - adapt to the actual content and environment
<picture>
  <source srcset="[converted-image.webp]" type="image/webp">
  <img src="https://yejibugo.co.kr/assets/images/ico_main_review2.png" alt="리뷰">
</picture>

10 targets; the first five are shown. Review the full saved list in the details below.

Lazy loading

Needs review
0/10

This detects loading="lazy" on img elements. Pages with few images can pass the tool’s heuristic without it.

Recommended action

Consider lazy loading below-the-fold images while keeping prominent first-screen images promptly available.

Targets and suggested changes

Targethttps://yejibugo.co.kr/assets/images/logo.png

HTML response line 242 · /html/body/div[1]/div[1]/div/div[1]/div[2]/a/img

Add loading="lazy" only if this image is below the initial viewport. Keep prominent initial-viewport images eager.

View evidence and example changes
Observed content
<img width="90" src="/assets/images/logo.png" alt="예지부고 로고">
Example - adapt to the actual content and environment
<img src="https://yejibugo.co.kr/assets/images/logo.png" alt="예지부고 로고" loading="lazy">

Targethttps://yejibugo.co.kr/assets/images/ico_kakao_main.png

HTML response line 322 · /html/body/div[1]/div[3]/div[12]/div[1]/img

Add loading="lazy" only if this image is below the initial viewport. Keep prominent initial-viewport images eager.

View evidence and example changes
Observed content
<img width="35" src="/assets/images/ico_kakao_main.png" alt="카카오톡">
Example - adapt to the actual content and environment
<img src="https://yejibugo.co.kr/assets/images/ico_kakao_main.png" alt="카카오톡" loading="lazy">

Targethttps://yejibugo.co.kr/assets/images/cover.jpg

HTML response line 355 · /html/body/div[1]/div[3]/div[18]/div/img

Add loading="lazy" only if this image is below the initial viewport. Keep prominent initial-viewport images eager.

View evidence and example changes
Observed content
<img src="/assets/images/cover.jpg" alt="예지부고 브랜드 홍보 CF 영상" class="video-thumbnail">
Example - adapt to the actual content and environment
<img src="https://yejibugo.co.kr/assets/images/cover.jpg" alt="예지부고 브랜드 홍보 CF 영상" loading="lazy">

Targethttps://yejibugo.co.kr/assets/images/chart_login.png

HTML response line 422 · /html/body/div[1]/div[3]/div[33]/img

Add loading="lazy" only if this image is below the initial viewport. Keep prominent initial-viewport images eager.

View evidence and example changes
Observed content
<img width="100%" src="/assets/images/chart_login.png" alt="통계 차트">
Example - adapt to the actual content and environment
<img src="https://yejibugo.co.kr/assets/images/chart_login.png" alt="통계 차트" loading="lazy">

Targethttps://yejibugo.co.kr/assets/images/ico_main_review2.png

HTML response line 436 · /html/body/div[1]/div[3]/div[38]/div[1]/img

Add loading="lazy" only if this image is below the initial viewport. Keep prominent initial-viewport images eager.

View evidence and example changes
Observed content
<img width="30" src="/assets/images/ico_main_review2.png" alt="리뷰">
Example - adapt to the actual content and environment
<img src="https://yejibugo.co.kr/assets/images/ico_main_review2.png" alt="리뷰" loading="lazy">

10 targets; the first five are shown. Review the full saved list in the details below.

05

Technical checks

8 checks

Doctype

Passed
html

The doctype declaration helps browsers render HTML in standards mode.

Keep in mind

Place <!doctype html> at the start of the document and check for unintended output before it.

CSS files

Passed
3

Tool heuristic: up to 4 external files

This counts external stylesheet declarations. Count alone does not measure transfer size, caching or render blocking.

Keep in mind

Inspect duplicate or unused CSS and render blocking, then prioritize changes using actual performance measurements.

JavaScript files

Passed
1

Tool heuristic: up to 6 external files

This counts script elements with src attributes. File count alone cannot measure execution cost or responsiveness.

Keep in mind

Review duplicated scripts and expensive startup work; consider defer, async or delayed execution where appropriate.

Compression

Passed
gzip

This checks the HTML Content-Encoding header. Compression can reduce transfer size, with savings depending on the response.

Keep in mind

Review text compression on the server or CDN, treating already compressed image formats separately.

Security headers

Needs review
0/6

Tool heuristic: at least 3 of 6 selected headers present

This detects selected security-related response headers. Their count does not establish policy quality or protection.

Recommended action

Review CSP, HSTS and other values for the application, then test for blocked resources or broken functionality.

Targets and suggested changes

Targethttps://yejibugo.co.kr/

Web server / CDN response headers

These headers were absent. Configure response headers in the actual server/CDN settings: .htaccess or VirtualHost for Apache, or the Nginx server block. Validate the two example headers first; design CSP/HSTS for the real resources and HTTPS policy. The actual server configuration path is not visible to this tool.

View evidence and example changes
Observed content
strict-transport-security
content-security-policy
x-content-type-options
x-frame-options
referrer-policy
permissions-policy
Example - adapt to the actual content and environment
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin

HTTPS

Passed
https://yejibugo.co.kr/

This checks whether the final analyzed page used HTTPS. It is not a security audit of the whole site.

Keep in mind

Review certificate validity, mixed content and HTTPS on important linked pages and forms.

HTTPS redirect

Needs review
http://yejibugo.co.kr/

This checks whether a request starting over HTTP ends on HTTPS.

Recommended action

Configure consistent HTTP-to-HTTPS redirects and check for unnecessary chains or loops.

Targets and suggested changes

Targethttps://yejibugo.co.kr/

HTTP host redirect configuration

Redirect the HTTP host to working HTTPS using 301/308 while preserving path and query.

View evidence and example changes
Observed content
http://yejibugo.co.kr/
Example - adapt to the actual content and environment
http://yejibugo.co.kr/ → https://yejibugo.co.kr/

W3C validity

Needs review
3 errors · 25 warnings / notices

These are HTML validation results from W3C Nu, not a ranking, accessibility or security certification.

Recommended action

Use message details and line numbers to investigate actual markup issues such as invalid nesting or missing attributes.

Targets and suggested changes

Targethttps://yejibugo.co.kr/

HTML response line 422

Bad value “100%” for attribute “width” on element “img”: Expected a digit but saw “%” instead. Find the template producing this tag or attribute and validate again. The line number refers to response HTML, not a PHP source file.

View evidence and example changes
Observed content
"fade-up"><img width="100%" src="/assets/images/chart_login.png" alt="통계 차트"></div>

Targethttps://yejibugo.co.kr/

HTML response line 655

Bad value “100%” for attribute “width” on element “video”: Expected a digit but saw “%” instead. Find the template producing this tag or attribute and validate again. The line number refers to response HTML, not a PHP source file.

View evidence and example changes
Observed content
          <video id="cfVideo" width="100%" height="100%" playsinline preload="none" poster="/assets/images/cover.jpg" style="position:absolute; top:0; left:0; width:100%; height:100%; object-fit:cover; background:#000;">
     

Targethttps://yejibugo.co.kr/

HTML response line 655

Bad value “100%” for attribute “height” on element “video”: Expected a digit but saw “%” instead. Find the template producing this tag or attribute and validate again. The line number refers to response HTML, not a PHP source file.

View evidence and example changes
Observed content
          <video id="cfVideo" width="100%" height="100%" playsinline preload="none" poster="/assets/images/cover.jpg" style="position:absolute; top:0; left:0; width:100%; height:100%; object-fit:cover; background:#000;">
     
CSS files and locations3 saved

Up to 100 files per type are saved. File count alone does not establish a defect in any file.

URLHTML response location
https://fonts.googleapis.com/css2?family=Noto+Serif:wght@600&display=swap54 · /html/head/link[7]
https://fonts.googleapis.com/css2?family=Material+Symbols+Outlined:opsz,wght,FILL,GRAD@24,300,0,055 · /html/head/link[8]
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css56 · /html/head/link[9]
JavaScript files and locations1 saved

Up to 100 files per type are saved. File count alone does not establish a defect in any file.

URLHTML response location
https://code.jquery.com/jquery-3.6.0.min.js57 · /html/head/script[2]
Security response headersView values
strict-transport-security
Not found
content-security-policy
Not found
x-content-type-options
Not found
x-frame-options
Not found
referrer-policy
Not found
permissions-policy
Not found
W3C messages28 saved

Up to 30 messages are saved.

  1. errorLine 422

    Bad value “100%” for attribute “width” on element “img”: Expected a digit but saw “%” instead.

    "fade-up"><img width="100%" src="/assets/images/chart_login.png" alt="통계 차트"></div>
  2. errorLine 655

    Bad value “100%” for attribute “width” on element “video”: Expected a digit but saw “%” instead.

    <video id="cfVideo" width="100%" height="100%" playsinline preload="none" poster="/assets/images/cover.jpg" style="position:absolute; top:0; left:0; width:100%; height:100%; object-fit:cover; background:#000;">
  3. errorLine 655

    Bad value “100%” for attribute “height” on element “video”: Expected a digit but saw “%” instead.

    <video id="cfVideo" width="100%" height="100%" playsinline preload="none" poster="/assets/images/cover.jpg" style="position:absolute; top:0; left:0; width:100%; height:100%; object-fit:cover; background:#000;">
  4. infoLine 5

    Consider avoiding viewport values that prevent users from resizing documents.

    f-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" /> <
  5. infoLine 5

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    f-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" /> <
  6. infoLine 10

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    트웍스"> <meta name="robots" content="index,follow" /> <
  7. infoLine 11

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    w" /> <link rel="canonical" href="https://www.yejibugo.co.kr/" />
  8. infoLine 14

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    ) --> <meta property="og:type" content="website" /> <
  9. infoLine 15

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    e" /> <meta property="og:site_name" content="예지부고" /> <
  10. infoLine 16

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    고" /> <meta property="og:title" content="예지부고 - 품격있는 무료 모바일 부고장" /> <
  11. infoLine 17

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    장" /> <meta property="og:description" content="회원가입 없이 3분이면 제작 끝! 카톡·문자 간편 전송과 실시간 확인 통계를 제공하는 고품격 무료 모바일 부고장 서비스" /> <
  12. infoLine 18

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    스" /> <meta property="og:url" content="https://www.yejibugo.co.kr/" /> <
  13. infoLine 19

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    /" /> <meta property="og:image" content="https://www.yejibugo.co.kr/assets/images/cover.jpg" /> <
  14. infoLine 20

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    g" /> <meta property="og:locale" content="ko_KR" />
  15. infoLine 23

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    d --> <meta name="twitter:card" content="summary_large_image" /> <
  16. infoLine 24

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    e" /> <meta name="twitter:title" content="예지부고 - 품격있는 무료 모바일 부고장" /> <
  17. infoLine 25

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    장" /> <meta name="twitter:description" content="회원가입 없이 무료로 이용하는 고품격 모바일 부고장 제작 및 발송 서비스" /> <
  18. infoLine 26

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    스" /> <meta name="twitter:image" content="https://www.yejibugo.co.kr/assets/images/cover.jpg" />
  19. infoLine 55

    Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

    wap"> <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Material+Symbols+Outlined:opsz,wght,FILL,GRAD@24,300,0,0" /> <
  20. infoLine 261

    The “align” attribute on the “td” element is obsolete. Use CSS instead.

    <tr> <td align="center" width="45%"><div c
  21. infoLine 261

    The “width” attribute on the “td” element is obsolete. Use CSS instead.

    <tr> <td align="center" width="45%"><div c
  22. infoLine 262

    The “width” attribute on the “td” element is obsolete. Use CSS instead.

    /div></td> <td width="10%"></td>
  23. infoLine 263

    The “align” attribute on the “td” element is obsolete. Use CSS instead.

    10%"></td> <td align="center" width="45%"><div c
  24. infoLine 263

    The “width” attribute on the “td” element is obsolete. Use CSS instead.

    10%"></td> <td align="center" width="45%"><div c
  25. infoLine 266

    The “align” attribute on the “td” element is obsolete. Use CSS instead.

    <tr> <td align="center"><div c
  26. infoLine 267

    The “align” attribute on the “td” element is obsolete. Use CSS instead.

    /div></td> <td align="center">|</td>
  27. infoLine 268

    The “align” attribute on the “td” element is obsolete. Use CSS instead.

    er">|</td> <td align="center"><div c
  28. infoLine 563

    This document has heading elements but none of them has a computed heading level of 1.

    > <h3 class="sj-auth-title">상주 본인
06

Search and AI crawlers

4 checks

Robots.txt

Passed
robots.txt

This checks the robots.txt response. File presence does not verify all crawler permissions or actual indexing.

Keep in mind

Review bot and path rules for your intended policy. Protect private information with authentication and access controls.

XML Sitemap

Needs review
The expected configuration was not detected.

This detects a sitemap format at a declared or default URL. It does not crawl and validate every listed URL.

Recommended action

Include intended canonical URLs and meaningful update dates. Declare a custom sitemap location in robots.txt.

Targets and suggested changes

Targethttps://www.yejibugo.co.kr/sitemap.xml

/sitemap.xml / robots.txt

Generate XML using real canonical URLs and declare the working location in robots.txt. Link an existing custom sitemap instead of duplicating it.

View evidence and example changes
Example - adapt to the actual content and environment
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>https://yejibugo.co.kr/</loc></url></urlset>

llms.txt

Needs review
The expected configuration was not detected.

This checks for a text response at /llms.txt. Its presence does not guarantee use by an AI service or search visibility.

Recommended action

If you publish one, describe public resources accurately and keep its content and links current.

Targets and suggested changes

Targethttps://yejibugo.co.kr/llms.txt

/llms.txt

If desired, publish UTF-8 text at the root and add real public documentation links. This is optional.

View evidence and example changes
Example - adapt to the actual content and environment
# 예지부고 - 품격있는 모바일 부고장

- [Home](https://yejibugo.co.kr/)

AI crawlers

Passed
AI search/answer bots allowed 5/5 · training bots allowed 3/3

Passes when every AI search/answer bot is allowed; training bots are shown for reference only

This interprets root-path robots.txt rules for five AI search/answer bots (which read pages to cite them in answers) and three training bots. Only the search/answer bots decide the result; training bots are shown for reference. Actual citations are not checked.

Keep in mind

Allow the search/answer bots if you want to be cited in AI answers. Blocking training crawlers is a policy choice and does not affect this result.

Bot access to the root path

OAI-SearchBot Search/answerAllowed
ChatGPT-User Search/answerAllowed
Claude-SearchBot Search/answerAllowed
Claude-User Search/answerAllowed
PerplexityBot Search/answerAllowed
GPTBot TrainingAllowed
ClaudeBot TrainingAllowed
Google-Extended TrainingAllowed
robots.txt sourceExpand
User-agent: *
Allow: /
Disallow: /views/mng/
Disallow: /phpmyadmin/

Sitemap: https://www.yejibugo.co.kr/sitemap.xml
07

PageSpeed Insights

External performance test

Run Google Lighthouse performance, accessibility, best practices and SEO checks. Device-specific results are cached for one day and are separate from the overall score above.