bigrays.com website review

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

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

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

18 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, myomni.app and marsello.app and others), adding 3.9 MB and 851 ms of main-thread time.

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

177 KiB could be saved by minifying JavaScript.

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

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

myomni.app costs a phone 183 ms of main-thread work and 776 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,314 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

marsello.com costs a phone 75 ms of main-thread work and 1.1 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.

marsello.app costs a phone 106 ms of main-thread work and 715 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.

Shopify costs a phone 45 ms of main-thread work and 304 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

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

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

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

3 KiB JavaScript is shipped twice across bundles.

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 27.7 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 28.3 s. Good is under 3.8 s.

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

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

For real visitors the layout shifts by 0.13 (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 77 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 842 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Your homepage downloads 7.9 MB in 254 requests on a phone: images 3.1 MB (22), scripts 3.1 MB (91) and other files 774 KiB (101). Under 2 MB keeps phones on slow connections fast.

Big-Rays-Alaskan-Outfitter-Winter-Catalog-Shoot-2025_Lena-Le weighs 692 KiB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Big-Rays-Alaskan-Outfitter-Winter-Catalog-Shoot-2025_Lena-Le at 2,247 px wide, shown at 406 px. Resized copies would save about 533 KiB.

instagram-image-9c1ed07b-ee2d-4301-ba95-458fdc1244a8.jpg 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).

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

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

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

2 frames have no title, so screen-reader users cannot tell what they contain.

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

Your title is only 21 characters: “Big Ray's – Big Ray's”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 377 pages on bigrays.com and 4 external pages.

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

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

https://bigrays.com/customer_authentication/redirect, https://bigrays.com/collections/mens, https://bigrays.com/collections/mens/Bottoms, https://bigrays.com/collections/mens/Bottoms+Bibs, https://bigrays.com/collections/mens/Bottoms+Snow-Pants and https://bigrays.com/collections/mens/Bottoms+Jeans and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://bigrays.com/collections/mens/Bottoms, whose canonical is https://bigrays.com/collections/mens/bottoms. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

https://bigrays.com/collections/mens/Bottoms+Snow-Pants, https://bigrays.com/collections/mens/Bottoms+Jeans, https://bigrays.com/collections/mens/Bottoms+Pants and https://bigrays.com/collections/mens/Bottoms+Rain-Pants took over 3 s to send their HTML from our server.

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

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.

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

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