wt-map.com website review

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

The page goes through 2 redirects before it starts loading, costing about 3.2 s. Link and advertise the final URL directly.

3 images could be 841 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

6 third-party services load with your homepage (Vimeo, Optanon and wpp.com and others), adding 14.2 MB and 885 ms of main-thread time.

Vimeo costs a phone 687 ms of main-thread work and 13.5 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 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

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

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

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

wpp.com costs a phone 72 ms of main-thread work and 451 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.

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

The HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The brain of a consultancy, the heart of an agency”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 15.6 MB in 232 requests on a phone: other files 11.0 MB (88), scripts 2.6 MB (60) and images 1.3 MB (61). Under 2 MB keeps phones on slow connections fast.

1 image (208 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (50 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 4.43 g of CO₂e: 531.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

Your title is only 3 characters: “MAP”. 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 canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://wt-map.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 15 pages on wt-map.com and 1 external page.

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 403 of the 724 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://wt-map.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.

/ and https://wt-map.com/about-us all use the title “MAP”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://wt-map.com/careers and https://wt-map.com/careers/All use the same meta description. A description written for each page earns more clicks.

https://wt-map.com/privacy-policy, https://wt-map.com/cookie-statement and https://wt-map.com/client-privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://wt-map.com/contact 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 8 pages linked from your homepage and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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: 21 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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