maxtrixkids.com website review

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

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

8 third-party services load with your homepage (ContentSquare, Google Tag Manager and Klaviyo and others), adding 2.1 MB and 2.6 s of main-thread time.

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

About 1,010 KiB of JavaScript is downloaded but never used on this page.

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

ContentSquare costs a phone 969 ms of main-thread work and 178 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 700 ms.

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

Klaviyo costs a phone 291 ms of main-thread work and 508 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 262 ms of main-thread work and 86 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 172 ms. During a long task the page ignores taps.

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

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

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

8 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Brother and sister playing on solid wood bunk bed with slid…”.

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 7.6 MB in 493 requests on a phone: scripts 3.0 MB (183), media 2.6 MB (1) and other files 1.0 MB (232). Under 2 MB keeps phones on slow connections fast.

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

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

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 81 characters, so Google will cut it off around 60: “Customizable Bunk Beds & Loft Beds, Mattresses, Dressers & Storage – Maxtrix Kids”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 261 pages on maxtrixkids.com and 4 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.

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

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

https://www.maxtrixkids.com/customer_authentication/redirect and https://www.maxtrixkids.com/collections/twin-xl-over-queen-bunk-beds have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.maxtrixkids.com/collections/black-friday-doorbusters, https://www.maxtrixkids.com/customer_authentication/redirect, https://www.maxtrixkids.com/collections/bunk-beds, https://www.maxtrixkids.com/collections/best-sellers, https://www.maxtrixkids.com/collections/twin-bunk-beds and https://www.maxtrixkids.com/collections/xl-queen-bunk-beds and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://i.liadm.com/s/85221?&aid=60ae8e66-c8ac-46ce-9df3-710db3481105&ref=907DD37B&_=0.8673974843290815.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Contentsquare tag 966284 skipped: another Contentsquare tag already runs”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 54 cookies (measured from a US location before any click).

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