Website review, no card needed

allenamericans.com logo

allenamericans.com website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 92 checks

This review found 44 issues worth fixing on allenamericans.com, 11 of them high impact, across 92 checks. The most urgent: main-thread work: 17.9 s. 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
1.1 s848 msApr 25Oct 10947 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026955 ms
May 2, 2026945 ms
May 9, 2026953 ms
May 16, 2026959 ms
May 23, 2026946 ms
May 30, 2026971 ms
Jun 6, 2026919 ms
Jun 13, 2026872 ms
Jun 20, 2026917 ms
Jun 27, 2026878 ms
Jul 4, 2026968 ms
Jul 11, 2026950 ms
Jul 18, 20261.0 s
Jul 25, 20261.0 s
Aug 1, 2026982 ms
Aug 8, 2026979 ms
Aug 15, 2026950 ms
Aug 22, 2026946 ms
Aug 29, 2026946 ms
Sep 5, 2026957 ms
Sep 12, 2026957 ms
Sep 19, 2026931 ms
Sep 26, 2026931 ms
Oct 3, 2026923 ms
Oct 10, 2026947 ms
Real-visitor tap response (INP)75th percentile, phones
126 ms73 msApr 25Oct 10120 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026103 ms
May 2, 2026101 ms
May 9, 2026101 ms
May 16, 2026100 ms
May 23, 202696 ms
May 30, 202695 ms
Jun 6, 202690 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202680 ms
Jul 4, 202687 ms
Jul 11, 202694 ms
Jul 18, 202695 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202695 ms
Aug 15, 2026102 ms
Aug 22, 2026103 ms
Aug 29, 2026104 ms
Sep 5, 2026107 ms
Sep 12, 2026109 ms
Sep 19, 2026110 ms
Sep 26, 2026111 ms
Oct 3, 2026115 ms
Oct 10, 2026120 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 allenamericans.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allenamericans.com at 1.9 s1.9 s
  2. allenamericans.com at 3.9 s3.9 s
  3. allenamericans.com at 5.8 s5.8 s
  4. allenamericans.com at 7.8 s7.8 s
  5. allenamericans.com at 9.7 s9.7 s
  6. allenamericans.com at 11.6 s11.6 s
  7. allenamericans.com at 13.6 s13.6 s
  8. allenamericans.com at 15.5 s15.5 s

Speed

14 to fix50
  • Main-thread work: 17.9 s

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

  • Google/Doubleclick Ads adds 1.6 s

    1.6 s

    Google/Doubleclick Ads costs a phone 1.6 s of main-thread work and 1.2 MB 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.

  • 3,491 HTML elements

    The page has 3,491 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/Doubleclick Ads, Pubmatic and Rubicon Project and others), adding 3.3 MB and 5.2 s of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 2.2 MB

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

  • Reduce unused JavaScript

    150 ms · 1.5 MB

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

  • Improve image delivery

    750 ms · 732 KiB

    23 images could be 732 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 50

    50/100

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

  • Pubmatic adds 942 ms

    942 ms

    Pubmatic costs a phone 942 ms of main-thread work and 261 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.

  • Rubicon Project adds 721 ms

    721 ms

    Rubicon Project costs a phone 721 ms of main-thread work and 103 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.

  • Google Tag Manager adds 642 ms

    642 ms

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

  • Infolinks adds 588 ms

    588 ms

    Infolinks costs a phone 588 ms of main-thread work and 174 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 410 ms. During a long task the page ignores taps.

  • Render-blocking requests

    350 ms

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

  • Minify JavaScript

    71 KiB

    71 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    59 KiB

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

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

    14 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 59.6 s

    59.6 s

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

  • Total Blocking Time: 3.1 s

    3.1 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • 48 images without width and height

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2026-27 Regular Season Schedule”.

  • First Contentful Paint: 2.3 s

    2.3 s

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

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

    +15%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

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: 1.1 s

    1.1 s

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

  • Real-user INP: 114 ms

    114 ms

    Real visitors wait 114 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 497 ms

    497 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

4 to fix33
  • Page weight: 6.6 MB in 1,223 requests

    6.6 MB

    Your homepage downloads 6.6 MB in 1,223 requests on a phone: scripts 3.9 MB (127), images 1.9 MB (449) and other files 404 KiB (488). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    619 KiB

    6 images are downloaded at several times the size a phone draws them, for example 106_78.png at 500 px wide, shown at 32 px. Resized copies would save about 619 KiB.

  • 15 images below the first screen load straight away

    15 images further down the page (956 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 10 images in older formats

    10 images (783 KiB) 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.

  • About 1.9 g of CO₂ per visit

    1.88 g

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

Accessibility

6 to fix83
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • 3 form fields without a label

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

  • <dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

    <dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. (1 element).

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • Every image has alt text

    All 138 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8584
  • 2 H1 headlines

    There are 2 <h1> headlines (“Search” and “2026-27 Regular Season”). One clear main headline is easier for people and search engines.

  • Meta description is long (169 characters)

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

  • No robots.txt

    There is no robots.txt at allenamericans.com/robots.txt, the first file search crawlers ask for.

  • 4 links with vague text

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

  • 110 internal links, 98 external

    The homepage links to 110 pages on allenamericans.com and 98 external pages.

5 checks passed
  • Title: 58 characters

    Your title is a healthy 58 characters: “Allen Americans | Allen, TX Professional Hockey | Schedule”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: SportsTeam.

  • Open Graph tags complete

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

  • XML sitemap found

    Your XML sitemap is reachable at https://allenamericans.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.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://allenamericans.com/tickets/groups, https://allenamericans.com/tickets/season-tickets, https://allenamericans.com/tickets/premium-seating, https://allenamericans.com/news, https://allenamericans.com/team/roster and https://allenamericans.com/team/statistics and 9 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 59 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 3188
  • 29 third-party cookies

    29 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

  • 6 JavaScript errors while loading

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

  • Browser-reported issues

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    62 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

  • 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 1,403 words of copy

    The homepage carries about 1,403 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule” and “Promo Schedule”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Promo Schedule”, “Printable PDF Schedule” and “Shop”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

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

  • 22 cookies set on arrival

    22

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

  • 67 other companies contacted

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

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 allenamericans.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
Analytics
Google Tag Manager

Company

Founded
2009
Headquarters
Allen

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on allenamericans.com, including 20 speed issues, 4 SEO issues and 4 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