morqelanivztw.info
Kurse programmieren & UX/UI-Design | Morqelanivztw
1 failed · 6 warnings · 22 passed
Audited Wed, 29 Jul 2026 15:45:06 GMT · https://morqelanivztw.info/
Meta & Head
20.1/25
Title, description, canonical, social tags — what search engines read first.
Open Graph tagsmedium impactlow effort
No Open Graph tags found
Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.
Canonical URLmedium impactlow effort
No <link rel="canonical"> found
When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
6 passing checks
- Title tag<title> is "Kurse programmieren & UX/UI-Design | Morqelanivztw" (54 characters)
- Meta descriptionMeta description is "Kurse für Programmierung und UX/UI-Design von Morqelanivztw. Klare Kursstruktur, transparente Kosten, feste Inhalte und flexible Zahlungsoptionen." (146 characters)
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Page allows indexingrobots: index, follow
Content & Structure
21.9/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
7 h1 headings found: "Klare Struktur, transparente Kosten und praxisnahe Inhalte für deinen nächsten Schritt.", "Über Morqelanivztw", "So läuft die Zusammenarbeit ab"
Multiple h1s split the page's main-topic signal, leaving search engines to guess which headline actually defines the page. Keep the one h1 that best states the primary topic and demote the rest to h2 or h3, so the outline reads as a single subject with subtopics. A frequent culprit is a site logo or blog title wrapped in an h1 inside the shared header template — change that to a <div> or <p> and reserve h1 for the page's own content.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("Über Morqelanivztw") to h3 ("Transparente Kurskosten")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
6 passing checks
- Word count825 words of visible text
- Image alt text9 of 9 images have alt text
- Structured data (JSON-LD)JSON-LD types found: LocalBusiness
- HTML lang attribute<html lang="de">
- JavaScript-dependent contentvisible text ~7445 chars in the initial HTML
- Internal linking24 internal, 10 external links
Technical
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
10 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte186 ms
- Reasonable HTML size24.4 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.