wingd.com website review

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

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

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

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

Google Tag Manager costs a phone 283 ms of main-thread work and 425 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.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

5 third-party services load with your homepage (Google Tag Manager, Cookiebot and LinkedIn Ads and others), adding 616 KiB and 391 ms of main-thread time.

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

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

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

3 KiB could be saved by minifying JavaScript.

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 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “High power. High impact. An optimised propulsion solution, …”.

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

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

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

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

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

22 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 103 ms to 116 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.9 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.6 MB in 88 requests on a phone: images 1.6 MB (55), scripts 780 KiB (16) and fonts 96 KiB (2). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example wingd_mette_2562_v1.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 63 KiB.

1 image further down the page (100 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 12 characters: “Home | WinGD”. 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.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 131 pages on wingd.com and 9 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 https://wingd.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://wingd.com/Careers, https://wingd.com/products-solutions, https://wingd.com/products-solutions/engines, https://wingd.com/design-development/engine-technologies/x-df-dual-fuel-design, https://wingd.com/products-solutions/engines/general-technical-data and https://wingd.com/products-solutions/engines/fuel-flexibility and 9 others 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 https://wingd.com/Careers, whose canonical is https://wingd.com/about-wingd/careers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://wingd.com/Careers, https://wingd.com/products-solutions/engines/general-technical-data, https://wingd.com/products-solutions/engines/fuel-flexibility, https://wingd.com/products-solutions/engines/fuel-flexibility/lng and https://wingd.com/products-solutions/engines/fuel-flexibility/ammonia took over 3 s to send their HTML from our server.

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

21 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”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 13 fields (0 required). Every extra field lowers completion.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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

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