360immerse.ca website review

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

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

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

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

1 image could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 162 ms of main-thread time.

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

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

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.

Your largest element takes 30.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “REDEFINING EXCELLENCE THROUGH AN VISIONARY IMMERSIVE EXCLUS…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 19.9 MB in 54 requests on a phone: media 11.3 MB (5), images 6.7 MB (20) and fonts 696 KiB (7). Under 2 MB keeps phones on slow connections fast.

9 images weigh 6.2 MB together. On a phone connection a single image that size takes seconds.

12 images are downloaded at several times the size a phone draws them, for example 64-Brahms-Bay-Twilight-9-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 5.2 MB.

15 images (6.6 MB) 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.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

The homepage links to 24 pages on 360immerse.ca and 5 external pages.

There is no https://www.360immerse.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.360immerse.ca/privacy and https://www.360immerse.ca/terms have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.360immerse.ca/contact and https://www.360immerse.ca/book-now have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 8 pages linked from your homepage 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: the server responded with a status of 410 ()”.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 87 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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