kde.org website review

18 images could be 7.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

36 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

About 27 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

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

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

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

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

Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

Your homepage downloads 14.3 MB in 57 requests on a phone: images 13.8 MB (46), fonts 411 KiB (3) and scripts 82 KiB (3). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example fullscreen_with_apps.png at 2,880 px wide, shown at 270 px. Resized copies would save about 3.7 MB.

3 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

16 images (6.1 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.

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

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

10 tap targets are too small or too close together to hit reliably with a finger.

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

4 links inside paragraphs rely on colour alone to stand out.

1 element hidden from screen readers can still receive keyboard focus.

1 image has no alt text, which hurts accessibility and image search.

3 visible links have no text or label, so screen readers cannot say where they go.

Your title is only 20 characters: “Home - KDE Community”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“What is KDE?”, “Plasma” and “Community”). One clear main headline is easier for people and search engines.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 90 pages on kde.org and 61 external pages.

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.

There is no /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.

/, /bs and /et all use the title “Home - KDE Community”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/support, /bs and /et use the same meta description. A description written for each page earns more clicks.

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

3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 links from your homepage to your own site are broken, for example https://kde.org/ga/ (network).

2 links to other sites are dead, for example https://kde.slimbook.es/ (404).

HSTS is set, but max-age is 182 days; one year is the recommended minimum.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

kde.org is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

kde.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage carries about 794 words of visible text.

kde.org has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 mx ip4:46.43.1.242 ip6:2001:41c9:1:41e::242 ip4:209.51.188.41 ip6:2001:470:142:8::100 ?all”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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.