devteam.co.kr

https://www.devteam.co.kr/ Tested Oct 5, 2026 · 09:10 UTC 18 tests
Get a certificate
94out of 100
A

Very good

All tests finished in 65 s.

Complete
0.98 sAvg. load time (8 regions)
98/100Lighthouse performance
853 msServer response (TTFB)
A+SSL/TLS grade
8 / 8AI search crawlers allowed

Top fixes (12 of 14)

Brand name ranking Google

The site is not on the first page of Google (top 10) for "DevTeam Korea". Even customers searching for your brand will struggle to find it.

Content-Security-Policy (CSP) Headers

No Content-Security-Policy. It is the main browser-side defense against cross-site scripting (XSS).

Server response time (TTFB) SEO basics

Time to first byte, measured from our test server in the US (Virginia), is slow. Check page caching and server performance.

US response time (Google & AI crawlers) Global speed

Responses are slowish from the US, the source of most Googlebot and AI crawler traffic. Google lowers its crawl rate for sites that respond slowly.

Known TLS vulnerabilities SSL/TLS

Possible BREACH exposure: potentially VULNERABLE, br gzip HTTP compression detected - only supplied '/' tested. This only matters if compressed pages reflect user input next to secrets (such as CSRF tokens).

Cipher suites TLS config

Legacy CBC-SHA1 suites are still offered.

Desktop screenshot of devteam.co.kr
Mobile screenshot
Captured with real Chrome from our US test server (Virginia).

Performance

How fast your pages load around the world and on phones.

Global load speed

Loaded in a real browser from 8 regions worldwide: average load 976 ms, slowest London. From the US, the source of most Googlebot and AI crawler traffic, the server responds in 658 ms. Still...

77/100 C
US response time (Google & AI crawlers) (Improve)
Responses are slowish from the US, the source of most Googlebot and AI crawler traffic. Google lowers its crawl rate for sites that respond slowly.
658 ms (East 814 ms · West 502 ms)
Target: 0.6s or less
How to fixCaching the HTML of public pages at the CDN edge gets US responses down to tens of milliseconds. Start by cutting server processing time with page caching and faster database queries.
How we test this →
CDN & edge cache (Improve)
The CDN connects visitors to a nearby edge server, but the HTML is fetched from the origin server every time. From US East, the first response takes 1.21 s.
CDN (HTML from origin)
Target: First response within 0.8s from any region
How to fixCache the HTML of public pages (no login or cart) at the CDN as well; in Cloudflare, Cache Rules set what is cached and the Edge TTL. Purge a page's cached URL whenever you edit it.
How we test this →
All 4 checks and details
US response time (Google & AI crawlers) (Improve)
Responses are slowish from the US, the source of most Googlebot and AI crawler traffic. Google lowers its crawl rate for sites that respond slowly.
658 ms (East 814 ms · West 502 ms)
Target: 0.6s or less
How to fixCaching the HTML of public pages at the CDN edge gets US responses down to tens of milliseconds. Start by cutting server processing time with page caching and faster database queries.
How we test this →
CDN & edge cache (Improve)
The CDN connects visitors to a nearby edge server, but the HTML is fetched from the origin server every time. From US East, the first response takes 1.21 s.
CDN (HTML from origin)
Target: First response within 0.8s from any region
How to fixCache the HTML of public pages (no login or cart) at the CDN as well; in Cloudflare, Cache Rules set what is cached and the Edge TTL. Purge a page's cached URL whenever you edit it.
How we test this →
Availability by region (Good)
The page loaded normally in all 8 regions, so crawlers anywhere in the world can read the site.
8/8 regions OK
Target: Loads in every region
How we test this →
Load speed across 8 regions (Good)
Across 8 regions: average server response 593 ms, average full load 976 ms. Slowest: London (1.09 s).
Rated A+ · avg 976 ms
Target: Rated A or better on the 8-region scale
How we test this →

Full page load by region — first visit and repeat visit

Seoulap-northeast-2
338 ms
Tokyoap-northeast-1
490 ms
Singaporeap-southeast-1
804 ms
Sydneyap-southeast-2
947 ms
US EastVirginia
1.45 s
US WestOregon
1.06 s
Frankfurteu-central-1
1.32 s
Londoneu-west-2
1.41 s
First visit (empty cache)Repeat visit (cached)

Timing details

RegionDNS + connectServer responseLoadRepeat loadRequests
Seoul ap-northeast-2 27 ms 69 ms 338 ms 515 ms 13
Tokyo ap-northeast-1 60 ms 199 ms 490 ms 361 ms 13
Singapore ap-southeast-1 101 ms 459 ms 804 ms 632 ms 13
Sydney ap-southeast-2 164 ms 559 ms 947 ms 712 ms 13
US East us-east-1 396 ms 814 ms 1.45 s 917 ms 13
US West us-west-2 299 ms 502 ms 1.06 s 497 ms 13
Frankfurt eu-central-1 29 ms 1.05 s 1.32 s 475 ms 13
London eu-west-2 67 ms 1.09 s 1.41 s 1.32 s 13

Measured with headless Chrome on 8 AWS regions by Global Website Speed Test. Server response = request sent → first byte (excludes DNS/TCP/TLS); load = navigation start → load event.

Core Web Vitals (Lighthouse)

Mobile performance 98/100, LCP 1.91 s, CLS 0. Measured with Lighthouse from our test server in the US (Virginia).

