evona.com website review

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

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

Your mobile performance score is 82 (desktop: 95). Pages that score under 90 lose visitors before the first paint.

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

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

1 image could be 26 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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 first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

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

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

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

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

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

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

evona-logo.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example evona-logo.webp at 2,851 px wide, shown at 343 px. Resized copies would save about 137 KiB.

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

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

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

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

The homepage links to 16 pages on evona.com and 7 external pages.

/spacejobs and /job-board all use the title “Job board - EVONA”. Search engines can't tell which page to show for a search, so each competes with the others.

/spacejobs and /job-board use the same meta description. A description written for each page earns more clicks.

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

We fetched 7 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://evona.com/.

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

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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

DMARC is set to p=none, so mail pretending to be evona.com is still delivered. Reports are on, so moving to quarantine is the next step.

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.