junoxen.site
Junoxen | Rozwój kariery w sektorze edukacji
1 failed · 7 warnings · 21 passed
Audited Thu, 16 Jul 2026 01:01:10 GMT · https://junoxen.site/
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
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.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image, 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:image, og:url tags 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.
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 "Junoxen | Rozwój kariery w sektorze edukacji" (44 characters)
- Meta descriptionMeta description is "Programy i ścieżki rozwoju dla specjalistów edukacyjnych w Polsce. Skoncentrowane na mierzalnych wynikach, szybkim wdrożeniu i kontroli jakości." (144 characters)
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Page allows indexingNo restrictive robots meta tag
Content & Structure
23.4/25
Headings, copy depth, images, structured data, internal linking.
Structured data (JSON-LD)medium impactmedium effort
No JSON-LD structured data blocks found
Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.
7 passing checks
- Single H1 heading1 h1 found: "Rozwijaj kompetencje"
- Heading hierarchy21 headings in order without skipped levels
- Word count810 words of visible text
- Image alt text3 of 3 images have alt text
- HTML lang attribute<html lang="pl">
- JavaScript-dependent contentvisible text ~18609 chars in the initial HTML
- Internal linking18 internal, 0 external links
Technical
19.9/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
XML sitemap availablemedium impactlow effort
sitemap.xml exists but is not valid XML
Your sitemap exists but isn't valid XML, so search engines reject the whole file and you get none of its discovery benefit — worse than having no sitemap, because you probably believe it's working. Regenerate it with your framework's built-in generator or a sitemap library rather than hand-editing; unescaped ampersands in URLs (& instead of &) are the most common breakage. Validate before deploying, and check the Sitemaps report in Google Search Console afterwards — it surfaces parse errors explicitly.
Fast time to first bytehigh impactmedium effort
943 ms
Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.
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.
Missing pages return 404low impactlow effort
missing paths return a non-404 status (soft 404)
URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.
8 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
- Reasonable HTML size39.1 KB
- 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.