98/100 A+
All 9 checks passed — show details
Mobile performance score (Lighthouse) (Good)
The page loads quickly on mobile.
98 / 100
Target: 90 or higher
How we test this →
Largest Contentful Paint (LCP) (Good)
Time until the largest image or text block on the first screen appears. It meets the target.
1.91 s
Target: 2.5s or less
How we test this →
Total Blocking Time (TBT, responsiveness) (Good)
Time the page is frozen by JavaScript and cannot respond to input (the lab stand-in for INP). It meets the target.
0 ms
Target: 200ms or less
How we test this →
Cumulative Layout Shift (CLS) (Good)
The layout barely shifts while the page loads.
0
Target: 0.1 or less
How we test this →
First Contentful Paint (FCP) (Good)
Time until the first text or image appears on screen. It meets the target.
1.68 s
Target: 1.8s or less
How we test this →
Total page weight (Good)
Page weight is reasonable.
178KB · 14 requests
Target: 2MB or less
How we test this →
Accessibility, Best Practices & SEO scores (Good)
Lighthouse Accessibility 100, Best Practices 100, SEO 100.
100 / 100 / 100
Render-blocking scripts (Good)
Scripts in <head> do not block rendering.
0
Target: Scripts in <head> use defer/async
How we test this →
Modern image formats (Good)
Images use lightweight modern formats.
7/12
Target: WebP or AVIF
How we test this →
1.91 sLargest Contentful Paint
0Cumulative Layout Shift
0 msTotal Blocking Time
1.68 sFirst Contentful Paint
2.68 sSpeed Index

How the page appeared while loading (simulated mobile)

Page at 375 ms
375 ms
Page at 750 ms
750 ms
Page at 1.13 s
1.13 s
Page at 1.5 s
1.5 s
Page at 1.88 s
1.88 s
Page at 2.25 s
2.25 s
Page at 2.63 s
2.63 s
Page at 3 s
3 s
98Lighthouse Performance
100Lighthouse Accessibility
100Lighthouse Best practices
100Lighthouse SEO

Biggest opportunities

OpportunityEstimated savings
Remove render-blocking requests
Shorten critical request chains
Use efficient cache lifetimes for static files
Est savings of 19 KiB
Ship less legacy JavaScript
Est savings of 11 KiB

Lighthouse 13.5.0 · mobile emulation (mid-range phone, slow 4G) from our US server. Lab data: real visitors' numbers vary.

Mobile experience

Median repeat-visit load 621 ms on 3 phone profiles, 0 JavaScript errors from your own code.

100/100 A+
All 6 checks passed — show details
Load time on a mid-range phone (Good)
Pages load quickly on phones even with a slow CPU.
621 ms repeat · 1.12 s first visit
Target: Under 1.5 s on repeat visits (4× CPU slowdown)
How we test this →
Main thread blocking (Good)
Scripts leave the phone responsive to taps while the page loads.
0 ms
Target: Under 200 ms of long tasks
How we test this →
No JavaScript errors (Good)
Your own scripts ran without errors on all devices.
0 own · 0 third-party
Target: 0 errors from your own scripts
How we test this →
Fits the phone screen (Good)
No horizontal scrolling on any device.
Fits
Target: No sideways scrolling
How we test this →
Tap targets large enough (Good)
Buttons and links are easy to tap.
2 small
Target: Buttons and controls at least 24×24 px (WCAG 2.2)
How we test this →
Readable text size (Good)
Text is legible without zooming.
0% tiny text
Target: Under 5% of text smaller than 12 px
How we test this →
DeviceFirst visitRepeat visitBlockingJS errorsFits screen
iPhone SE (3rd gen)
375×667
950 ms 646 ms 0 ms 0 Yes
iPhone 15 Pro
393×659
1.12 s 587 ms 0 ms 0 Yes
Pixel 7
412×839
1.28 s 621 ms 0 ms 0 Yes

Playwright device profiles with a 4× CPU slowdown. Load = navigation start → load event; blocking = long tasks over 50 ms.

Security

Encryption, certificates and the headers that protect visitors.

SSL/TLS security (testssl.sh)

testssl.sh rating A+ (96/100) for www.devteam.co.kr: TLS 1.2, TLS 1.3.

96/100 A+
Known TLS vulnerabilities (Improve)
Possible BREACH exposure: potentially VULNERABLE, br gzip HTTP compression detected - only supplied '/' tested. This only matters if compressed pages reflect user input next to secrets (such as CSRF tokens).
1 found
Target: Not vulnerable
How to fixKeep secrets out of compressed responses that echo user input, or mask CSRF tokens per request.
How we test this →
Cipher suites & forward secrecy (Improve)
Strong ciphers with forward secrecy are offered, but some obsolete CBC ciphers are still enabled.
Forward secrecy
Target: Strong AEAD ciphers with forward secrecy
How to fixRemove CBC-mode cipher suites (keep AES-GCM and ChaCha20-Poly1305).
How we test this →
DNS CAA record (Improve)
No CAA record: any certificate authority may issue certificates for your domain.
Missing
Target: Restricts which CAs may issue certificates
How to fixAdd a DNS CAA record naming your CA, e.g. 0 issue "letsencrypt.org".
How we test this →
All 6 checks and details
Known TLS vulnerabilities (Improve)
Possible BREACH exposure: potentially VULNERABLE, br gzip HTTP compression detected - only supplied '/' tested. This only matters if compressed pages reflect user input next to secrets (such as CSRF tokens).
1 found
Target: Not vulnerable
How to fixKeep secrets out of compressed responses that echo user input, or mask CSRF tokens per request.
How we test this →
Cipher suites & forward secrecy (Improve)
Strong ciphers with forward secrecy are offered, but some obsolete CBC ciphers are still enabled.
Forward secrecy
Target: Strong AEAD ciphers with forward secrecy
How to fixRemove CBC-mode cipher suites (keep AES-GCM and ChaCha20-Poly1305).
How we test this →
DNS CAA record (Improve)
No CAA record: any certificate authority may issue certificates for your domain.
Missing
Target: Restricts which CAs may issue certificates
How to fixAdd a DNS CAA record naming your CA, e.g. 0 issue "letsencrypt.org".
How we test this →
SSL/TLS rating (SSL Labs method) (Good)
testssl.sh rates this server A+ using the SSL Labs grading guide.
A+ · 96/100
Target: A or A+
How we test this →
Protocol versions (Good)
Only TLS 1.2 and TLS 1.3 are offered.
TLS 1.2, TLS 1.3
Target: TLS 1.2 + TLS 1.3 only
How we test this →
Certificate validity (Good)
Trusted chain from WE1 (Google Trust Services from US), EC 256 bits (curve P-256), ECDSA with SHA256.
47 days left
Target: Trusted chain, matches host, > 30 days left
How we test this →
A+Rating (SSL Labs method)
47 daysCertificate valid for
TLS 1.2 · TLS 1.3Protocols offered
IssuerWE1 (Google Trust Services from US)
KeyEC 256 bits (curve P-256)
SignatureECDSA with SHA256
Expires2026-11-21 06:13
Names covereddevteam.co.kr *.devteam.co.kr
OCSP staplingnot offered

