Is Your Site Marketing-Hygienic?

Goal

Give the page exactly one <h1> that states what it's about, so people and crawlers get a clear entry point into the content outline.

Result

Exactly one <h1>: "Költöztetés Budapesten, vidéken és külföldön szakszerűen"

Goal

Keep heading levels sequential (H1 → H2 → H3) so screen readers and crawlers can build an accurate document outline.

Result

Heading levels increase in order, without skipping a level.

Goal

Mark header, nav, main, and footer regions semantically so screen readers and agents can jump straight to the right part of the page.

Result

header, nav, main, and footer landmarks are all present.

Goal

Give every <img> an alt attribute — descriptive text for meaningful images, empty alt="" for purely decorative ones.

Result

146/146 images have an alt attribute.

Goal

Write link text that describes the destination on its own, without relying on surrounding context — screen reader users often tab through links in a list.

Result

No generic ('click here'/'read more') or empty links found.

Goal

Give every form field a visible <label> tied to it (for/id or wrapping), and make validation errors reach screen readers — native browser validation, or aria-invalid plus an error message linked with aria-describedby or an aria-live/role=alert region.

Result

17/17 form fields have a visible label.

Goal

Every action (book, buy, send, subscribe) is a real <button> or <a href> with an accessible name, so screen readers and agents can tell what will happen — a clickable <div> or an icon-only button is invisible as an action.

Result

27 button(s), all with an accessible name; no clickable <div>/<span> found.

Goal

Menus and site navigation are plain <a href> links inside <nav>, present in the server HTML, so keyboard users can Tab through them and crawlers/agents that skip JavaScript can still discover every page.

Result

88 navigation link(s) found in 5 <nav> landmark(s) in the initial HTML.

Goal

Every link, button and form control must be focusable — reachable with the Tab key — because that is also how agents find what they can act on. Controls with tabindex="-1", links without an href and javascript: links are invisible to both.

Result

No links or controls removed from the keyboard order (no negative tabindex, no href-less or javascript: links).

Goal

Click the logo, put the mouse away and press Tab: every link — including drop-down and sub-menu items — must receive visible focus in a sensible order. Then open DevTools (F12) → Accessibility and check that each button and link shows a role, a name, enabled and focusable.

Result

Manual check — the scanner reads the HTML but cannot press Tab in a real browser.

Goal

Pass an automated accessibility audit run in a real browser: Lighthouse's accessibility category (axe-core rules) should score 90+ with no failing audits. Confirm with WAVE (wave.webaim.org) — the target there is an AIM score of 9 out of 10.

Result

Lighthouse accessibility 100/100 — no failing audits.

Goal

Identify the rendering mode and keep key content server-rendered or static (SSR/SSG). Many AI/LLM crawlers never execute JavaScript, so content that only appears after hydration is invisible to them.

Result

Rendering mode: server-rendered or static (SSR/SSG) — WordPress. ~17474 characters of visible text arrive in the server HTML.

Goal

Don't make JavaScript the only way to understand or use the page: "Load more" and infinite scroll need real pagination links, forms need a <form> with an action and a submit button, interactive content needs its HTML in the page with JavaScript only as enhancement.

Result

No JavaScript-only pagination or forms found in the server HTML.

Goal

Keep total JavaScript under 100 KB gzipped — ideally 0–50 KB (hard ceiling ~170 KB). The average site ships ~700 KB of JavaScript in ~20 requests per page; every extra KB costs load time, carbon, and agent parsing effort.

Result

~3 KB of JS (transfer size, i.e. gzipped/brotli where the server compresses) across 1 sampled file(s).

Goal

Every third-party script (tag manager, analytics, pixels, chat widgets, overlays) should earn its place: each one adds JavaScript, delays interaction, and sends visitor data elsewhere. Keep the ones you act on; remove the rest.

Result

No third-party scripts in the initial HTML.

Goal

