wakandi.no website review

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

6 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, hsappstatic.net and Google Tag Manager and others), adding 2.6 MB and 1.5 s of main-thread time.

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

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

hsappstatic.net costs a phone 412 ms of main-thread work and 718 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.

A phone's processor spends 3.7 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Cloudflare CDN costs a phone 111 ms of main-thread work and 415 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.

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.

3 KiB could be saved by minifying CSS.

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 14.6 s on a phone. Good is under 1.8 s.

Your largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Accelerating the digital transformation of the informal eco…”.

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

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

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

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

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

Your homepage downloads 8.7 MB in 96 requests on a phone: images 5.3 MB (24), scripts 2.6 MB (32) and other files 377 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Impact-picture-1-2.jpg at 1,460 px wide, shown at 350 px. Resized copies would save about 90 KiB.

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

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

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

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

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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 20 pages on wakandi.no and 23 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.

The HTML your server sends has 505 of the 1,220 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://wakandi.com/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.

https://wakandi.com/social-impact-tech, https://wakandi.com/our-commitment and https://wakandi.com/introduction-to-wakandi have no meta description, so Google writes the search snippet from whatever text it finds.

https://wakandi.com/introduction-to-wakandi 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 9 pages linked from your homepage and read each the way a search engine does.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Loading the stylesheet 'https://7052064.fs1.hubspotusercontent-na1.net/hubfs/7052064/hub_generated/module_assets/1/-271…”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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: 16 testimonial or review blocks. 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 1,220 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies, 8 of them by other companies (measured from a US location before any click).

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