testssl.sh checked 19 known TLS attacks · low-risk notes: Lucky13.

TLS configuration (SSLyze)

TLS scan of www.devteam.co.kr: TLS 1.2, TLS 1.3; 0 problems, 1 warning.

92/100 A
Cipher suites (Improve)
Legacy CBC-SHA1 suites are still offered.
7 TLS 1.2 suites · 100% forward secrecy
Target: No weak ciphers; forward secrecy everywhere
How to fixOffer only ECDHE suites with AES-GCM or ChaCha20-Poly1305 (Mozilla "intermediate" profile).
How we test this →
All 8 checks and details
Cipher suites (Improve)
Legacy CBC-SHA1 suites are still offered.
7 TLS 1.2 suites · 100% forward secrecy
Target: No weak ciphers; forward secrecy everywhere
How to fixOffer only ECDHE suites with AES-GCM or ChaCha20-Poly1305 (Mozilla "intermediate" profile).
How we test this →
OCSP stapling (Info)
OCSP stapling is off. Optional: many CAs are retiring OCSP, so this matters less than it used to.
Off
Target: Enabled
How we test this →
Protocol versions (Good)
Only modern protocols are offered, including TLS 1.3.
TLS 1.2, TLS 1.3
Target: TLS 1.2 and 1.3 only
How we test this →
Certificate trusted and matches the domain (Good)
Issued by Google Trust Services and valid for www.devteam.co.kr.
Trusted
Target: Valid chain from a public CA, covers www.devteam.co.kr
How we test this →
Certificate expiry (Good)
Valid until Nov 21, 2026.
46 days left
Target: More than 30 days left, auto-renewed
How we test this →
Key and signature strength (Good)
Key size and signature algorithm are strong.
ECDSA 256 · sha256
Target: RSA ≥ 2048 or ECDSA ≥ 256; SHA-256 or better
How we test this →
Key exchange curves (Good)
Modern elliptic curves are supported.
X25519, secp256r1, secp384r1, secp521r1
Target: X25519 / P-256
How we test this →
Known TLS vulnerabilities (Good)
Not vulnerable to Heartbleed, ROBOT, OpenSSL CCS injection, insecure renegotiation or TLS compression.
None found
Target: Not vulnerable to Heartbleed, ROBOT, CCS, CRIME…
How we test this →

Protocol support

SSL 2.0 ✕ SSL 3.0 ✕ TLS 1.0 ✕ TLS 1.1 ✕ TLS 1.2 ✓ TLS 1.3 ✓
7TLS 1.2 cipher suites
3TLS 1.3 cipher suites
100%Forward secrecy
3Certificates in chain

Security headers

7 of 9 security header checks passed, 1 missing or unsafe.

82/100 B
Content-Security-Policy (CSP) (Problem)
No Content-Security-Policy. It is the main browser-side defense against cross-site scripting (XSS).
Missing
Target: Restricts scripts; no unsafe-inline without nonce/hash
How to fixStart with a policy such as: default-src 'self'; script-src 'self' (plus the domains you load scripts from); object-src 'none'; base-uri 'self'; frame-ancestors 'self'. Test it in report-only mode first.
How we test this →
Cookie security flags (Improve)
Cookies without protective flags: XSRF-TOKEN (no HttpOnly). (HttpOnly is not needed for cookies your JavaScript must read.)
2 cookies
Target: Secure; HttpOnly; SameSite
How to fixSet session and login cookies with Secure; HttpOnly; SameSite=Lax (or Strict).
How we test this →
All 10 checks and details
Content-Security-Policy (CSP) (Problem)
No Content-Security-Policy. It is the main browser-side defense against cross-site scripting (XSS).
Missing
Target: Restricts scripts; no unsafe-inline without nonce/hash
How to fixStart with a policy such as: default-src 'self'; script-src 'self' (plus the domains you load scripts from); object-src 'none'; base-uri 'self'; frame-ancestors 'self'. Test it in report-only mode first.
How we test this →
Cookie security flags (Improve)
Cookies without protective flags: XSRF-TOKEN (no HttpOnly). (HttpOnly is not needed for cookies your JavaScript must read.)
2 cookies
Target: Secure; HttpOnly; SameSite
How to fixSet session and login cookies with Secure; HttpOnly; SameSite=Lax (or Strict).
How we test this →
Cross-Origin-Opener-Policy (Info)
Optional hardening: COOP isolates your window from pages opened in popups.
Missing
Target: same-origin
How we test this →
Strict-Transport-Security (HSTS) (Good)
Browsers will only ever connect to this site over HTTPS.
180 days, subdomains, preload
Target: max-age ≥ 15552000 (180 days); includeSubDomains
How we test this →
Clickjacking protection (Good)
Other sites cannot embed your pages in a hidden frame.
SAMEORIGIN
Target: X-Frame-Options: SAMEORIGIN or CSP frame-ancestors
How we test this →
X-Content-Type-Options (Good)
Browsers will not guess file types, which blocks some content-injection attacks.
nosniff
Target: nosniff
How we test this →
Referrer-Policy (Good)
Full URLs are not leaked to other sites.
strict-origin-when-cross-origin
Target: strict-origin-when-cross-origin
How we test this →
Permissions-Policy (Good)
Browser features such as camera and geolocation are restricted.
Set
Target: Disable unused features (camera, microphone, geolocation…)
How we test this →
Software versions hidden (Good)
Response headers do not reveal server software versions.
Hidden
No mixed content (Good)
Every script, stylesheet, frame and image on the page loads over HTTPS.
None
Target: All resources over HTTPS
How we test this →

