bigagnes.com website review

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

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

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

8 third-party services load with your homepage (Klaviyo, Osano CMP and Shopify and others), adding 1.5 MB and 1.5 s of main-thread time.

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

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

Klaviyo costs a phone 381 ms of main-thread work and 649 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 347 ms of main-thread work and 464 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.

Osano CMP costs a phone 354 ms of main-thread work and 85 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.

Bazaarvoice costs a phone 289 ms of main-thread work and 105 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.

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

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

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

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

40 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 7.7 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 896 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 4.9 MB in 268 requests on a phone: images 2.0 MB (43), scripts 1.6 MB (100) and other files 808 KiB (107). Under 2 MB keeps phones on slow connections fast.

NoahWetzel_1314_5833_BrownsCreek-LOWRES_480x.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 1.39 g of CO₂e: 166.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 137 pages on bigagnes.com and 6 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bigagnes.com/pages/accessibility-statement, whose canonical is https://www.bigagnes.com/pages/accessibility-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

3 errors were logged to the browser console while the page loaded, for example “Unexpected token 'false'”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.