brookandyork.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Shopify and others), adding 2.2 MB and 1.2 s of main-thread time.

Google Tag Manager costs a phone 502 ms of main-thread work and 522 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.

14 images could be 380 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.

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

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

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

Google CDN costs a phone 174 ms of main-thread work and 333 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.

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

Shopify costs a phone 112 ms of main-thread work and 305 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.

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

tidio.co costs a phone 80 ms of main-thread work and 515 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.

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

About 63 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 240 ms faster on a phone.

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

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

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

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

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

Your homepage downloads 5.1 MB in 325 requests on a phone: scripts 2.4 MB (107), other files 1.1 MB (153) and images 991 KiB (30). Under 2 MB keeps phones on slow connections fast.

1 image (116 KiB) is 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 1.44 g of CO₂e: 172.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

The homepage links to 158 pages on brookandyork.com and 10 external pages.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5223573&Ver=2&mid=a01e1e31-752f-4ab3-a668-b3ed80a4cba5&bo=1&sid=d6280350d9ca11f18d7b11560212f88e&vid=d62801b0d9ca11f1afe451072a390958&vids=1&msclkid=N&pi=918639831&lg=.

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

2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://brookandyork.com/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

brookandyork.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

brookandyork.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage carries about 570 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 28 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.