Website review, no card needed

annarbortees.com logo

annarbortees.com website review

Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 79 checks

This review found 33 issues worth fixing on annarbortees.com, 6 of them high impact, across 79 checks. The most urgent: aRIA attributes must conform to valid values (2 elements). 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

Full-page screenshot of annarbortees.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. annarbortees.com at 0.5 s0.5 s
  2. annarbortees.com at 1.1 s1.1 s
  3. annarbortees.com at 1.6 s1.6 s
  4. annarbortees.com at 2.2 s2.2 s
  5. annarbortees.com at 2.7 s2.7 s
  6. annarbortees.com at 3.3 s3.3 s
  7. annarbortees.com at 3.8 s3.8 s
  8. annarbortees.com at 4.3 s4.3 s

Speed

8 to fix81
  • 3,480 HTML elements

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

  • Mobile performance score: 81

    81/100

    Your mobile performance score is 81 (desktop: 82). Pages that score under 90 lose visitors before the first paint.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Freshchat, fw-cdn.com and cloudflare.com and others), adding 1.1 MB and 647 ms of main-thread time.

  • Freshchat adds 487 ms

    487 ms

    Freshchat costs a phone 487 ms of main-thread work and 851 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.

  • Improve image delivery

    467 KiB

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

  • Main-thread work: 3.8 s

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

  • 8 long tasks on the main thread

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

  • Reduce unused JavaScript

    319 KiB

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

  • Reduce unused CSS

    150 ms · 81 KiB

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

  • Use efficient cache lifetimes

    223 KiB

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

  • Font display

    50 ms

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

  • 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: 13 ms

    13 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 19.3 s

    19.3 s

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

  • Total Blocking Time: 388 ms

    388 ms

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Speed Index: 3.9 s

    3.9 s

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

7 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: 148 ms

    148 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 480 ms

    480 ms

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

2 to fix81
  • Page weight: 3.8 MB in 289 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 289 requests on a phone: scripts 1.3 MB (144), other files 1.3 MB (91) and images 859 KiB (36). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Aerial_Maple_Edit.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).

  • About 1.1 g of CO₂ per visit

    1.08 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.8 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

6 to fixGoogle 8592
  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 9 text elements with low contrast

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

  • Hidden but focusable

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

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

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

  • 5 links without text

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

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

    Alternative text of images should not be repeated as text: 12 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 21 images in the HTML carry an alt attribute.

  • 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. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8581
  • No meta description

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

  • No structured data

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

  • No social preview image

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

  • 10 links with vague text

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

  • 509 internal links, 9 external

    The homepage links to 509 pages on annarbortees.com and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “The Ann Arbor T-shirt Company / Celebrate Your Identity”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “The Ann Arbor T-shirt Company / Celebrate Your Identity”.

  • Canonical URL set

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

AI search readiness

1 to fix88
  • 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.

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,047 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without a meta description

    https://www.annarbortees.com/pages/brands, https://www.annarbortees.com/collections/47-brand, https://www.annarbortees.com/collections/a4, https://www.annarbortees.com/collections/adams-headwear, https://www.annarbortees.com/collections/adidas and https://www.annarbortees.com/collections/alleson-athletic and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 19 small tap targets

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

  • 1 third-party cookie

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 538 words of copy

    The homepage carries about 538 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “REQUEST A QUOTE” and “START DESIGNING”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop AATees Retail”, “Contact Us” and “Request a Quote”.

  • 4 short forms

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

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 11 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on annarbortees.com, including 13 speed issues, 4 SEO issues and 3 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