Website review, no card needed

travismathew.com logo

travismathew.com website review

Visit site (opens in a new tab)Reviewed 4 November 202637 issues · 88 checks

This review found 37 issues worth fixing on travismathew.com, 16 of them high impact, across 88 checks. The most urgent: page weight: 149.0 MB in 931 requests. 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
2.9 s2.3 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
220 ms144 msMay 16Oct 31211 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026196 ms
May 23, 2026167 ms
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026154 ms
Jun 20, 2026157 ms
Jun 27, 2026162 ms
Jul 4, 2026167 ms
Jul 11, 2026172 ms
Jul 18, 2026175 ms
Jul 25, 2026174 ms
Aug 1, 2026176 ms
Aug 8, 2026179 ms
Aug 15, 2026184 ms
Aug 22, 2026187 ms
Aug 29, 2026188 ms
Sep 5, 2026184 ms
Sep 12, 2026179 ms
Sep 19, 2026174 ms
Sep 26, 2026178 ms
Oct 3, 2026179 ms
Oct 10, 2026187 ms
Oct 17, 2026196 ms
Oct 24, 2026200 ms
Oct 31, 2026211 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 travismathew.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. travismathew.com at 0.9 s0.9 s
  2. travismathew.com at 1.8 s1.8 s
  3. travismathew.com at 2.7 s2.7 s
  4. travismathew.com at 3.6 s3.6 s
  5. travismathew.com at 4.5 s4.5 s
  6. travismathew.com at 5.4 s5.4 s
  7. travismathew.com at 6.3 s6.3 s
  8. travismathew.com at 7.2 s7.2 s

Speed

13 to fix34
  • Use efficient cache lifetimes

    1.3 s · 1.3 MB

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

  • Render-blocking requests

    1.9 s

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

  • Improve image delivery

    1.4 s · 370 KiB

    6 images could be 370 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Main-thread work: 12.1 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 919 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 34

    34/100

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

  • 7,291 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, sematext.com and Klaviyo and others), adding 2.8 MB and 2.6 s of main-thread time.

  • Reduce unused JavaScript

    600 ms · 1.9 MB

    About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • sematext.com adds 356 ms

    356 ms

    sematext.com costs a phone 356 ms of main-thread work and 40 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.

  • Klaviyo adds 287 ms

    287 ms

    Klaviyo costs a phone 287 ms of main-thread work and 632 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.

  • 20 long tasks on the main thread

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

  • rebuyengine.com adds 193 ms

    193 ms

    rebuyengine.com costs a phone 193 ms of main-thread work and 557 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.

  • Minify JavaScript

    120 KiB

    120 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    118 KiB

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

  • Reduce unused CSS

    34 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 11.5 s

    11.5 s

    Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 49.9 s

    49.9 s

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

  • Speed Index: 15.3 s

    15.3 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • 2 images without width and height

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.05

    0.05

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 780 ms

    780 ms

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

  • Largest content (LCP) got 12% faster for real visitors

    -12%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 149.0 MB in 931 requests

    149.0 MB

    Your homepage downloads 149.0 MB in 931 requests on a phone: media 133.9 MB (16), images 8.6 MB (432) and scripts 5.0 MB (206). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (191 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 42.2 g of CO₂ per visit

    42.23 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 9392
  • 2 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 185 form fields without a label

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

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

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

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

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

  • ARIA role should be appropriate for the element (4 elements)

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 8583
  • No H1 headline

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//travismathew.com/cdn/shop/files/tm-desktop-logo.svg?v…”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 519 internal links, 28 external

    The homepage links to 519 pages on travismathew.com and 28 external pages.

5 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Shop lifestyle essentials & performance golf apparel by TravisMathew. California-inspired Men's and Women's apparel & a…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “TravisMathew Official | Confident, Comfortable Apparel”.

  • Canonical URL set

    The canonical URL is https://travismathew.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://travismathew.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,058 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://travismathew.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages without a meta description

    https://travismathew.com/pages/stores, https://travismathew.com/collections/wolf-shepherd, https://travismathew.com/collections/social-club and https://travismathew.com/collections/mens-shirt-jackets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://travismathew.com/pages/stores, https://travismathew.com/products/e-gift-card, https://travismathew.com/collections/mens-new-arrivals, https://travismathew.com/collections/best-sellers, https://travismathew.com/collections/wolf-shepherd and https://travismathew.com/collections/cloud-collection and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://travismathew.com/collections/mens-outerwear took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 7785
  • 25 small tap targets

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

  • Deprecated browser APIs

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

  • 4 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • About 527 words of copy

    The homepage carries about 527 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “Shop Gifts For Him”.

  • 90 calls to action

    The homepage has 90 calls to action, for example “Sign Up”, “Join For Free” and “Shop All Men”.

  • 5 short forms

    5 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Criteo, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 cookies (measured from a US location before any click).

  • 59 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 travismathew.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Founded
2007
Headquarters
Huntington Beach

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on travismathew.com, including 19 speed issues, 3 SEO issues and 2 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