Response headers we read

servercloudflare
referrer-policystrict-origin-when-cross-origin
x-frame-optionsSAMEORIGIN
permissions-policygeolocation=(), microphone=()
x-content-type-optionsnosniff
strict-transport-securitymax-age=15552000; includeSubDomains; preload

Quality

Accessibility, browser support and layout on every screen size.

Accessibility (WCAG)

No WCAG violations detected by axe-core (40 rules passed).

100/100 A+
Check passed — show details
No automatically detectable WCAG issues (Good)
axe-core found no violations of WCAG 2.2 A/AA rules on this page. Automated tools catch roughly a third of issues, so test keyboard and screen-reader use too.
0 issues
0Critical
0Serious
0Moderate
0Minor
40Rules passed

axe-core 4.13.0 · WCAG 2.2 A/AA + best practices on the rendered desktop page. Score = 100 − 15 per critical, 8 per serious, 4 per moderate and 2 per minor rule failed.

Browser compatibility

Works cleanly in 3 of 3 browser engines (Chromium, Firefox, WebKit).

100/100 A+
All 3 checks passed — show details
Works in Chrome / Edge (Chromium) (Good)
Loads and renders without script errors in Chrome / Edge (Chromium).
633 ms · 0 JS errors
Target: Loads, renders the same content, no script errors
Works in Firefox (Gecko) (Good)
Loads and renders without script errors in Firefox (Gecko).
758 ms · 0 JS errors
Target: Loads, renders the same content, no script errors
Works in Safari (WebKit) (Good)
Loads and renders without script errors in Safari (WebKit).
1.24 s · 0 JS errors
Target: Loads, renders the same content, no script errors
Chrome / Edge (Chromium) screenshot
Chrome / Edge (Chromium)
633 ms · 0 JS errors · 4,600 chars
Firefox (Gecko) screenshot
Firefox (Gecko)
758 ms · 0 JS errors · 4,600 chars
Safari (WebKit) screenshot
Safari (WebKit)
1.24 s · 0 JS errors · 4,600 chars

Responsive layout

The layout fits all 11 tested screen widths.

100/100 A+
All 3 checks passed — show details
Phones (320–414px) (Good)
Content fits the screen at every tested width (414px, 390px, 375px, 360px, 320px).
Fits at 5 widths
Target: No horizontal scrolling
Tablets and foldables (672–1024px) (Good)
Content fits the screen at every tested width (1024px, 834px, 768px, 672px).
Fits at 4 widths
Target: No horizontal scrolling
Laptops and desktops (1280–1440px) (Good)
Content fits the screen at every tested width (1440px, 1280px).
Fits at 2 widths
Target: No horizontal scrolling

Screen widths tested

1440px 1280px 1024px 834px 768px 672px 414px 390px 375px 360px 320px

SEO

What search engines see: meta tags, structure, crawlability and links.

SEO essentials

The homepage responded in 853 ms and landed on www.devteam.co.kr. H1 "MVP부터 AI·앱 개발까지,실제로…", 4,756 characters of text, 12 images, 26 internal links.

95/100 A+
Server response time (TTFB) (Improve)
Time to first byte, measured from our test server in the US (Virginia), is slow. Check page caching and server performance.
853 ms
Target: 0.8 s or less (ideal: 0.2 s)
How to fixAdd page caching (on the server or a CDN) and look for slow database queries and plugins. If your server is far from your visitors, move to a closer region or put a CDN in front of it.
How we test this →
All 18 checks and details
Server response time (TTFB) (Improve)
Time to first byte, measured from our test server in the US (Virginia), is slow. Check page caching and server performance.
853 ms
Target: 0.8 s or less (ideal: 0.2 s)
How to fixAdd page caching (on the server or a CDN) and look for slow database queries and plugins. If your server is far from your visitors, move to a closer region or put a CDN in front of it.
How we test this →
Homepage response (Good)
Search engines can load the homepage normally.
HTTP 200
Target: HTTP 200
HTTPS enabled (Good)
The site is served over a secure connection (HTTPS).
HTTPS
Target: Served over https://
How we test this →
HTTP → HTTPS redirect (Good)
HTTP requests are permanently redirected (301) to HTTPS.
301
Target: 301 permanent redirect
How we test this →
www vs. non-www (Good)
devteam.co.kr redirects to www.devteam.co.kr.
www.devteam.co.kr
Target: One host; the other 301-redirects
Redirect chain (Good)
The URL loads directly, with no redirects.
None
Target: 1 hop or fewer
HTML document size (Good)
The HTML size is reasonable.
79KB
Target: 300 KB or less
Text compression (gzip/Brotli) (Good)
The HTML is sent compressed.
zstd
Target: br or gzip
How we test this →
HTTP/2 or newer (Good)
A modern protocol delivers multiple resources in parallel.
HTTP/2
Target: HTTP/2 or HTTP/3
X-Robots-Tag header (Good)
No header blocks indexing.
None
H1 heading (Good)
The page has exactly one main heading (H1).
MVP부터 AI·앱 개발까지,실제로 운영되는 …
Target: One per page, stating the main topic
Texts
  • MVP부터 AI·앱 개발까지,실제로 운영되는 서비스를 만듭니다
