corekites.com website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

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

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

8 images could be 695 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

7 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 146 ms to 154 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 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.0 MB in 40 requests on a phone: media 11.7 MB (2), images 813 KiB (21) and scripts 260 KiB (8). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example czM6Ly9jb3Jla2l0ZXMtbmVvcy9uZW9zL3Jlc291cmNlcy9wZXJzaXN0ZW50 at 5,614 px wide, shown at 360 px. Resized copies would save about 545 KiB.

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

2 elements hidden from screen readers can still receive keyboard focus.

4 images have no alt text, which hurts accessibility and image search.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your meta description is only 47 characters: “CORE - Performance Kite und Wing Gear seit 2001”. 70 to 160 characters is enough to sell the click.

The homepage links to 251 pages on corekites.com and 17 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.

/de/kontakt, /de/impressum, /de/datenschutz and /de/agb have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /social, whose canonical is /de/social. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/de/kontakt and /de/carved/boards/imperator-7-limited-edition have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ridecore.com 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.

ridecore.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 449 words of visible text.

DMARC is set to p=none, so mail pretending to be corekites.com is still delivered. Add a report address, check the reports, then move to quarantine.

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.

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

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.