Website review, no card needed

kathimerini.gr logo

kathimerini.gr website review

Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 86 checks

This review found 38 issues worth fixing on kathimerini.gr, 13 of them high impact, across 86 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.2 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.3 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
217 ms156 msMay 16Oct 31206 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026166 ms
May 23, 2026163 ms
May 30, 2026166 ms
Jun 6, 2026170 ms
Jun 13, 2026177 ms
Jun 20, 2026183 ms
Jun 27, 2026185 ms
Jul 4, 2026186 ms
Jul 11, 2026185 ms
Jul 18, 2026187 ms
Jul 25, 2026188 ms
Aug 1, 2026188 ms
Aug 8, 2026190 ms
Aug 15, 2026194 ms
Aug 22, 2026195 ms
Aug 29, 2026198 ms
Sep 5, 2026203 ms
Sep 12, 2026204 ms
Sep 19, 2026206 ms
Sep 26, 2026210 ms
Oct 3, 2026208 ms
Oct 10, 2026208 ms
Oct 17, 2026206 ms
Oct 24, 2026205 ms
Oct 31, 2026206 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of kathimerini.gr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kathimerini.gr at 0.4 s0.4 s
  2. kathimerini.gr at 0.8 s0.8 s
  3. kathimerini.gr at 1.1 s1.1 s
  4. kathimerini.gr at 1.5 s1.5 s
  5. kathimerini.gr at 1.9 s1.9 s
  6. kathimerini.gr at 2.3 s2.3 s
  7. kathimerini.gr at 2.6 s2.6 s
  8. kathimerini.gr at 3.0 s3.0 s

Speed

7 to fix71
  • Improve image delivery

    3.2 s · 887 KiB

    7 images could be 887 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.

  • Reduce unused JavaScript

    1.2 s · 206 KiB

    About 206 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • 3,229 HTML elements

    The page has 3,229 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    800 ms · 271 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (271 KiB).

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • vogue.gr adds 0 ms

    0 ms

    vogue.gr costs a phone 0 ms of main-thread work and 323 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 8 third-party services on the page

    8 third-party services load with your homepage (piano.io, Other Google APIs/SDKs and Cxense and others), adding 853 KiB and 298 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    72 KiB

    About 72 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 309 ms of it running JavaScript. That is comfortably low.

  • Server response: 471 ms

    471 ms

    Your server sent the HTML in 471 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 17.4 s

    17.4 s

    Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “εκρηξη-στην-πλάκα-ζητάμε-συγγνώμη-564562753”.

  • Time to Interactive: 18.0 s

    18.0 s

    The page becomes fully interactive after 18.0 s. Good is under 3.8 s.

  • Tap response (INP) got 25% slower for real visitors

    +25%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 166 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.6 s

    2.6 s

    The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 130 ms

    130 ms

    Real visitors wait 130 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.09

    0.09

    For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 352 ms

    352 ms

    Real visitors wait 352 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

  • Total Blocking Time: 61 ms

    61 ms

    Scripts block the page for only 61 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix28
  • Page weight: 5.9 MB in 96 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 96 requests on a phone: images 4.9 MB (57), scripts 516 KiB (16) and HTML 222 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    photo-collage.png_25_-1080x607.png weighs 805 KiB. On a phone connection a single image that size takes seconds.

  • 36 images below the first screen load straight away

    36 images further down the page (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 13 images in older formats

    13 images (2.3 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 9 images far larger than shown

    387 KiB

    9 images are downloaded at several times the size a phone draws them, for example photo-collage.png_25_-1080x607.png at 1,080 px wide, shown at 358 px. Resized copies would save about 387 KiB.

  • About 1.7 g of CO₂ per visit

    1.66 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 8690
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 16 text elements with low contrast

    16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (87 elements)

    All page content should be contained by landmarks: 87 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 145 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9280
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found ((untyped)) but with 1 problem, for example “block has no @type”.

  • No XML sitemap

    No XML sitemap at https://www.kathimerini.gr/sitemap-misc.xml, so Google discovers your pages only by following links.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 412 internal links, 42 external

    The homepage links to 412 pages on kathimerini.gr and 42 external pages.

4 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Τα Νέα Σήμερα στην Ελλάδα και τον Κόσμο | Ειδήσεις Online και Έκτακτη Επικαιρότητα τώρα από τη Νο1 Ημερήσια Πολιτική κα…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Νέα και Ειδήσεις από την Ελλάδα και τον Κόσμο | Η ΚΑΘΗΜΕΡΙΝΗ”.

  • Canonical URL set

    The canonical URL is https://www.kathimerini.gr/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

2 to fix37
  • robots.txt blocks 2 AI answer engine crawlers

    2 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.kathimerini.gr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://www.kathimerini.gr/syndromes is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share a meta description

    https://www.kathimerini.gr/ereplica, https://www.kathimerini.gr/newsletters, https://www.kathimerini.gr/games, https://www.kathimerini.gr/columns and https://www.kathimerini.gr/ekpompes use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.kathimerini.gr/syndromes, https://www.kathimerini.gr/ereplica, https://www.kathimerini.gr/newsletters, https://www.kathimerini.gr/games, https://www.kathimerini.gr/kairos-prognosi and https://www.kathimerini.gr/politics and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://www.kathimerini.gr/politics, https://www.kathimerini.gr/economy, https://www.kathimerini.gr/society, https://www.kathimerini.gr/world, https://www.kathimerini.gr/opinion and https://www.kathimerini.gr/culture and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 pages slow to respond

    https://www.kathimerini.gr/culture, https://www.kathimerini.gr/columns, https://www.kathimerini.gr/ekpompes, https://www.kathimerini.gr/k/gastronomos and https://www.kathimerini.gr/eortologio took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 186 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.kathimerini.gr' has been b…”.

2 checks passed
  • Tap targets are thumb-sized

    67 of 76 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 111 words

    The homepage has only about 111 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 16 other companies contacted

    Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at kathimerini.gr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on kathimerini.gr, including 12 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25