How we test this →
Heading hierarchy (H1–H6) (Good)
The headings follow a logical order.
44
Target: H1 → H2 → H3, in order
Outline
  • MVP부터 AI·앱 개발까지,실제로 운영되는 서비스를 만듭니다 · 1
  • 이런 프로젝트를 주로 맡습니다 · 2
  • MVP 개발 · 3
  • 정부지원사업 MVP · 3
  • AI 연동 개발 · 3
  • 사내 AI 도입 · 3
  • 시스템 연동·사내 시스템 · 3
  • 앱 개발 (Flutter) · 3
  • 이미 운영 중인 서비스도 맡겨 주세요 · 2
  • 웹 긴급지원 · 3
  • AI 코드 완성 · 3
  • 성능·보안 진단 · 3
How we test this →
Text in the HTML (Good)
There is enough text for search engines to read.
4,756 chars
Target: At least 300 characters of text search engines can read
How we test this →
Image alt text (Good)
Every image has an alt attribute.
12/12
Target: alt text on every meaningful image
How we test this →
Image dimensions (width/height) (Good)
Most images have their dimensions set.
12/12
Target: width and height attributes set
How we test this →
Image lazy loading (Good)
Lazy loading is in use.
9/12
Target: loading="lazy" on offscreen images
How we test this →
Internal links (Good)
The homepage links to several internal pages.
26
Target: Links to your key pages
How we test this →
Link text (Good)
Most links have text that describes their destination.
85/85
Target: Text that describes the destination
How we test this →

How the home page responded

Final URLhttps://www.devteam.co.kr/
ResponseHTTP 200 · HTTP/2 · 172.67.161.66
First byte853 ms (from our US server)
servercloudflare
content-typetext/html; charset=utf-8
cache-controlno-cache, private
cf-cache-statusDYNAMIC
content-encodingzstd
strict-transport-securitymax-age=15552000; includeSubDomains; preload
4,756Chars
1,295Words
12Images
44Headings
0External links
26Internal links

Meta tags & link previews

8 key meta items checked: 7 good, 1 to improve, 0 failing. The key tags for link previews are in place (6 passed).

96/100 A+
Meta description (Improve)
The description is long and will be cut off in search results.
118 chars
Target: About 120–160 characters, with a call to action
How to fixPut the key point first and trim it to about 160 characters.
Current text
스타트업 MVP, 정부지원사업 과제, 사내 AI 도입, ERP·그룹웨어 연동, Flutter 앱까지. 기획·디자인·개발·배포·운영을 한 팀이 책임지고 소스코드와 서버 권한을 모두 넘겨드립니다. 1영업일 내 회신.
How we test this →
All 16 checks and details
Meta description (Improve)
The description is long and will be cut off in search results.
118 chars
Target: About 120–160 characters, with a call to action
How to fixPut the key point first and trim it to about 160 characters.
Current text
스타트업 MVP, 정부지원사업 과제, 사내 AI 도입, ERP·그룹웨어 연동, Flutter 앱까지. 기획·디자인·개발·배포·운영을 한 팀이 책임지고 소스코드와 서버 권한을 모두 넘겨드립니다. 1영업일 내 회신.
How we test this →
Language versions (hreflang) (Info)
No hreflang tags. A single-language site does not need them.
None
Search engine verification tags (Info)
No verification meta tags. (You may have verified with an HTML file or a DNS record.)
None
Title tag (Good)
The title is short enough to show in full in search results.
46 chars
Target: About 50–60 characters, key phrase first
Current text
MVP 개발 · AI 개발 · 웹·앱 개발 전문 개발사 | DevTeam Korea
How we test this →
Canonical URL (Good)
The canonical correctly points to the page itself.
https://www.devteam.co.kr/
Target: Absolute URL pointing to the page itself
URL
https://www.devteam.co.kr/
How we test this →
Robots meta tag (Good)
Nothing blocks indexing (default: index, follow).
Not set (allowed by default)
Target: index, follow
How we test this →
Mobile viewport (Good)
The page adapts to mobile screens.
width=device-width, initial-scale=1, viewport-fit=cover
Target: width=device-width, initial-scale=1
How we test this →
Document language (lang) (Good)
The document language is declared.
ko
Target: <html lang="…">, e.g. "en"
Character encoding (Good)
The page is encoded in UTF-8.
UTF-8
Target: UTF-8
Favicon (Good)
A favicon is present. Google shows it as your site icon in search results.
2 declared
Target: icon + apple-touch-icon
og:title (Good)
A link-preview title is set.
MVP 개발 · AI 개발 · 웹·앱 개발 전문 개…
Target: Same as or close to the page title
How we test this →
og:description (Good)
A link-preview description is set.
스타트업 MVP, 정부지원사업 과제, 사내 A…
og:image (preview image) (Good)
The preview image has a good size for sharing.
1200×630
Target: 1200×630 px · under 5 MB
URL
https://www.devteam.co.kr/images/og/home.jpg
Type
image/jpeg
Bytes
65698
Width
1200
Height
630
How we test this →
og:url (Good)
Matches the preferred (canonical) URL.
https://www.devteam.co.kr/
og:type · og:site_name · og:locale (Good)
The supporting tags are set.
3/3
Og:type
website
Og:locale
ko_KR
Og:site name
DevTeam Korea
How we test this →
X (Twitter) card (Good)
An X (Twitter) card is set.
summary_large_image
Target: summary_large_image
How we test this →

Google result (estimated)

DevTeam Korea · https://www.devteam.co.kr/
MVP 개발 · AI 개발 · 웹·앱 개발 전문 개발사 | DevTeam Korea
스타트업 MVP, 정부지원사업 과제, 사내 AI 도입, ERP·그룹웨어 연동, Flutter 앱까지. 기획·디자인·개발·배포·운영을 한 팀이 책임지고 소스코드와 서버 권한을 모두 넘...

Link preview (Facebook, LinkedIn, Slack…)

Structured data

10 schema types in use.

