Website review, no card needed

torrecid.com logo

torrecid.com website review

Visit site (opens in a new tab)Reviewed 30 October 202632 issues · 74 checks

This review found 32 issues worth fixing on torrecid.com, 17 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.4 s3.7 sMay 9Oct 245.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.4 s
May 23, 20264.5 s
May 30, 20264.7 s
Jun 6, 20264.8 s
Jun 13, 20264.6 s
Jun 20, 20264.6 s
Jun 27, 20264.9 s
Jul 4, 20265.2 s
Jul 11, 20265.3 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.1 s
Aug 8, 20265.3 s
Aug 15, 20265.2 s
Aug 22, 20264.9 s
Aug 29, 20264.9 s
Sep 5, 20264.9 s
Sep 12, 20264.9 s
Sep 19, 20265.3 s
Sep 26, 20265.9 s
Oct 3, 20265.9 s
Oct 10, 20266.1 s
Oct 17, 20266.0 s
Oct 24, 20265.6 s
Real-visitor tap response (INP)75th percentile, phones
137 ms102 msMay 9Oct 24116 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026133 ms
May 16, 2026127 ms
May 23, 2026121 ms
May 30, 2026112 ms
Jun 6, 2026112 ms
Jun 13, 2026111 ms
Jun 20, 2026111 ms
Jun 27, 2026112 ms
Jul 4, 2026109 ms
Jul 11, 2026106 ms
Jul 18, 2026109 ms
Jul 25, 2026111 ms
Aug 1, 2026113 ms
Aug 8, 2026116 ms
Aug 15, 2026117 ms
Aug 22, 2026113 ms
Aug 29, 2026114 ms
Sep 5, 2026119 ms
Sep 12, 2026118 ms
Sep 19, 2026124 ms
Sep 26, 2026133 ms
Oct 3, 2026121 ms
Oct 10, 2026125 ms
Oct 17, 2026124 ms
Oct 24, 2026116 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of torrecid.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. torrecid.com at 1.2 s1.2 s
  2. torrecid.com at 2.5 s2.5 s
  3. torrecid.com at 3.7 s3.7 s
  4. torrecid.com at 5.0 s5.0 s
  5. torrecid.com at 6.2 s6.2 s
  6. torrecid.com at 7.5 s7.5 s
  7. torrecid.com at 8.7 s8.7 s
  8. torrecid.com at 10.0 s10.0 s

Speed

7 to fix55
  • Use efficient cache lifetimes

    14.6 s · 26.6 MB

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

  • Render-blocking requests

    8.9 s

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

  • Reduce unused CSS

    6.0 s · 1.3 MB

    About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.0 s faster on a phone.

  • Reduce unused JavaScript

    3.6 s · 731 KiB

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

  • Font display

    1.1 s

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

  • Mobile performance score: 55

    55/100

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

  • Improve image delivery

    842 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, YouTube and Google Fonts and others), adding 260 KiB and 92 ms of main-thread time.

  • Document request latency

    94 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    33 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 572 ms of it running JavaScript. That is comfortably low.

  • Server response: 574 ms

    574 ms

    Your server sent the HTML in 574 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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-user LCP: 8.0 s

    8.0 s

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

  • Real-user FCP: 5.7 s

    5.7 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • First Contentful Paint: 9.8 s

    9.8 s

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

  • Largest Contentful Paint: 20.7 s

    20.7 s

    Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are a globalized multinational family business with subs…”. Most of its time is element render delay (13.8 s).

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 20.8 s

    20.8 s

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

  • Largest content (LCP) got 37% slower for real visitors

    +37%

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

  • Tap response (INP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user INP: 146 ms

    146 ms

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

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.055

    0.055

    The layout barely moves while loading (CLS 0.055, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 41.0 MB in 92 requests

    41.0 MB

    Your homepage downloads 41.0 MB in 92 requests on a phone: media 33.4 MB (6), images 4.4 MB (7) and scripts 1.5 MB (66). Under 2 MB keeps phones on slow connections fast.

  • About 11.6 g of CO₂ per visit

    11.63 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

Google 98100
  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 8 H1 headlines

    There are 8 <h1> headlines (“A Family Company”, “1963” and “A Globalized Multinational”). One clear main headline is easier for people and search engines.

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 29 internal links, 9 external

    The homepage links to 29 pages on torrecid.com and 9 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “A Family Company Our story started in 1963 OUR HISTORY A Globalized Multinational Subsidiaries in countries Customers i…”.

  • Title: 37 characters

    Your title is a healthy 37 characters: “Torrecid – A Family and Green Company”.

  • Canonical URL set

    The canonical URL is https://www.torrecid.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.torrecid.com/wp-sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.torrecid.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.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

5 to fix76
  • 12 pages share 6 titles

    / and https://www.torrecid.com/es/inicio all use the title “Torrecid – A Family and Green Company”, and 5 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.torrecid.com/author/torrecid has no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages share a meta description

    https://www.torrecid.com/globalization and https://www.torrecid.com/index.php/globalization use the same meta description. A description written for each page earns more clicks.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.torrecid.com/index.php/globalization, whose canonical is https://www.torrecid.com/globalization. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.torrecid.com/author/torrecid has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.torrecid.com/products, https://www.torrecid.com/green-company, https://www.torrecid.com/talent, https://www.torrecid.com/news, https://www.torrecid.com/index.php/globalization and https://www.torrecid.com/index.php/innovation and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    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 calls to action

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

  • No social proof

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

  • Only about 104 words

    The homepage has only about 104 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 5 cookies set on arrival

    5

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

  • No consent tool detected

    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.

  • 5 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at torrecid.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Telefonica De Espana

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on torrecid.com, including 16 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25