antwalk.com website review

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

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

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

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

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

53 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and LinkedIn Ads and others), adding 431 KiB and 259 ms of main-thread time.

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

Desktop scores 68 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

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

Scripts block taps and scrolling for 555 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 6.4 MB in 196 requests on a phone: images 5.1 MB (66), scripts 650 KiB (44) and HTML 262 KiB (1). Under 2 MB keeps phones on slow connections fast.

1 image (67 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.

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

950 images have no alt text, which hurts accessibility and image search.

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

Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 71 characters, so Google will cut it off around 60: “Leading Business Capability Development Platform for Corporate Training”.

Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 54 pages on antwalk.com and 1,151 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 /ebooks/leadership-has-no-gender, which answers with an error. Visitors hit a dead end and search engines drop it.

/ and /solutions/sales-academy all use the title “Leading Business Capability Development Platform for Corporate Traini…”. Search engines can't tell which page to show for a search, so each competes with the others.

/contact-us and /solutions/sales-academy have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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 1,876 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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