95/100 A+
Required & recommended properties (Improve)
All required properties are present, but some recommended ones are empty: ProfessionalService.telephone, ProfessionalService.openingHoursSpecification or openingHours, ProfessionalService.geo
3 recommended missing
Target: All required properties for each type
How to fixFilling in the recommended properties too lets search results and AI answers make fuller use of your data.
Recommended
  • ProfessionalService.telephone
  • ProfessionalService.openingHoursSpecification or openingHours
  • ProfessionalService.geo
How we test this →
All 7 checks and details
Required & recommended properties (Improve)
All required properties are present, but some recommended ones are empty: ProfessionalService.telephone, ProfessionalService.openingHoursSpecification or openingHours, ProfessionalService.geo
3 recommended missing
Target: All required properties for each type
How to fixFilling in the recommended properties too lets search results and AI answers make fuller use of your data.
Recommended
  • ProfessionalService.telephone
  • ProfessionalService.openingHoursSpecification or openingHours
  • ProfessionalService.geo
How we test this →
Rich result types (Info)
Found types that can enhance your search results: Organization
Organization
JSON-LD structured data (Good)
Found 10 types in 2 blocks.
Organization, ProfessionalService, ImageObject, PostalAddress, Country, ContactPoint and more
Target: Organization · WebSite · schema for each page type
How we test this →
JSON syntax (Good)
Every JSON-LD block is valid JSON.
Valid
Company/brand info (Organization) (Good)
Company/brand entity information is declared.
Organization/ProfessionalService
Target: Organization or LocalBusiness
How we test this →
External profiles (sameAs) (Good)
Official external profiles are linked.
3
Target: Official social, blog and wiki profiles
How we test this →
Site name (WebSite) (Good)
A WebSite schema is present, which Google uses for the site name shown in search results.
Present
Target: WebSite name · url
How we test this →

JSON-LD found on the page (2)

