tomsguide.com website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  +4%

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

• Largest content (LCP) held steady for real visitors

  +7%

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

• Page weight: 9.3 MB

  9.3 MB

  Your homepage downloads 9.3 MB on a phone, 4.2 MB of it images (46%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  WU6pa7hKuxs5ScCoqcXYWA.jpg weighs 3.2 MB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 3 images in older formats

  3 images (3.4 MB) 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.

  Elements (3)

• About 2.6 g of CO₂ per visit

  2.62 g

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

• 2 buttons without a name

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

  Elements (2)

• Images must have alternative text (1 element)

  Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 20 text elements with low contrast

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

  Elements (3)

• ARIA dialog and alertdialog nodes should have an accessible name (1 element)

  ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Scrollable region must have keyboard access (1 element)

  Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• All page content should be contained by landmarks (7 elements)

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

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  Elements (3)

• Banner landmark should not be contained in another landmark (1 element)

  Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Alternative text of images should not be repeated as text (26 elements)

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

  Elements (3)

• 8 form fields without a label

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

  View source

• ARIA role should be appropriate for the element (1 element)

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

  Elements (1)

• Meta description is long (184 characters)

  Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No social preview image

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

  View source

• No X (Twitter) card tag

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

• 309 internal links, 11 external

  The homepage links to 309 pages on tomsguide.com and 11 external pages.

• Most text only appears after JavaScript runs

  25%

  A phone browser shows 3,207 words, but the HTML your server sends has only 813. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

  View source

• No llms.txt

  There is no /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.

• Opted out of AI training for 1 crawler

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

• 2 linked pages hidden from search

  /membership and /newsletter are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  Elements (2)

• 3 pages share a title

  /, /au and /uk all use the title “Tom's Guide | Tech Product Reviews, Top Picks and How To”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (3)

• 2 pages share a meta description

  /au and /uk use the same meta description. A description written for each page earns more clicks.

• 15 pages without an H1

  /phones/reviews, /computing/reviews, /membership, /au, /uk and /newsletter and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 4 broken images

  4 images failed to load on a phone, for example https://ib.adnxs.com/getuid?https%3A%2F%2Fpixel.servebom.com%2Fpartner%3Fcb%3D4897%26svc%3Dus%26id%3D23%26uid%3D%24UID.

• 5 JavaScript errors while loading

  5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

• Thin social proof

  Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

• About 3,207 words of copy

  The homepage carries about 3,207 words of visible text.

• 9 trackers load before any consent

  9

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

• 37 cookies set on arrival

  37

  Opening the homepage sets 37 cookies (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.

• 89 other companies contacted

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