SEO report for www.paranormalium.pl

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to paranormalium.pl…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap found at https://www.paranormalium.pl/sitemap-google-news.php with 1,032 URLs.

  Declared in robots.txt.

  This page is NOT listed in it.

  No lastmod dates – add accurate ones so search engines know what changed.

• ✓

  Canonical URLhigh

  Canonical: https://www.paranormalium.pl/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://paranormalium.pl/ → https://www.paranormalium.pl/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  paranormalium.pl redirects to www.paranormalium.pl.

Search snippet & sharing 63%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Radio Paranormalium”

  About 193px of Google's ~580px desktop width – short; use the space.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✓

  Meta descriptionhigh

  120 characters, ~765px of ~990px.

  Good length.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

• ✗

  Open Graph & social cardsmedium

  Open Graph title or image missing.

  No twitter:card tag.

  Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.

  Make the tags with the free Open Graph generator

  Read the guide: does social media help SEO?

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="pl-PL"

Content quality 58%

Is there enough clear, useful text that matches what the page targets?

• ✓

  Word countmedium

  837 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• i

  Readabilitymedium

  Reading-ease scores only work for English; this page is lang="pl-PL".

• ✓

  Topic focushigh

  1 of 1 title keywords appear in the main content.

• ✗

  H1 headingcritical

  No H1 heading.

  Fix: Use one H1 that states the page topic with its main keyword.

• ✓

  Heading structuremedium

  2 headings for 837 words.

  Levels are in order.

• !

  Text-to-code ratiolow

  9% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 38%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✗

  llms.txtlow

  No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.

  Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✗

  Question-led contentmedium

  No headings phrased as questions.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✗

  Entity clarityhigh

  No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✗

  Freshness signalsmedium

  No published/updated date found.

  Fix: Show a 'last updated' date and add dateModified to your structured data.

• ✗

  Trust pages (E-E-A-T)medium

  No links found to about, contact or privacy pages.

  Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 0%

Machine-readable facts for rich results and AI.

• ✗

  JSON-LD present & validhigh

  No JSON-LD structured data.

  Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).

  Make valid code with the free schema generator

  Read the guide: schema markup

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 69%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  149 internal and 19 external links.

• !

  Anchor text qualitymedium

  Same text used for different pages: “pomoc techniczna”, “archiwum podcastów”, “czytaj więcej”.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• !

  Broken links (sample)high

  Checked 12 internal link(s).

  Broken: /kontakt.html (500).

  1 link(s) point to a redirect – link to the final address instead.

  Fix: Fix or remove links that return errors, and update links that redirect.

Performance 63%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• !

  Server response (TTFB)high

  1513 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• ✓

  HTML sizemedium

  124 kB of HTML.

• ✓

  Compressionmedium

  Compressed with gzip.

• ✓

  Render-blocking resourceshigh

  0 blocking script(s) and 0 stylesheet(s) in <head>.

• !

  Scripts & third partiesmedium

  11 script tag(s); files loaded from 2 other domain(s): fonts.gstatic.com, cdn.onesignal.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  32 image(s).

  4 without width/height – can cause layout shift (CLS).

  The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.

  10 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✗

  Cachinglow

  No Cache-Control header.

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• i

  HTTP/3low

  Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.

Security 67%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✗

  HSTSmedium

  No Strict-Transport-Security header.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: CSP.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✗

  Server fingerprintlow

  X-Powered-By reveals “PHP/8.5”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 83%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: user-scalable=yes, initial-scale=1, maximum-scale=10, minimum-scale=1, width=device-width

• ✓

  Image alt textmedium

  All 32 images have alt text.

• ✗

  Form labelsmedium

  14 of 20 form field(s) have no label.

  Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).

• ✓

  Link nameslow

  Every link has a readable name.

• ✓

  Tap-to-contactmedium

  One-tap contact: phone and email.

Local SEO 33%

Signals that help you appear in Google Maps and 'near me' searches.

• ✗

  LocalBusiness markuphigh

  No LocalBusiness structured data.

  Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Contact details on pagemedium

  A UK phone number is shown.

  No postcode found (fine for service-area businesses).

  An email link is shown.

• ✗

  Map & directionslow

  No map or directions link.

  Fix: Add a Google Maps directions link so customers can find you.

  Read the guide: the local SEO checklist