Organization, ProfessionalService, ImageObject, PostalAddress, Country, ContactPoint, WebSite
{
    "@context": "https://schema.org",
    "@graph": [
        {
            "@type": [
                "Organization",
                "ProfessionalService"
            ],
            "@id": "https://www.devteam.co.kr/#organization",
            "name": "DevTeam Korea",
            "legalName": "주식회사 뎁팀",
            "alternateName": [
                "뎁팀",
                "DevTeam",
                "DevTeam Co., Ltd."
            ],
            "url": "https://www.devteam.co.kr/",
            "logo": {
                "@type": "ImageObject",
                "url": "https://www.devteam.co.kr/storage/branding/logo_color_512.png",
                "width": 512,
                "height": 512
            },
            "image": "https://www.devteam.co.kr/images/og/default.jpg",
            "description": "MVP 개발, 정부지원사업 MVP, AI 연동·사내 AI 도입, ERP·그룹웨어 시스템 연동, Flutter 앱 개발, 웹 긴급지원을 제공하는 소프트웨어 개발사. 기획부터 배포·운영까지 한 팀이 책임집니다.",
            "taxID": "433-88-03388",
            "address": {
                "@type": "PostalAddress",
                "streetAddress": "컨벤시아대로 81, 드림시티 5층 509-제이492호",
                "addressLocality": "연수구",
                "addressRegion": "인천광역시",
                "postalCode": "21995",
                "addressCountry": "KR"
            },
            "areaServed": {
                "@type": "Country",
                "name": "KR"
            },
            "contactP...
FAQPage, Question, Answer
{
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
        {
            "@type": "Question",
            "name": "개발 비용은 어떻게 정해지나요?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "필요한 기능과 화면 수, 외부 시스템 연동 여부, 희망 일정에 따라 달라집니다. 상담 내용을 바탕으로 1영업일 안에 범위·일정·견적을 함께 정리해 드리며, 예산이 정해져 있다면 그 안에서 먼저 만들 수 있는 범위를 제안합니다."
            }
        },
        {
            "@type": "Question",
            "name": "기획서가 없는데 상담할 수 있나요?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "네. 대부분 아이디어 설명이나 참고 사이트, 손으로 그린 화면 정도로 시작합니다. 필요하면 기능 정의서(PRD)와 화면 설계를 개발 전에 함께 만듭니다."
            }
        },
        {
            "@type": "Question",
            "name": "정부지원사업 과제로 진행할 수 있나요?",
            "acceptedAnswer": {
                "@type": "Answer",
                "text": "네. 예비·초기창업패키지, 지자체·대학 지원사업 과제는 저희에게 가장 자주 들어오는 의뢰 중 하나입니다. 사업 기간에 맞춘 일정과 법인 명의 견적서·계약서·세금계산서, 결과 보고에 쓸 산출물을 함께 준비합니다. 정부지원사업 MVP 안내를 참고해 주세요."
            }
        },
        {
            "@type": "Question",
            "name": "개발 기간은 보통 얼마나 걸리나요?",
            "acceptedAnswer": {
                "@type": "Answe...

Crawlability: robots.txt & sitemap

Parsed the robots.txt rules. Problems: 0, improvements: 0. URLs in the sitemap: 184; most recent update 2026-09-27. Naver search readiness: 6/8 items ready.

96/100 A+
Naver Search Advisor verification (Improve)
No Naver verification meta tag. Without Search Advisor you cannot see how Naver crawls and shows your site. (Ignore this if you verified with an HTML file.)
Not verified
Target: Registered in Search Advisor · sitemap submitted
How to fixRegister the site at searchadvisor.naver.com and submit your sitemap and RSS feed.
How we test this →
RSS feed (Improve)
No RSS feed link. If you publish often, submitting an RSS feed to Search Advisor helps.
None
Target: Blogs and news sites submit RSS
How to fixAdd <link rel="alternate" type="application/rss+xml" href="/feed"> and submit the feed in Search Advisor.
How we test this →
All 18 checks and details
Naver Search Advisor verification (Improve)
No Naver verification meta tag. Without Search Advisor you cannot see how Naver crawls and shows your site. (Ignore this if you verified with an HTML file.)
Not verified
Target: Registered in Search Advisor · sitemap submitted
How to fixRegister the site at searchadvisor.naver.com and submit your sitemap and RSS feed.
How we test this →
RSS feed (Improve)
No RSS feed link. If you publish often, submitting an RSS feed to Search Advisor helps.
None
Target: Blogs and news sites submit RSS
How to fixAdd <link rel="alternate" type="application/rss+xml" href="/feed"> and submit the feed in Search Advisor.
How we test this →
AI training crawler policy (Info)
AI training crawlers (GPTBot and others) are not blocked. If you do not want your content used for AI training, you can block them selectively.
None blocked
robots.txt file (Good)
robots.txt is served correctly.
HTTP 200 · 1.1KB
Target: /robots.txt returns 200 · text/plain
How we test this →
Search engine crawling (Good)
Google, Bing, Naver (Yeti) and Daum can all crawl the homepage.
All allowed
Target: Google, Bing, Naver and Daum allowed
How we test this →
Sitemap directive (Good)
Tells crawlers where your sitemap is.
1
Target: Sitemap: https://.../sitemap.xml
How we test this →
AI search crawlers (Good)
AI search services such as ChatGPT search, Claude and Perplexity can read and cite your site.
All allowed
Target: ChatGPT, Claude and Perplexity search bots allowed
How we test this →
Sitemap file (Good)
Sitemap found (URL list).
https://www.devteam.co.kr/sitemap.xml
Target: sitemap.xml served · listed in robots.txt
URL
https://www.devteam.co.kr/sitemap.xml
How we test this →
URLs listed (Good)
URLs listed in the sitemap: 184.
184
Target: Close to the number of pages you want indexed
How we test this →
Last modified date (lastmod) (Good)
Each URL has a last-modified date, so changed pages get recrawled quickly.
Latest 2026-09-27
Target: Accurate lastmod values
How we test this →
URL consistency (Good)
All URLs use the canonical host (www.devteam.co.kr) and https.
Consistent
Target: Canonical host · https
How we test this →
Sitemap URL responses (sample of 6) (Good)
All sampled URLs respond with 200 OK.
6/6 OK
Target: All 200 · no redirects
How we test this →
Naver crawler (Yeti) access (Good)
Naver's crawler can crawl the site.
Allowed
Target: Yeti allowed in robots.txt
How we test this →
Text in HTML (server rendering) (Good)
The HTML contains text that Naver's crawler can read.
4,756 chars
Target: Key text included in the HTML
How we test this →
Preview tags (Open Graph) (Good)
Previews display correctly in Naver search and when shared on Naver Blog and Cafe.
Present
Target: og:title · og:description · og:image
How we test this →
Meta description (Good)
A meta description is available for Naver's result snippet.
118 chars
Sitemap (for Search Advisor) (Good)
You have a sitemap to submit to Search Advisor.
Found
Mobile optimization (Good)
A mobile viewport is set.
Viewport set

Search engine crawlers

GoogleGooglebot
Allowed
BingBingbot
Allowed
NaverYeti
Allowed
Daum (Kakao)Daumoa
Allowed

Sitemap

184URLs listed
179with lastmod
2026-09-27Newest update
URL listhttps://www.devteam.co.kr/sitemap.xml
Show robots.txt
# DevTeam Korea (주식회사 뎁팀) — https://www.devteam.co.kr
# AI guidance: https://www.devteam.co.kr/llms.txt
# Full context:  https://www.devteam.co.kr/llms-full.txt

# 기본: 모든 크롤러 허용 (비공개/시스템 영역만 차단)
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /client/
Disallow: /google/
Disallow: /github/
Disallow: /logout
Disallow: /estimate/
Disallow: /pay/
Disallow: /partner/
Disallow: /login
Disallow: /cdn-cgi/
Disallow: /images/contact/

# AI · 답변 엔진(GEO/AEO) 크롤러 — 공개 콘텐츠 학습/인용 환영
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: anthropic-ai
User-agent: Claude-User
User-agent: Claude-SearchBot
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: Bingbot
User-agent: CCBot
Allow: /
Disallow: /admin/
Disallow: /client/
Disallow: /google/
Disallow: /github/
Disallow: /logout
Disallow: /estimate/
Disallow: /pay/
Disallow: /partner/
Disallow: /login
Disallow: /cdn-cgi/
Disallow: /images/contact/

Sitemap: https://www.devteam.co.kr/sitemap.xml
Suggested robots.txt
User-agent: *
Allow: /
Disallow: /admin/

# Allow AI search and answer engines (GEO)
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: PerplexityBot
Allow: /

Sitemap: https://www.devteam.co.kr/sitemap.xml

AI visibility

Whether ChatGPT, Claude, Perplexity and Google AI can find, read and quote you.

AI crawler access

8 of 8 AI search crawlers allowed in robots.txt, 4 of 4 served by your firewall, llms.txt present.

100/100 A+
All 7 checks passed — show details
AI training crawlers (Info)
Training crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot…) are allowed. Blocking them is a content-licensing choice and does not affect AI search answers.
All allowed
AI search crawlers allowed (robots.txt) (Good)
All 8 AI search and answer crawlers may read the site.
8 / 8 allowed
Target: ChatGPT, Claude, Perplexity, Google and Bing search crawlers allowed
How we test this →
AI crawlers not blocked by firewall (Good)
Requests with ChatGPT, Claude and Perplexity crawler user agents received the same page as a browser.
4 / 4 served
Target: Same page for AI crawlers as for browsers
How we test this →
llms.txt (Good)
llms.txt follows the llmstxt.org format: 19 links in 6 sections.
4KB
Target: # Title, > summary, ## sections with links
How we test this →
llms-full.txt (Good)
llms-full.txt offers the full text of your key pages in one file.
Found
Content readable without JavaScript (Good)
The page text is in the HTML itself, so crawlers that do not run JavaScript can read it.
4,756 chars of text
Target: Main text present in the HTML
How we test this →
Quoting allowed (no nosnippet) (Good)
No nosnippet or max-snippet:0 directive, so search and AI answers may quote your text.
Allowed

robots.txt rules for AI and search crawlers

OAI-SearchBotOpenAI · ChatGPT search index
Allowed
ChatGPT-UserOpenAI · Live visits for ChatGPT users
Allowed
GPTBotOpenAI · Model training
Allowed
Claude-SearchBotAnthropic · Claude search index
Allowed
Claude-UserAnthropic · Live visits for Claude users
Allowed
ClaudeBotAnthropic · Model training
Allowed
PerplexityBotPerplexity · Perplexity search index
Allowed
Perplexity-UserPerplexity · Live visits for Perplexity users
Allowed
GooglebotGoogle · Google Search and AI Overviews
Allowed
Google-ExtendedGoogle · Gemini training and grounding
Allowed
BingbotMicrosoft · Bing and Copilot
Allowed
Applebot-ExtendedApple · Apple Intelligence training
Allowed
CCBotCommon Crawl · Open dataset used to train many LLMs
Allowed
meta-externalagentMeta · Meta AI training
Allowed
AmazonbotAmazon · Alexa and Rufus answers
Allowed

Real requests with AI crawler user agents

OAI-SearchBotHTTP 200
Served
GPTBotHTTP 200
Served
ClaudeBotHTTP 200
Served
PerplexityBotHTTP 200
Served

llms.txt

DevTeam Korea (주식회사 뎁팀)
DevTeam Korea(주식회사 뎁팀)는 한국의 소프트웨어 개발사입니다. 스타트업 MVP, 정부지원사업 과제 개발, AI 연동·사내 AI 도입, ERP·그룹웨어·WMS 시스템 연동, Flutter 앱, Electron 데스크톱 앱, 다국어 웹사이트를 기획부터 배포·운영까지 한 팀이 맡고, 운영 중인 사이트의 장애(502·500 에러, 해킹, 인증서 만료)를 긴급 복구합니다. 소스코드와 서버 권한은 모두 고객에게 이관합니다.
Sections: 핵심 사실 (Key facts) · 개발 서비스 (Build) · AI · 시스템 · 운영 · 개선 · 회사 · 자료 · Optional

AI answer readiness

AI answer readiness 100/100: the signals AI uses to understand and quote a site are in place.

100/100 A+
All 7 checks passed — show details
Author or publisher named (Info)
No author or publisher markup on this page. For articles and guides, name the author (Person schema, author meta) to build credibility.
Not named
Brand defined as an entity (Good)
Structured data names your organization and links its official profiles, so AI can tie mentions of "DevTeam Korea" to you.
Organization + 3 profiles
Target: Organization JSON-LD with name, logo, url and sameAs profiles
How we test this →
One consistent brand name (Good)
Your brand name is declared the same way everywhere.
DevTeam Korea
Target: Same name in Organization, WebSite and og:site_name
How we test this →
Questions answered directly (Good)
The page answers questions in a question → answer format, which AI assistants quote readily.
FAQPage schema + 1 question headings
Target: FAQ section or question headings with short answers
Question headings
  • 자주 묻는 질문
How we test this →
Scannable structure (Good)
Content is split into headed sections with lists or tables, so key facts are easy to extract.
12 H2 · 12 lists · 0 tables
Target: Several H2 sections plus lists or tables
How we test this →
Trust pages linked (E-E-A-T) (Good)
The home page links to pages that show who runs the site and how to reach them.
3 / 4
Target: About · Contact · Privacy · Terms linked from the home page
Found
  • about: https://www.devteam.co.kr/about
  • terms: https://www.devteam.co.kr/terms
  • privacy: https://www.devteam.co.kr/privacy
How we test this →
Freshness signals (Good)
Recent update dates are published, which helps AI and search engines trust the information is current.
Last update 2026-09-27
Target: dateModified / sitemap lastmod within 6 months
How we test this →
DevTeam KoreaBrand name AI is likely to use
10Schema.org types on the page
OrganizationProfessionalServiceImageObjectPostalAddressCountryContactPointWebSiteFAQPageQuestionAnswer

What AI says about you

The AI assistant described devteam.co.kr using 4 sources, including your own site.

100/100 A+
All 3 checks passed — show details
AI can describe your site (Good)
Asked "What is devteam.co.kr?", the AI assistant found your site and described it (see the answer below). Check that the description is accurate.
Described
Target: An accurate description when asked "What is devteam.co.kr?"
How we test this →
Your site is cited as a source (Good)
The answer cites your own site, so readers can click through to you.
4 of 4 sources
Target: Own domain among the sources
How we test this →
Brand name appears in the answer (Good)
The answer uses your brand name "DevTeam Korea".
Yes
AI assistant with web search · asked "What is devteam.co.kr?"
DevTeam Korea (devteam.co.kr), operated by DevTeam Co., Ltd., is a South Korea-based software development agency that handles end-to-end digital product creation from initial planning and design to deployment and ongoing operations. The company offers minimum viable product (MVP) development, cross-platform web and mobile applications using frameworks like Flutter and Laravel, enterprise system and ERP integrations, and internal AI solutions such as large language model and RAG implementations. Additionally, it provides technical support services, including emergency website troubleshooting, SEO and performance diagnostics, and post-launch maintenance, while delivering full source code and server ownership to clients. These services are primarily intended for startups, businesses participating in government-supported tech projects, and organizations looking to introduce AI tools or upgrade their internal digital infrastructure.

Sources it used: devteam.co.kr devteam.co.kr devteam.co.kr devteam.co.kr

Answer generated by Google Gemini with Google Search grounding. AI answers change over time and differ between assistants.

Deeper tests for site owners

Load testing (k6), the OWASP ZAP vulnerability scan and the Nuclei CVE scan send heavy or attack-style traffic, so they run only on domains you have verified, as part of paid plans (from $5 for a 1-day pass).

See plans

Test another website

Free, no sign-up. Results appear live as each test finishes.