exki.com website review

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

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

About 171 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

Google CDN costs a phone 434 ms of main-thread work and 736 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.

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

3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 804 KiB and 474 ms of main-thread time.

11 KiB could be saved by minifying CSS.

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

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

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

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

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 text “Discover our new Autumn/Winter range ! New recipes, seasona…”.

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

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

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

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

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

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

Scripts block taps and scrolling for 397 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.174 while loading, so content jumps under the reader's thumb. Good is under 0.1.

2 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-24, real Chrome visitors' tap response (inp) went from 87 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.6 MB in 30 requests on a phone: scripts 1.5 MB (8), images 397 KiB (9) and other files 351 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Discover our new Autumn/Winter range !” and “”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 44 pages on exki.com and 4 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.

Your homepage links to /cookie-policy and /contactus, which answer with an error. Visitors hit a dead end and search engines drop them.

/shop/wishlist declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and /shop/wishlist all use the title “EXKi | Meals inspired by plants, take out or eat in”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/contact, /carrot-club, /delivery, /my-exki and /conditions-generales-d-utilisation-du-site have no meta description, so Google writes the search snippet from whatever text it finds.

/commitment-healthy-and-sustainable-cuisine has no <h1> headline, so visitors and search engines get no clear main topic.

/commitment-healthy-and-sustainable-cuisine has 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.

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

6 of 14 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_UNKNOWN_URL_SCHEME”.

Large scripts ship without source maps.

3 links from your homepage to your own site are broken, for example https://www.exki.com/cookie-policy (404).

1 link to other sites is dead, for example https://twitter.com/exkiofficial (404).

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

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

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://www.exki.com/shop/wishlist.

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.

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

exki.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: 1 testimonial or review block. 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.

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

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 3 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.