kosmc.ai website review

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

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

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

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

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

About 192 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.

6 third-party services load with your homepage (Facebook, Google Tag Manager and Clarity and others), adding 635 KiB and 381 ms of main-thread time.

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

Polyfills for old browsers add 13 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.

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.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “musician1”.

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

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

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

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

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

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

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

Your homepage downloads 2.8 MB in 76 requests on a phone: images 1.9 MB (45), scripts 640 KiB (15) and fonts 181 KiB (5). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example medianews4u.0558c7017bbc98fde927.webp at 650 px wide, shown at 144 px. Resized copies would save about 472 KiB.

11 images further down the page (670 KiB) 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 0.79 g of CO₂e: 94.9 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.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Some list items are not inside a list.

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

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

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

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

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

The homepage links to 41 pages on kosmc.ai and 18 external pages.

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

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

1 link go through two or more redirects, for example https://docs.google.com/forms/d/1CQZY1QeLjkOxiho1Y9nZl3JT6vPyXziaGApX65IWiBI/.

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.

kosmc.ai 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.

kosmc.ai'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.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

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 271 words of visible text.

kosmc.ai 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.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 4 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.

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