torexgold.com website review

About 309 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

About 160 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

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

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

5 third-party services load with your homepage (proactivedigital.solutions, vrify.com and FontAwesome CDN and others), adding 334 KiB and 29 ms of main-thread time.

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

Desktop scores 83 but mobile only 47. 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.

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.

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

Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Consistently Delivering Solid Operational Performance Torex…”. Most of its time is resource load delay (3.0 s).

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

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

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

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

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

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

4 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 101 ms to 92 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 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 images (98 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.

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

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: 2 elements on the page fail this check, rated serious by axe-core.

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

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 6 <h1> headlines (“Consistently Delivering Solid Operational Perform…”, “Torex Releases Los Reyes Preliminary Economic Ass…” and “GOLD: The Journey Continues”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 143 pages on torexgold.com and 14 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://torexgold.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://torexgold.com/about-us and https://torexgold.com/about-us/our-company all use the title “Torex Gold Resources Inc. | Our Company”, 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://torexgold.com/about-us, https://torexgold.com/about-us/our-company, https://torexgold.com/about-us/executive-team, https://torexgold.com/about-us/board-of-directors, https://torexgold.com/about-us/corporate-governance and https://torexgold.com/about-us/photo-gallery and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://torexgold.com/about-us, whose canonical is https://torexgold.com/about-us/our-company. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://torexgold.com/responsible-mining-esg has no <h1> headline, so visitors and search engines get no clear main topic.

https://torexgold.com/about-us/executive-team, https://torexgold.com/about-us/legal, https://torexgold.com/assets, https://torexgold.com/assets/morelos, https://torexgold.com/assets/los-reyes and https://torexgold.com/assets/early-stage-exploration and 2 others took over 3 s to send their HTML from our server.

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

11 of 19 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: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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