boxabl.com website review

11 images could be 12.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.1 s faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, noform.ai and Facebook and others), adding 1.5 MB and 1.1 s of main-thread time.

About 515 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 58 (desktop: 54). Pages that score under 90 lose visitors before the first paint.

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

Google Tag Manager costs a phone 590 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.

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

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

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

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 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero Image 1”.

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

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

Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 14.7 MB in 235 requests on a phone: images 12.4 MB (48), scripts 2.0 MB (70) and other files 111 KiB (103). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 4 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.

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

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

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

Your title is only 6 characters: “BOXABL”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 30 characters: “BOXABL - The Future of Housing”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 57 pages on boxabl.com and 20 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187169301&Ver=2&mid=133af130-feeb-458a-8cda-6dc177b11545&bo=1&sid=b3c1a5c0ce2411f1922dc1b4c701c9c2&vid=b3c1bf40ce2411f1afe251ad87b6242a&vids=1&msclkid=N&pi=918639831&l.

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

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

Chrome logged issues while loading the page (“Cookie”).

1 link from your homepage to your own site is broken, for example https://www.boxabl.com/cdn-cgi/l/email-protection (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://www.boxabl.com/disclosure.

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.

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

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.

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

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 HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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