tgm-staging.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and posthog.com and others), adding 1.7 MB and 1.3 s of main-thread time.

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

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

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

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

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

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

moengage.com costs a phone 37 ms of main-thread work and 406 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.

Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

About 19 KiB of CSS is downloaded but never applied on this page.

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.

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

Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “M-HOME-M-11.11-EN (1).png”.

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

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

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

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

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

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 7.7 MB in 285 requests on a phone: images 4.8 MB (126), scripts 2.5 MB (87) and HTML 158 KiB (4). Under 2 MB keeps phones on slow connections fast.

M-HOME-M-11.11-EN_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example M-HOME-K-971_f9137538-45c5-48b2-8a26-86c74df04dd6.png at 1,462 px wide, shown at 390 px. Resized copies would save about 186 KiB.

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

46 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

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

Google's crawler is blocked from indexing this page.

Your title is only 11 characters: “TGM Staging”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

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

The homepage links to 139 pages on tgm-staging.com and 13 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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://tgm-staging.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://tgm-staging.com/pages/find-a-store, https://tgm-staging.com/collections/best-sellers-women, https://tgm-staging.com/pages/about, https://tgm-staging.com/products/s184v12-men-shell-pocket-shacket, https://tgm-staging.com/products/s1528v12-men-shell-zip-vest and https://tgm-staging.com/products/s1323v11-men-recycled-zip-up-branded-jacket and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://tgm-staging.com/pages/find-a-store, https://tgm-staging.com/pages/about and https://tgm-staging.com/pages/sustainability all use the title “Default regular page | The Giving Movement”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://tgm-staging.com/pages/find-a-store, https://tgm-staging.com/collections/best-sellers-women, https://tgm-staging.com/pages/about, https://tgm-staging.com/pages/new-our-story, https://tgm-staging.com/pages/press-1 and https://tgm-staging.com/pages/sustainability use the same meta description. A description written for each page earns more clicks.

https://tgm-staging.com/pages/find-a-store, https://tgm-staging.com/pages/about, https://tgm-staging.com/pages/new-our-story, https://tgm-staging.com/pages/our-impact, https://tgm-staging.com/pages/press-1 and https://tgm-staging.com/pages/sustainability have no <h1> headline, so visitors and search engines get no clear main topic.

https://tgm-staging.com/products/s184v12-men-shell-pocket-shacket and https://tgm-staging.com/products/s1323v11-men-recycled-zip-up-branded-jacket took over 3 s to send their HTML from our server.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

Social proof on the homepage: 3 trust badges. 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 624 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 2 mores (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 27 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.