blackveilbrides.net website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.

14 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

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

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

8 third-party services load with your homepage (route.com, Google Tag Manager and bandsintown.com and others), adding 2.1 MB and 1.3 s of main-thread time.

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

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

route.com costs a phone 378 ms of main-thread work and 542 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.

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

bandsintown.com costs a phone 215 ms of main-thread work and 449 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 148 ms of main-thread work and 317 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,517 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

13 KiB could be saved by minifying CSS.

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

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 17.4 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 21.9 s. Good is under 3.8 s.

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

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

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

Real visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 4.2 MB in 304 requests on a phone: scripts 2.4 MB (151), other files 808 KiB (117) and images 648 KiB (16). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 3cb6ce07-dd66-42d3-9762-234a03d9db36.png at 5,019 px wide, shown at 356 px. Resized copies would save about 105 KiB.

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

19 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“Black Veil Brides”, “” and “Latest merch”). One clear main headline is easier for people and search engines.

The homepage links to 62 pages on blackveilbrides.net and 18 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.blackveilbrides.net/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.blackveilbrides.net/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.blackveilbrides.net/collections/music, https://www.blackveilbrides.net/apps/single/membership and https://www.blackveilbrides.net/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.blackveilbrides.net/products/black-veil-brides-corpse-f-b-wht, https://www.blackveilbrides.net/products/black-veil-brides-sharp-f-b-wht, https://www.blackveilbrides.net/products/black-veil-brides-mirror-f-b-wht and https://www.blackveilbrides.net/products/black-veil-brides-house-of-wap-wht use the same meta description. A description written for each page earns more clicks.

https://www.blackveilbrides.net/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.blackveilbrides.net/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 168 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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