Website review, no card needed
smumustangs.com website review
Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 88 checks
This review found 41 issues worth fixing on smumustangs.com, 16 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 98 ms |
| May 9, 2026 | 98 ms |
| May 16, 2026 | 98 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 99 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 100 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 140 ms |
| Oct 17, 2026 | 141 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
How it loaded on a phone
2.7 s
5.3 s
8.0 s
10.6 s
13.3 s
16.0 s
18.6 s
21.3 s
Speed
Use efficient cache lifetimes
2.1 s · 1.5 MB154 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Reduce unused JavaScript
2.1 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
3.2 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.
Main-thread work: 12.4 s
A phone's processor spends 12.4 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Infolinks and others), adding 2.3 MB and 2.7 s of main-thread time.
Google/Doubleclick Ads adds 556 ms
556 msGoogle/Doubleclick Ads costs a phone 556 ms of main-thread work and 590 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
590 KiB24 images could be 590 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 500 ms
500 msGoogle Tag Manager costs a phone 500 ms of main-thread work and 786 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.
transcend-cdn.com adds 374 ms
374 mstranscend-cdn.com costs a phone 374 ms of main-thread work and 319 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 383 ms
383 msInfolinks costs a phone 383 ms of main-thread work and 155 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 295 ms. During a long task the page ignores taps.
Rubicon Project adds 282 ms
282 msRubicon Project costs a phone 282 ms of main-thread work and 112 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.
1,878 HTML elements
The page has 1,878 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 64 KiBPolyfills for old browsers add 64 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
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: 141 ms
141 msYour server sent the HTML in 141 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
First Contentful Paint: 7.7 s
7.7 sThe first text or image appears after 7.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Luis Flores”.
Speed Index: 23.7 s
23.7 sVisually, the page fills in at 23.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 54.2 s
54.2 sThe page becomes fully interactive after 54.2 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.15
0.15For real visitors the layout shifts by 0.15 (75th percentile). Good is under 0.1.
Tap response (INP) got 43% slower for real visitors
+43%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 98 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 186 ms
186 msReal visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 673 ms
673 msReal visitors wait 673 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.1
0.1The layout barely moves while loading (CLS 0.1, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 1,153 requests
5.4 MBYour homepage downloads 5.4 MB in 1,153 requests on a phone: scripts 3.3 MB (161), images 976 KiB (346) and other files 499 KiB (491). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (85 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.5 g of CO₂ per visit
1.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.52 g of CO₂e: 182.6 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
Orphan list items
Some list items are not inside a list.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (51 characters)
Your meta description is only 51 characters: “The official athletics website for the SMU Mustangs”. 70 to 160 characters is enough to sell the click.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
157 internal links, 38 external
The homepage links to 157 pages on smumustangs.com and 38 external pages.
5 checks passed
Title: 42 characters
Your title is a healthy 42 characters: “SMU Athletics - Official Athletics Website”.
Canonical URL set
The canonical URL is https://smumustangs.com/.
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://admin.smumustangs.com/sitemap.xml.
AI search readiness
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://smumustangs.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.
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, 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 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,107 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://smumustangs.com/boxscore.aspx, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages without a meta description
https://smumustangs.com/api/v2/promotions/17/click and https://smumustangs.com/api/v2/promotions/18/click have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://smumustangs.com/sidearmstats/msoc/summary, https://smumustangs.com/news/2026/10/18/volleyball-livings-11-kills-leads-no-5-smu-in-sweep-of-florida-state, https://smumustangs.com/api/v2/promotions/17/click, https://smumustangs.com/api/v2/promotions/18/click, https://smumustangs.com/sports/mens-basketball and https://smumustangs.com/sports/womens-basketball and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://smumustangs.com/sidearmstats/msoc/summary, https://smumustangs.com/api/v2/promotions/17/click and https://smumustangs.com/api/v2/promotions/18/click have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 138 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
39 third-party cookies
39 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 (“The Topics API is deprecated and will be removed in a future release.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
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
77 of 79 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 448 words of copy
The homepage carries about 448 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: “Men's Basketball Schedule” and “Women's Basketball Schedule”.
26 calls to action
The homepage has 26 calls to action, for example “Buy Tickets, Opens in new window”, “Schedule” and “Ticket Policies & Will Call”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 1 more (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
47 other companies contacted
Loading the homepage contacts 47 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 smumustangs.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
- Nuxt
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on smumustangs.com, including 23 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.