shopbitsandbows.com website review

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

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

12 images could be 290 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.

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

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

Shopify costs a phone 110 ms of main-thread work and 309 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 third-party services load with your homepage (Shopify, automizely.com and automizely-analytics.com and others), adding 503 KiB and 327 ms of main-thread time.

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

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

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

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

9 KiB could be saved by minifying CSS.

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 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Featured banner image”.

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

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

Your homepage downloads 2.6 MB in 206 requests on a phone: images 933 KiB (21), other files 774 KiB (106) and scripts 543 KiB (67). Under 2 MB keeps phones on slow connections fast.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

Alternative text of images should not be repeated as text: 14 elements on the page fail this check, rated minor by axe-core.

Your title is only 25 characters: “Bits & Bows | Accessories”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 145 pages on shopbitsandbows.com and 8 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.

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

15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=52013962&Ver=2&mid=6d45d23c-2058-48b8-85e4-2c10d59661fd&bo=1&sid=f5822660dab011f1baca6f299d21309e&vid=f5825de0dab011f198cce11f9900cad4&vids=1&msclkid=N&pi=918639831&lg.

Social proof on the homepage: 37 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 1 more (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 19 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.