takingbacksundaystore.com website review

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

8 third-party services load with your homepage (spotifycdn.com, Google CDN and Bold Commerce and others), adding 1.4 MB and 777 ms of main-thread time.

About 606 KiB of JavaScript is downloaded but never used on this page.

spotifycdn.com costs a phone 400 ms of main-thread work and 716 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.

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

9 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

About 76 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LOUDER NOW 20TH ANNIVERSARY VINYL AVAILABLE NOW”. Most of its time is element render delay (2.4 s).

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

Your homepage downloads 3.4 MB in 202 requests on a phone: scripts 1.3 MB (58), images 1.1 MB (28) and other files 744 KiB (96). Under 2 MB keeps phones on slow connections fast.

mobile-8.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

2 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 24 characters: “Taking Back Sunday Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 40 characters: “Taking Back Sunday Official Online Store”. 70 to 160 characters is enough to sell the click.

There are 2 <h1> headlines (“Taking Back Sunday” and “Taking Back Sunday Red Rocks 2026 Poster”). One clear main headline is easier for people and search engines.

The homepage links to 99 pages on takingbacksundaystore.com and 17 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.

https://takingbacksundaystore.com/collections/all, https://takingbacksundaystore.com/collections/shirts-tank-tops, https://takingbacksundaystore.com/collections/womens-shirts-tanks, https://takingbacksundaystore.com/collections/sweatshirts, https://takingbacksundaystore.com/collections/jackets and https://takingbacksundaystore.com/collections/152-merch and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://takingbacksundaystore.com/collections/louder-now-20th-anniversary/products/taking-back-sunday-louder-now-20th-anniversary-edition-vinyl-laminate-1, whose canonical is https://takingbacksundaystore.com/products/taking-back-sunday-louder-now-20th-anniversary-edition-vinyl-laminate-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

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 548 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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 12 cookies, 2 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.