365gameday.com website review

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

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

About 260 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 720 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Privy, Facebook and Twitter and others), adding 499 KiB and 212 ms of main-thread time.

About 30 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.

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

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

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

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.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

332 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

2 links inside paragraphs rely on colour alone to stand out.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

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

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

Your title is only 27 characters: “"Where Everyday is Gameday"”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 56 characters: “Come find the best gear in the nation for your top team!”. 70 to 160 characters is enough to sell the click.

2 links have no real href, so search engines can't follow them.

The homepage links to 879 pages on 365gameday.com and 13 external pages.

https://365gameday.com/collections/lsu-all-gear, https://365gameday.com/collections/lsu-apparel/mens-shirt, https://365gameday.com/collections/lsu-apparel/NCAA-Footwear, https://365gameday.com/collections/ncaa-drinkware-coolers/LSU-Tigers, https://365gameday.com/collections/georgia-all-gear and https://365gameday.com/collections/georgia-mens-apparel/Bowl-Game-Playoffs and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://365gameday.com/collections/lsu-apparel/NCAA-Footwear, whose canonical is https://365gameday.com/collections/lsu-apparel/ncaa-footwear. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://365gameday.com/collections/lsu-all-gear, https://365gameday.com/collections/lsu-apparel/mens-shirt, https://365gameday.com/collections/lsu-apparel/NCAA-Footwear, https://365gameday.com/collections/ncaa-drinkware-coolers/LSU-Tigers, https://365gameday.com/collections/georgia-all-gear and https://365gameday.com/collections/georgia-mens-apparel/Bowl-Game-Playoffs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot destructure property 'name' of 'e' as it is undefined.”.

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 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 2,372 words of visible text.

Before a visitor clicks anything, the page loads Meta Pixel (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.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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