raiders.com website review

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

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

About 966 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

Integral Ad Science costs a phone 1.5 s of main-thread work and 637 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.

About 157 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

Your mobile performance score is 17. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Integral Ad Science, Google/Doubleclick Ads and Optanon and others), adding 2.8 MB and 3.4 s of main-thread time.

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

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

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Optanon costs a phone 224 ms of main-thread work and 303 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.

nfltags.com costs a phone 145 ms of main-thread work and 371 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.

42 KiB JavaScript is shipped twice across bundles.

7 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking any of the buttons in this banner, or by clicki…”.

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

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

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, 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).

Your homepage downloads 7.9 MB in 325 requests on a phone: images 4.0 MB (103), scripts 2.5 MB (104) and fonts 733 KiB (25). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.

2 images (3.5 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.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (70 elements).

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

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

There are 3 <h1> headlines (“Las Vegas Raiders Home | Official Team Website | …”, “Las Vegas Raiders YouTube” and “Raider Nation Radio”). One clear main headline is easier for people and search engines.

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

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 120 pages on raiders.com and 87 external pages.

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.

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

https://www.raiders.com/game-day/2026/reg-week8/raiders-at-jets, https://www.raiders.com/community/raiders-foundation and https://www.raiders.com/alumni-relations all use the title “Las Vegas Raiders | Official Team Website | Raiders.com”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.raiders.com/game-day/2026/reg-week8/raiders-at-jets, https://www.raiders.com/promotions, https://www.raiders.com/community/raiders-foundation and https://www.raiders.com/alumni-relations have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.raiders.com/community/raiders-foundation, whose canonical is https://www.raiders.com/foundation. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.raiders.com/game-day/2026/reg-week8/raiders-at-jets, https://www.raiders.com/community/raiders-foundation and https://www.raiders.com/alumni-relations have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

6 errors were logged to the browser console while the page loaded, for example “🚀 Failed to execute data element module core/src/lib/dataElements/customCode.js for data element identityProvider (Loc…”.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Google Ads and The Trade Desk (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.

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

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