saliotitegr.info
saliotitegr.info - Home - 'Profesionálna príprava na STK a emisné kontroly s overeným kontrolným zoznamom.'
0 failed · 6 warnings · 23 passed
Audited Sun, 12 Jul 2026 21:45:41 GMT · https://saliotitegr.info/
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "saliotitegr.info - Home - 'Profesionálna príprava na STK a emisné kontroly s overeným kontrolným zoznamom.'" (107 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:url
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:url tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
7 passing checks
- Meta descriptionMeta description is "Odborná príprava vozidiel na STK a emisnú kontrolu v Bratislave. Kontrolný zoznam za 30 €, diagnostika za 45 €. Kontakt: +421918856318." (135 characters)
- Canonical URLCanonical href is "https://saliotitegr.info/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: index, follow
Content & Structure
21.9/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
2 h1 headings found: "Kontrolný zoznam najčastejších príčin neúspechu", "Informácie o saliotitegr.info"
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 ("Informácie o saliotitegr.info") to h3 ("Presná príprava STK")
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 count1944 words of visible text
- Image alt text6 of 6 images have alt text
- Structured data (JSON-LD)JSON-LD types found: WebPage
- HTML lang attribute<html lang="sk">
- JavaScript-dependent contentvisible text ~11712 chars in the initial HTML
- Internal linking23 internal, 0 external links
Technical
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
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://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte48 ms
- Reasonable HTML size45.5 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.