badflag.com website review

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

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

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

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

8 third-party services load with your homepage (YouTube, replocdn.com and reamaze.com and others), adding 18.9 MB and 869 ms of main-thread time.

Shopify costs a phone 67 ms of main-thread work and 16.4 MB 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.

16 images could be 674 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

YouTube costs a phone 345 ms of main-thread work and 1.0 MB 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.

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

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

replocdn.com costs a phone 202 ms of main-thread work and 942 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 2,939 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

24 KiB could be saved by minifying JavaScript.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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

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

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

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

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

18 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 21.2 MB in 320 requests on a phone: media 14.6 MB (2), scripts 2.9 MB (98) and images 2.2 MB (79). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example Frame_5_3.png at 820 px wide, shown at 162 px. Resized copies would save about 511 KiB.

018aa2c4-e65e-473c-8eb6-ba96c2b744a6 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

ARIA commands must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

94 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: 2 elements on the page fail this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 links inside paragraphs rely on colour alone to stand out.

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is only 28 characters: “BadFlag.com – Bad Flag Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 33 characters: “BadFlag Car and Truck Flag Mounts”. 70 to 160 characters is enough to sell the click.

There are 5 <h1> headlines (“<img src="//badflag.com/cdn/shop/files/bad_flag_u…”, “Pray For Peace. Prepare For War. Men's T-Shirt” and “American Flag Leather Patch Crushable Rope Snapba…”). One clear main headline is easier for people and search engines.

The homepage links to 38 pages on badflag.com and 6 external pages.

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

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

https://badflag.com/pages/homepage-badflag, https://badflag.com/pages/pole-hardware, https://badflag.com/collections/all-flags, https://badflag.com/collections/shopify-collective-partners, https://badflag.com/collections/accessories and https://badflag.com/collections/replacement-parts and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://badflag.com/pages/homepage-badflag, https://badflag.com/pages/pole-hardware and https://badflag.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

https://badflag.com/pages/homepage-badflag and https://badflag.com/pages/pole-hardware have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'e'”.

Chrome logged issues while loading the page (“Cookie”).

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 1,317 words of visible text.

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