maxbone.com website review

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

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

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

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

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

8 third-party services load with your homepage (Accessibe Accessibility Overlay, forethought.ai and Klaviyo and others), adding 2.4 MB and 2.8 s of main-thread time.

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

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

forethought.ai costs a phone 587 ms of main-thread work and 1,001 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.

Accessibe Accessibility Overlay costs a phone 601 ms of main-thread work and 250 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.

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

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

Klaviyo costs a phone 418 ms of main-thread work and 336 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.

cloudfront.net costs a phone 339 ms of main-thread work and 169 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 317 ms of main-thread work and 240 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.

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

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.

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (6.6 s).

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

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

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

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

9 images 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' tap response (inp) went from 123 ms to 134 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.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 31.0 MB in 291 requests on a phone: media 25.8 MB (2), scripts 3.2 MB (111) and images 1,012 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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.

There are 4 <h1> headlines (“The smart way to feed daily”, “For dogs with great taste.” and “Don’t Just Take Our Word For It.”). One clear main headline is easier for people and search engines.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 205 pages on maxbone.com and 8 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.

/pages/collaborations and /pages/brands-who-love-max-bone all use the title “Exclusive Collaborations with brands we love | maxbone”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/rewards, /blogs/mb-eats, /collections/shop-all-products, /collections/food and /blogs/max-world have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/collaborations and /pages/brands-who-love-max-bone use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/brands-who-love-max-bone, whose canonical is /pages/collaborations. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/rewards has no <h1> headline, so visitors and search engines get no clear main topic.

/pages/brands-who-love-max-bone took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://cdn.klaviyomail.com/company/HJWY7J/images/2ca5368c-aace-45a0-88a1-4c7fc48054f1.jpeg.

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

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

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

2 links go through two or more redirects, for example https://www.maxbone.com/account/login.

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.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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,515 words of visible text.

DMARC is set to p=none, so mail pretending to be maxbone.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Criteo, Google Ads, Google Analytics, Google Tag Manager 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 34 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 66 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.