Website review, no card needed

mavs.com logo

mavs.com website review

Visit site (opens in a new tab)Reviewed 1 November 202646 issues · 81 checks

This review found 46 issues worth fixing on mavs.com, 19 of them high impact, across 81 checks. The most urgent: page weight: 12.3 MB in 276 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
3.6 s2.5 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.8 s
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.3 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.4 s
Oct 10, 20263.2 s
Oct 17, 20263.1 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
161 ms132 msMay 9Oct 24158 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026158 ms
May 16, 2026158 ms
May 23, 2026155 ms
May 30, 2026154 ms
Jun 6, 2026153 ms
Jun 13, 2026154 ms
Jun 20, 2026154 ms
Jun 27, 2026147 ms
Jul 4, 2026144 ms
Jul 11, 2026137 ms
Jul 18, 2026135 ms
Jul 25, 2026138 ms
Aug 1, 2026138 ms
Aug 8, 2026144 ms
Aug 15, 2026147 ms
Aug 22, 2026151 ms
Aug 29, 2026152 ms
Sep 5, 2026153 ms
Sep 12, 2026155 ms
Sep 19, 2026154 ms
Sep 26, 2026156 ms
Oct 3, 2026156 ms
Oct 10, 2026157 ms
Oct 17, 2026157 ms
Oct 24, 2026158 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 mavs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mavs.com at 1.5 s1.5 s
  2. mavs.com at 3.0 s3.0 s
  3. mavs.com at 4.5 s4.5 s
  4. mavs.com at 6.1 s6.1 s
  5. mavs.com at 7.6 s7.6 s
  6. mavs.com at 9.1 s9.1 s
  7. mavs.com at 10.6 s10.6 s
  8. mavs.com at 12.1 s12.1 s

Speed

5 to fix
  • Main-thread work: 10.7 s

    A phone's processor spends 10.7 s on main-thread work while loading, 6.4 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 (Google Tag Manager, Google/Doubleclick Ads and Facebook and others), adding 2.2 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 977 ms

    977 ms

    Google Tag Manager costs a phone 977 ms of main-thread work and 1.1 MB 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/Doubleclick Ads adds 229 ms

    229 ms

    Google/Doubleclick Ads costs a phone 229 ms of main-thread work and 544 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.

  • 2,794 HTML elements

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

  • Font display

    50 ms

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

  • 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

10 to fix0
  • 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.

  • Real-user LCP: 4.2 s

    4.2 s

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

  • Real-user CLS: 0.37

    0.37

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

  • Speed Index: 17.8 s

    17.8 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user INP: 251 ms

    251 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 921 ms

    921 ms

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

  • Cumulative Layout Shift: 0.222

    0.222

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

Images and page weight

4 to fix25
  • Page weight: 12.3 MB in 276 requests

    12.3 MB

    Your homepage downloads 12.3 MB in 276 requests on a phone: images 8.1 MB (81), scripts 3.3 MB (59) and fonts 478 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    26-27_NellieNight_TVDrop.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    853 KiB

    1 image is downloaded at several times the size a phone draws it, for example 26-27_NellieNight_TVDrop.jpg at 1,754 px wide, shown at 296 px. Resized copies would save about 853 KiB.

  • 4 images in older formats

    4 images (2.0 MB) 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 3.5 g of CO₂ per visit

    3.48 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

14 to fixGoogle 8583
  • Images must have alternative text (153 elements)

    Images must have alternative text: 153 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 5 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Main landmark should not be contained in another landmark (2 elements)

    Main landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

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

  • Elements marked as presentational should be consistently ignored (3 elements)

    Elements marked as presentational should be consistently ignored: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 41 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: 41 passed and 14 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9285
  • No H1 headline

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 4 internal links

    The homepage links to only 4 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

6 checks passed
  • Meta description: 116 characters

    Your meta description is 116 characters: “The official home of the Dallas Mavericks. Get the latest news, scores, schedule, highlights, tickets and Mavs gear.”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “The Official Home of the Dallas Mavericks”.

  • Canonical URL set

    The canonical URL is https://www.nba.com/mavs.

  • Structured data in place

    Structured data found: BreadcrumbList, SportsTeam and WebSite.

  • 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.nba.com/sitemap_index.xml.

AI search readiness

3 to fix28
  • robots.txt blocks 2 AI answer engine crawlers

    2 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Most text only appears after JavaScript runs

    1%

    A phone browser shows 1,420 words, but the HTML your server sends has only 21. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://www.nba.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 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

Other pages

2 to fix90
  • 3 pages without a meta description

    https://www.nba.com/mavs/news, https://www.nba.com/mavs/highlights and https://www.nba.com/mavs/community have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.nba.com/mavs/news and https://www.nba.com/mavs/highlights have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 10 broken images

    10 images failed to load on a phone, for example https://cdn.nba.com/next/fallback.jpg.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 1,420 words of copy

    The homepage carries about 1,420 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: “SCHEDULE” and “SHOP”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop All”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 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.

  • 18 cookies set on arrival

    18

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

  • 53 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Next.js
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
1980
Headquarters
Dallas

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on mavs.com, including 15 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