tw-group.com website review

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, Google Maps and cdn-cookieyes.com and others), adding 1.2 MB and 956 ms of main-thread time.

10 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

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

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

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

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

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

Desktop scores 74 but mobile only 49. 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.

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

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

Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Usamos cookies para mejorar su experiencia de navegación, m…”.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 130 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.7 MB in 149 requests on a phone: media 1.8 MB (2), scripts 1.6 MB (62) and images 799 KiB (17). Under 2 MB keeps phones on slow connections fast.

6 images (438 KiB) are 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.

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

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

Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

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.

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

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

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

There is no robots.txt at tw-group.com/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

The homepage links to 143 pages on tw-group.com and 7 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://tw-group.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://tw-group.com/pt-pt and https://tw-group.com/sv all use the title “Cada cliente, un mundo - TW Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tw-group.com/de has no meta description, so Google writes the search snippet from whatever text it finds.

https://tw-group.com/pt-pt and https://tw-group.com/sv use the same meta description. A description written for each page earns more clicks.

https://tw-group.com/en, https://tw-group.com/fr, https://tw-group.com/pt-pt, https://tw-group.com/sv and https://tw-group.com/de have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 556 words of visible text.

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

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

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