thebrokenbindingsub.com website review

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

9 images could be 890 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and vitals.app and others), adding 1.1 MB and 330 ms of main-thread time.

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

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

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

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

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

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

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

Your largest element takes 32.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SPECIALS & SUBSCRIPTIONS We, the Broken Binding SE, pride o…”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.4 MB in 235 requests on a phone: images 7.0 MB (34), scripts 1.3 MB (56) and other files 900 KiB (120). Under 2 MB keeps phones on slow connections fast.

21 images are downloaded at several times the size a phone draws them, for example logo-full.webp at 1,852 px wide, shown at 130 px. Resized copies would save about 2.3 MB.

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

3 images (2.1 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.

19 images further down the page (2.1 MB) 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 2.66 g of CO₂e: 319.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

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.

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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. (3 elements).

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 105 pages on thebrokenbindingsub.com and 12 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads 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 15 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.