Website review, no card needed

tigerteamstore.com logo

tigerteamstore.com website review

Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 86 checks

This review found 35 issues worth fixing on tigerteamstore.com, 12 of them high impact, across 86 checks. The most urgent: improve image delivery. 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
3.1 s1.4 sSep 5Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Oct 31, 20262.2 s
Nov 7, 20262.0 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
129 ms78 msSep 12Nov 14123 ms
Show as table
DateReal-visitor tap response (INP)
Sep 12, 202684 ms
Sep 19, 202687 ms
Sep 26, 202692 ms
Oct 3, 2026113 ms
Oct 10, 2026109 ms
Oct 17, 2026121 ms
Oct 24, 2026114 ms
Oct 31, 2026102 ms
Nov 14, 2026123 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 tigerteamstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tigerteamstore.com at 1.0 s1.0 s
  2. tigerteamstore.com at 2.1 s2.1 s
  3. tigerteamstore.com at 3.1 s3.1 s
  4. tigerteamstore.com at 4.2 s4.2 s
  5. tigerteamstore.com at 5.2 s5.2 s
  6. tigerteamstore.com at 6.3 s6.3 s
  7. tigerteamstore.com at 7.3 s7.3 s
  8. tigerteamstore.com at 8.3 s8.3 s

Speed

12 to fix50
  • Improve image delivery

    1.1 s · 1.2 MB

    15 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Render-blocking requests

    1.3 s

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

  • Signyfyd adds 1.0 s

    1.0 s

    Signyfyd costs a phone 1.0 s of main-thread work and 281 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.

  • Main-thread work: 6.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Signyfyd, ContentSquare and pub.network and others), adding 1.9 MB and 1.7 s of main-thread time.

  • Mobile performance score: 50

    50/100

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

  • Reduce unused JavaScript

    862 KiB

    About 862 KiB of JavaScript is downloaded but never used on this page.

  • 14 long tasks on the main thread

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

  • Use efficient cache lifetimes

    576 KiB

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

  • Reduce unused CSS

    450 ms · 104 KiB

    About 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • 2,774 HTML elements

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

  • pub.network adds 126 ms

    126 ms

    pub.network costs a phone 126 ms of main-thread work and 369 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.

  • Legacy JavaScript

    37 KiB

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

  • Minify CSS

    21 KiB

    21 KiB could be saved by minifying CSS.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

8 to fix100
  • Time to Interactive: 27.4 s

    27.4 s

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

  • Speed Index: 12.7 s

    12.7 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

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

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

    +32%

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

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

    +41%

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

  • Total Blocking Time: 485 ms

    485 ms

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

  • Cumulative Layout Shift: 0.125

    0.125

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

  • 3 images without width and height

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

5 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: 1.9 s

    1.9 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix53
  • Page weight: 5.7 MB in 517 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 517 requests on a phone: scripts 2.2 MB (168), images 1.6 MB (29) and other files 1.5 MB (283). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    8055-ATH-2026-Fall-Sideline-Shopify-Hero_m-780x1000.jpg 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).

  • 4 images far larger than shown

    442 KiB

    4 images are downloaded at several times the size a phone draws them, for example 8055_blue_homepage_make-it-yours-card-1.webp at 1,800 px wide, shown at 356 px. Resized copies would save about 442 KiB.

  • 1 image in older formats

    1 image (35 KiB) is 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.

  • About 1.6 g of CO₂ per visit

    1.63 g

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

Accessibility

4 to fixGoogle 9295
  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (2 elements).

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 74 images in the HTML carry an alt attribute.

  • 52 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: 52 passed and 3 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 9281
  • No H1 headline

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

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Official University of Missouri Athletics Store | MU Apparel & Merch”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 311 internal links, 9 external

    The homepage links to 311 pages on tigerteamstore.com and 9 external pages.

6 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Let's Go Tigers! Shop Official University of Missouri Apparel, Merchandise and Gifts at the MU Tiger Team Shop. Flat-Ra…”.

  • Canonical URL set

    The canonical URL is https://tigerteamstore.com/.

  • Structured data in place

    Structured data found: LocalBusiness, Organization, Store and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://tigerteamstore.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    8 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 11 small tap targets

    11 of 32 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 2 deprecated browser APIs that will stop working in future browsers (“The Topics API is deprecated and will be removed in a future release.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to execute script from 'https://ecommwidget.trurating.com/js?ver=4.1.2&locale=en-US' because its MIME type ('')…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No social proof

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 441 words of copy

    The homepage carries about 441 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now” and “Start your story right”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop All”, “Shop All Gifts & Accessories” and “Shop Now”.

  • 7 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 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.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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 Amazon Ads, Google Ads, Google Tag Manager, Meta Pixel and Segment 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.

  • 16 cookies set on arrival

    16

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

  • 45 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
Columbia

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on tigerteamstore.com, including 20 speed issues, 3 SEO issues and 1 conversion gap. 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