torre.co website review

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

About 1.0 MB of CSS is downloaded but never applied on this page.

Your mobile performance score is 73 (desktop: 66). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 820 KiB and 543 ms of main-thread time.

1 image could be 42 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

About 452 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Real visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

3 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-24, real Chrome visitors' tap response (inp) went from 248 ms to 279 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.2 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.9 MB in 129 requests on a phone: scripts 2.2 MB (88), fonts 547 KiB (2) and HTML 84 KiB (2). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (44 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.81 g of CO₂e: 97.5 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”.

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

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

2 links inside paragraphs rely on colour alone to stand out.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Elements with visible text labels do not have matching accessible names. (13 elements).

Your meta description is only 22 characters: “The global job network”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 64 pages on torre.co and 5 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 312 of the 759 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://torre.ai/create-job, https://torre.ai/recruit, https://torre.ai/postings/applications, https://torre.ai/developer/api-keys and https://torre.ai/balance-auto-reload are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://torre.ai/create-job and https://torre.ai/recruit all use the title “Post a job”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://torre.ai/create-job, https://torre.ai/recruit, https://torre.ai/developer/api-keys, https://torre.ai/balance-auto-reload and https://torre.ai/en/terms have no meta description, so Google writes the search snippet from whatever text it finds.

https://torre.ai/benefits, https://torre.ai/postings/applications, https://torre.ai/culturalfit, https://torre.ai/developer/api-keys, https://torre.ai/balance-auto-reload and https://torre.ai/app/messenger/conversations/16180 have no <h1> headline, so visitors and search engines get no clear main topic.

https://torre.ai/culturalfit and https://torre.ai/app/messenger/conversations/16180 have 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.

https://torre.ai/developer/api-keys and https://torre.ai/balance-auto-reload took over 3 s to send their HTML from our server.

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

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

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.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 15 cookies, 1 of them by other companies (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.