bixpy.com website review

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

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

About 538 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.

8 third-party services load with your homepage (Google Tag Manager, Shopify and corso.com and others), adding 1.4 MB and 872 ms of main-thread time.

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

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

Google Tag Manager costs a phone 286 ms of main-thread work and 334 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.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Shopify costs a phone 170 ms of main-thread work and 479 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,873 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 55 KiB of CSS is downloaded but never applied on this page.

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.

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.

2 KiB could be saved by minifying CSS.

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 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a blue and white sign”.

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

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

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

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

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

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

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

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

Your homepage downloads 8.4 MB in 272 requests on a phone: media 5.2 MB (1), scripts 1.5 MB (99) and other files 732 KiB (96). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Dynamic_Black_Friday_Banner.png at 1,000 px wide, shown at 300 px. Resized copies would save about 12 KiB.

3 images (174 KiB) are 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.

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

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

3 images have no alt text, which hurts accessibility and image search.

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

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

Your title is 71 characters, so Google will cut it off around 60: “Bixpy Kayak Propulsion System | Electric Outboard Motors – Bixpy Motors”.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 190 pages on bixpy.com and 10 external pages.

/collections/all, /policies/shipping-policy, /pages/kayak-motors, /pages/paddleboard-motors, /pages/float-tube-belly-boat-motors and /pages/canoe-motors and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/bixpy-fin-box-adapters took over 3 s to send its HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://bixpy.com/blogs/bixpy-blog/tagged/speciality-mounting (404).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://bixpy.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

bixpy.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

bixpy.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

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.

The homepage carries about 805 words of visible text.

DMARC is set to p=none, so mail pretending to be bixpy.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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