SEO report for www.centrum.cz

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 centrum.cz…

Indexing & crawling 88%

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.centrum.cz/news-sitemap.xml with 776 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

  No canonical tag.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://centrum.cz/ → https://www.centrum.cz/

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

• ✓

  www / non-wwwmedium

  centrum.cz redirects to www.centrum.cz.

Search snippet & sharing 83%

How the page looks in Google results and when shared.

• ✓

  Title tagcritical

  “Centrum.cz: Fandíme dobrému obsahu”

  About 354px of Google's ~580px desktop width.

• ✓

  Meta descriptionhigh

  113 characters, ~724px 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="cs"

Content quality 38%

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

• ✓

  Word countmedium

  3,284 words of main content (inside <main>).

  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="cs".

• ✗

  Topic focushigh

  0 of 3 title keywords appear in the main content (missing: fandíme, dobrému, obsahu).

  Fix: Use your main title phrases naturally in the opening paragraph and headings.

  Find the phrases people search with the free keyword generator

  Read the guide: how to write SEO content

• ✗

  H1 headingcritical

  No H1 heading.

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

• ✓

  Heading structuremedium

  20 headings for 3284 words.

  Levels are in order.

• ✓

  Text-to-code ratiolow

  72% of the HTML is visible text.

AI search readiness 44%

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

  1 heading(s) phrased as questions, e.g. “Do obytné čtvrti na Floridě se zřítilo soukromé letadlo. Po dopadu exp”.

  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 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): WebSite, SearchAction, EntryPoint.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  92 internal and 72 external links.

• ✗

  Anchor text qualitymedium

  No link text points to two different pages.

  2 link(s) with no text at all.

  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).

  No broken links found.

Performance 31%

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

• !

  Server response (TTFB)high

  1254 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

  980 kB of HTML – heavy for phones (we only analysed the first 1 MB).

  Fix: Remove inline bloat, base64 images and unused markup.

• i

  Compressionmedium

  Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.

• !

  Render-blocking resourceshigh

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

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  29 script tag(s); files loaded from 11 other domain(s): ban.maxa.cz, hpx-cdn.xsd.cz, connect.facebook.net, platform.twitter.com, prod-snowly-sasic.stdout.cz, cdn.performax.cz….

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

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  162 image(s).

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

  7 image(s) after the first three aren't lazy-loaded.

  145 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

  Cache-Control: public, max-age=180, s-maxage=180, stale-while-revalidate=59

• 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: none.

  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 “Next.js”.

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

Mobile & accessibility 58%

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

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1

• ✓

  Image alt textmedium

  All 162 images have alt text.

• ✗

  Form labelsmedium

  3 of 3 form field(s) have no label.

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

• ✗

  Link nameslow

  2 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✗

  Tap-to-contactmedium

  No tel: or mailto: links.

  Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

  Read the guide: mobile-friendly websites

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).

• ✗

  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