On-page SEO checker

Check the basics that decide whether search engines can reach, read and understand your page. The test fetches the HTML the way a crawler does, without running JavaScript, and checks HTTPS and redirects, server response time, compression, the H1 and heading outline, the amount of text, image alt text and internal links. Every warning and failure comes with a specific fix.

Runs only this test. Want everything? Run all 18 tests from the home page.

What this test checks

Reachability and HTTPS

Whether the page answers with HTTP 200 over HTTPS, and whether plain-HTTP requests are sent to HTTPS with a permanent 301 or 308 redirect.

Redirects and www consolidation

How many redirects the URL takes to reach the final page, and whether the www and non-www versions of your domain lead to one preferred host.

Server response time (TTFB)

Time to the first byte of the HTML, measured from our test server in Virginia, USA.

Size, compression and HTTP version

HTML document size, gzip, Brotli or zstd compression, and whether the server supports HTTP/2 or HTTP/3.

Indexing blocks

An X-Robots-Tag: noindex response header, a common leftover from staging setups that keeps the page out of search results.

H1 and heading outline

Exactly one H1 that states the topic, H2 subheadings, and no skipped levels such as an H2 followed directly by an H4.

Text in the HTML

How much readable body text the raw HTML contains, which exposes pages that are drawn entirely by JavaScript.

Images and internal links

Alt text and width and height on images, lazy loading on image-heavy pages, the number of internal links and how descriptive their link text is.

Sample result

A real result for devteam.co.kr, tested 1 hour ago.

SEO essentials

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

95/100A+
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.
825 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

How the home page responded

Final URLhttps://www.devteam.co.kr/
ResponseHTTP 200 · HTTP/2 · 104.21.34.129
First byte825 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

How it works

  1. Our test server in Virginia, USA, requests the URL you enter together with its http://, www and non-www versions, following up to 5 redirects.
  2. Requests identify themselves as WebPSQCBot/3.0, time out after 15 seconds and read up to 3 MB of HTML.
  3. The HTML is analyzed as delivered, without running JavaScript, so text that scripts add later is not counted.
  4. Every URL and redirect hop must use http or https on port 80 or 443 and resolve to public IP addresses; private and internal addresses are refused.
  5. Only the URL you enter is analyzed, usually in about 6 seconds; the site crawl test checks your other pages.

How it is scored

The score uses our item-weighted formula: a pass earns full credit, a warning half and a fail none. Page status, HTTPS, server response time and the H1 count 3×; the HTTPS redirect, www consolidation, redirect chain, compression, body text, image alt text and internal links 2×; HTML size, HTTP version, heading order, image dimensions, lazy loading and link text 1×. A noindex header, or a script-heavy page with almost no text in its HTML, counts 3× when it fails.

CheckGoodNeeds workPoor
Server response time (TTFB, from Virginia)0.8 s or less0.8–1.8 sOver 1.8 s
Redirects before the final URL0–123 or more
HTTP to HTTPS redirect301 or 308302 or 307 (temporary)No redirect
H1 headingsExactly one, with textSeveral, or emptyNone
Text in the HTML (characters, not counting spaces)300 or moreUnder 300Under 150 with 3+ external scripts
Images without an alt attributeNoneUp to 20%Over 20%
Unique internal links5 or more1–4None

Grades: A+ 95–100 · A 90–94 · B 80–89 · C 70–79 · D 60–69 · F below 60.

FAQ

How do I check my website's SEO for free?
Enter your URL and run this test. It fetches the page from our server and checks reachability, HTTPS, redirects, server response time, headings, body text, image alt text and internal links, with a fix for every warning and failure. For titles, descriptions and share previews, run the meta tags test; for crawl rules and sitemaps, run the crawlability test.
Should a page have only one H1?
HTML allows several H1 elements, and Google has said that multiple H1s do not hurt rankings. This test still recommends one H1 per page, because a single main heading states the topic clearly for search engines, AI assistants and screen-reader users. More than one H1 is a warning; a missing H1 fails.
What is a good server response time for SEO?
This test passes a time to first byte of 0.8 seconds or less and fails anything over 1.8 seconds, measured from our server in Virginia, USA. Google reduces its crawl rate when a site responds slowly, and a slow first byte delays everything else on the page. Page caching, a CDN and faster database queries are the usual fixes.
Why does the test find almost no text on my page?
The test reads the HTML your server sends and does not run JavaScript. If a framework draws your content in the browser, the HTML may contain only an empty container, and crawlers that do not render JavaScript, including most AI crawlers, see nothing. Server-side rendering or static generation puts the text into the HTML.
Does it matter whether my site uses www or not?
Either works for SEO. What matters is choosing one: the other version should 301-redirect to it, and your canonical tags should point to it. If both versions serve the page, search engines may treat them as duplicates and split ranking signals between them.