brooklynfc.shop website review

audioeye.com costs a phone 1.7 s of main-thread work and 301 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.

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

6 third-party services load with your homepage (audioeye.com, Klaviyo and searchatlas.com and others), adding 872 KiB and 2.0 s of main-thread time.

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

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

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

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

Klaviyo costs a phone 183 ms of main-thread work and 329 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.

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

1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

49 KiB JavaScript is shipped twice across bundles.

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

26 KiB could be saved by minifying JavaScript.

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

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.2 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 2.3 MB in 229 requests on a phone: scripts 1.0 MB (104), other files 619 KiB (54) and images 301 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

button, link, and menuitem elements do not have accessible names. (1 element).

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 22 characters: “Brooklyn FC | Fan Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“:root { --header-logo-width: 180px; }” and “26% OFF EVERYTHING”). One clear main headline is easier for people and search engines.

The homepage links to 112 pages on brooklynfc.shop and 16 external pages.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'dataset') https://brooklynfc.shop/cdn/shop/t/40/assets/rich-text.js?v=28348736…”.

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

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