1buck80.com website review

7 third-party services load with your homepage (YouTube, Bigcommerce and Facebook and others), adding 2.0 MB and 884 ms of main-thread time.

About 675 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 360 ms faster on a phone.

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

YouTube costs a phone 490 ms of main-thread work and 999 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.

4 images could be 190 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Bigcommerce costs a phone 246 ms of main-thread work and 610 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.

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

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

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

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

Polyfills for old browsers add 11 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.

5 KiB could be saved by minifying JavaScript.

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

Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

4 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.0 MB in 51 requests on a phone: scripts 1.2 MB (14), images 338 KiB (17) and fonts 180 KiB (4). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Untitled_design-22.png at 1,968 px wide, shown at 390 px. Resized copies would save about 125 KiB.

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

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

Your title is only 11 characters: “1buck80.com”. 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.

Your meta description is only 27 characters: “1 buck 80 - Don't Get Smart”. 70 to 160 characters is enough to sell the click.

21 links have no real href, so search engines can't follow them.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://1buck80.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 73 pages on 1buck80.com and 3 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://1buck80.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.

https://1buck80.com/categories, https://1buck80.com/hoodys, https://1buck80.com/sweaters, https://1buck80.com/t-shirts, https://1buck80.com/about and https://1buck80.com/www.1buck80.com/shipping-returns and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://1buck80.com/giftcertificates.php and https://1buck80.com/compare use the same meta description. A description written for each page earns more clicks.

https://1buck80.com/hoodys, https://1buck80.com/sweaters, https://1buck80.com/about, https://1buck80.com/www.1buck80.com/contact, https://1buck80.com/blog and https://1buck80.com/giftcertificates.php and 2 others 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 19 found) and read each the way a search engine does.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is served at too low a resolution for sharp phone screens.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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 Google Ads 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 14 cookies, 2 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.