Keep the total transferred weight of the page at or under ~270 KB for an A+ carbon rating (≤ ~530 KB still earns an A). For scale: static HTML ~0.1 MB loads in 0.3–0.8 s, a standard React app ~1.2 MB in 1.2–2.5 s, a heavy framework ~4.8 MB in 4–8 s — and conversion is about 3× higher at 1 s than at 5 s. Images are usually the biggest lever.

Result

~179 KB transferred — HTML 93 KB · CSS 6 KB · JS 3 KB · images 77 KB (14 sampled) · 20 requests referenced in the HTML (average site: ~20).

Goal

The server should start answering within ~800 ms (Google's "good" TTFB; ≤ 600 ms is better) and deliver the whole HTML well within the 1–5 seconds AI crawlers wait before giving up. Slow hosting, no page cache or a heavy theme/plugin stack delays everything after it — for visitors and crawlers alike.

Result

The page's HTML started arriving after ~136 ms (best of two requests from our server on a warm connection); the complete HTML took ~510 ms on a cold connection, the way a crawler meets it (AI crawlers time out after 1–5 s).

Goal

Serve HTML, CSS and JavaScript compressed (Brotli or gzip). It typically cuts text transfer by 70–80 % at no cost — what optimisation plugins call "zip".

Result

6/6 text resources served compressed (HTML: gzip).

Goal

Every page builder and every plugin that loads its own CSS/JS adds a layer between your content and the reader. Clean up before you add: fewer plugins, a light theme, no builder where the block editor or plain HTML will do.

Issue

Divi page builder in use.

How to implement

List the plugins that load files on this page and remove or replace the ones you can live without; load the rest only where they're needed. For new pages, prefer a lightweight theme (e.g. GeneratePress) and the block editor over a page builder.

Resources

Goal

Pass Google's Core Web Vitals on mobile: Largest Contentful Paint ≤ 2.5 s, Interaction to Next Paint ≤ 200 ms (lab stand-in: Total Blocking Time ≤ 200 ms), Cumulative Layout Shift ≤ 0.1.

Result

LCP 1.4 s (lab), TBT 0 ms (lab), CLS 0.000 (lab) · Lighthouse performance 99/100. Source: Google PageSpeed Insights (mobile); "field" = real Chrome users, "lab" = one Lighthouse run.

Goal

JavaScript that loads but never runs on this page is pure cost. Lighthouse's "Reduce unused JavaScript" audit measures it; the target is under 50 KB of unused JavaScript (and under 100 KB of JavaScript in total).

Result

~0 KB of JavaScript could be removed according to Lighthouse (counts every script loaded during the run, including ones other scripts load later — so it can exceed the JS weight sampled from the HTML above).

Goal

Describe the page's main entity (who you are, what you offer) as JSON-LD so search engines and AI agents can read it as structured facts, not prose to interpret.

Result

2 JSON-LD block(s) found.

Goal

Keep every JSON-LD block syntactically valid — a single stray comma invalidates the whole block.

Result

All JSON-LD blocks are valid JSON.

Goal

Use a well-known schema.org @type (Organization, LocalBusiness, Product, Service, Article, FAQPage, etc.) so search engines and agents recognize what kind of thing this page describes.

Result

Found: Place, MovingCompany, Organization, WebSite, ImageObject, WebPage, FAQPage

Goal

Keep a single, consistent Organization/LocalBusiness record so crawlers and AI agents don't get contradictory facts about who you are.

Result

Organization/LocalBusiness data is consistent.

Goal

Every structured-data object on the page passes the official Schema Markup Validator (validator.schema.org) with no errors or warnings: valid types, valid property names, valid values.

Result

6 object(s) validated (WebPage, MovingCompany / Organization, PostalAddress, Country, Place, GeoCoordinates, …): 0 error(s), 0 warning(s).

Goal

Give each page structured data for a type Google can show as a rich result (Article, Product, FAQ, Breadcrumb, Local business, Event, Recipe, Video, Software app…) with the properties it requires. FAQ results are shown only for some sites in Google, but the markup still helps AI answers.

Result

Complete rich-result markup: Organization (logo/knowledge panel), FAQ.

Goal

Say who stands behind the page in a form machines can read — a Person/Organization in JSON-LD with a name and a url/email/sameAs, an author/publisher property, a <meta name="author">, or a rel="author" link. Claims without a named, reachable author get mentioned, not cited.

Result

JSON-LD names a Person/Organization with a URL, email or sameAs links.

Goal

Keep content current and say so: show when it was published or last updated (e.g. "Updated September 2026 · Author: Name") in a form machines can read (datePublished/dateModified in JSON-LD, a <time datetime> element, or article:modified_time), so agents can tell current content from stale content.

Result

JSON-LD carries datePublished/dateModified; most recent date 2026-10-20 (3 day(s) ago).

Goal

Give every page a descriptive <title>, a meta description, a canonical URL, the page language, a viewport tag and Open Graph title/image — the metadata search engines, AI crawlers and link previews read first.

Result

Title (67 chars), description (154 chars), canonical, lang="hu-HU", viewport and Open Graph tags are present.

Goal

Show proof that you did the work: link an author/about page and case studies, references or client examples (with dates) from your pages. "We offer the best deal in town" — can you prove it? Without proof you get mentioned, not cited.

Result

Author/about link: yes; case studies/references link: yes.

Goal

Ask honestly for each authority page: if this page did not exist, would it matter? It should only exist if its content exists only here. If it is a rewrite of what 16 other sites say, rethink it — AI crawlers look for the single best, unique answer.

Result

Manual check — uniqueness of content can't be judged by a scanner.

Goal

Serve every page over HTTPS, redirect http:// to https://, and load no images, scripts or styles over plain http — browsers, search engines and AI systems treat insecure pages as less trustworthy.

Result

HTTPS, http:// redirects to https://, HSTS enabled, no mixed content.

Goal

Every link on the page leads somewhere: broken links waste crawl budget, break agents' paths through your site and signal neglected content.

Result

25 of 88 link(s) tested (internal first); none broken.

Goal

Publish a robots.txt file so crawlers know what they may fetch before they fetch anything else.

Result

Found at https://herkulestrans.hu/robots.txt

Goal

Give crawlers a complete, structured list of your URLs instead of making them discover pages by following links alone.

Result

robots.txt references a sitemap.

Goal

Decide intentionally whether GPTBot, PerplexityBot, ClaudeBot, and similar AI crawlers can access your content, instead of leaving them on the default catch-all rule.

Result

robots.txt has explicit rules for: ChatGPT-User, PerplexityBot, plus a Content-Signal policy.

Goal

Search engines and AI crawlers may only use pages that are indexable: HTTP 200, no noindex in a robots meta tag or X-Robots-Tag header, and a canonical that points to the page itself.

Result

HTTP 200, no noindex, and the canonical (if any) points to this URL.

Goal

robots.txt must not block the crawlers that fetch pages for search and for users' questions (Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot/User…). Blocking AI training crawlers is a legitimate policy choice; blocking search and assistant crawlers makes you invisible in AI answers.

Result

No search or assistant crawler is blocked from the site root. No training crawler is blocked either.

Goal

When robots.txt allows them, AI crawlers (GPTBot, ClaudeBot, PerplexityBot) must actually get the same page as a visitor, within the 1–5 seconds they wait — no firewall block, no challenge page, no empty shell.

Result

Requests identifying as GPTBot (1635 ms), ClaudeBot (146 ms), PerplexityBot (154 ms) got the full page.

Goal

State a machine-readable policy on whether your content may be used for search indexing, AI-agent answers, and AI model training — separately.

Result

robots.txt declares a Content-Signal policy (search / ai-input / ai-train).

Goal

Offer a short, curated Markdown index of your most important pages so LLMs and agents don't have to guess which pages matter.

Result

llms.txt found — a curated entry point for LLMs/agents.

Goal

Offer a clean Markdown version of the page — what AI agents prefer to read — at least for your top five authority pages: a <link rel="alternate" type="text/markdown">, content negotiation on Accept: text/markdown, or a .md twin.

Result

A Markdown version of this page is available via a <link rel="alternate" type="text/markdown"> in the page: 17 KB with headings and links; tip: add frontmatter with title and canonical.

Goal

Clear, extractable content gets you cited when people ask AI to compare and shortlist: what you offer, what it costs, answers to common questions (FAQs) and how to contact or book you — reachable straight from the navigation or on the page.

Result

Found: services, pricing, contact, FAQs.

Goal

Structure content so each section covers one idea, answers its question early and is understandable on its own — that is good writing first, and it lets search and AI systems match a section to a question. Use subheadings, short paragraphs and lists; avoid "as mentioned above"; don't split text artificially. There is no ideal chunk size: a chunk ends where a thought is complete.

Issue

Structure issues: 20 sections averaging ~28 words — possibly split artificially.

How to implement

Give each idea its own descriptive subheading (questions work well when they are your readers' questions), put the answer in the first sentence, keep paragraphs short, use lists where they help skimming, and rewrite cross-references so each section stands alone.

Resources

Goal

Once a month, ask the main AI platforms (ChatGPT, Gemini, Claude, Perplexity, Copilot) the questions your clients ask. Check whether you are mentioned and cited, in an incognito window and logged in. If someone else is cited, study why and do a better job than they do.

Result

Manual check — the scanner can't see AI answers. Pair it with the vanish test and proof-of-work checks.

Goal

Estimate CO₂ per page view with the Sustainable Web Design model v4 and keep it at or below 0.095 g (A+); 0.186 g (A) is acceptable. The global median is about 0.36 g.

Result

~0.027 g CO₂/view (rating A+), estimated from ~179 KB transferred (HTML + sampled CSS/JS/images), Sustainable Web Design v4. websitecarbon.com's calculator did not answer during this scan (HTTP 403).

Goal

Serve images compressed and at their display size, in WebP or AVIF, and lazy-load the ones below the fold. Images are usually the biggest lever on page weight and carbon.

Issue

11 of 11 raster image(s) in PNG/JPEG/GIF instead of WebP/AVIF; 1 below-the-fold image(s) without loading="lazy".

How to implement

Export images at the pixel size they are displayed (2× for retina at most), convert to WebP/AVIF (keep a JPEG fallback in <picture> if needed), and add loading="lazy" to every image that isn't visible at first paint.

Resources

Goal

Serve static assets with long cache lifetimes (Cache-Control max-age ≥ 1 day, ideally immutable) from a CDN close to the visitor, so repeat views and far-away visitors cost almost nothing.

Result

CDN/edge cache detected: Amazon CloudFront; 16/16 sampled assets have a cache lifetime of a day or more (3 third-party tag files not counted — the provider sets their cache).

Goal

Host on infrastructure that runs on renewable energy or is verified green (The Green Web Foundation directory). It lowers the data-centre share of every page view's footprint.

Issue

Hosting is not verified as green.

How to implement

Ask your host whether they are listed with The Green Web Foundation, or move to a verified green host/CDN when feasible.

Resources

Goal

Optional: publish an agent manifest at /.well-known/ (ai-agent.json pointing agents to your critical pages, or ai-plugin.json describing a callable API with name, description, auth and OpenAPI spec location).

Issue

No /.well-known/ai-agent.json or ai-plugin.json manifest found (optional, early-stage convention).

How to implement

If you expose an API agents could call on your behalf (booking, ordering, lookups), publish a manifest at /.well-known/ai-plugin.json describing the endpoint, auth, and an OpenAPI spec.

Goal

Publish a /.well-known/security.txt (RFC 9116) with a contact method — a small, standard trust signal that you're a real, reachable operator.

Result

Found a security.txt file.