nixplay.ca website review

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

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

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

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

7 third-party services load with your homepage (Shopify, nixplay.com and shop.app and others), adding 296 KiB and 522 ms of main-thread time.

Shopify costs a phone 521 ms of main-thread work and 243 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.

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

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

About 76 KiB of JavaScript is downloaded but never used on this page.

32 KiB could be saved by minifying JavaScript.

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

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

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 layout shifts by 0.539 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “with shared albums”.

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

Real visitors wait 824 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

Your homepage downloads 7.5 MB in 144 requests on a phone: media 5.6 MB (6), images 746 KiB (46) and other files 557 KiB (36). Under 2 MB keeps phones on slow connections fast.

6 images (1.1 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.

7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 3ba781abfc24489ebdea15232f273a93.thumbnail.0000000000.jpg at 721 px wide, shown at 1 px. Resized copies would save about 55 KiB.

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

There are 2 <h1> headlines (“How can we help?” and “Tell your story with shared albums with web and m…”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 132 pages on nixplay.ca and 29 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.nixplay.ca/pages/features, https://www.nixplay.ca/pages/photo-management, https://www.nixplay.ca/pages/photo-editing, https://www.nixplay.ca/pages/nix-events, https://www.nixplay.ca/pages/competitions and https://www.nixplay.ca/pages/plan-compare and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

The homepage carries about 538 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Opening the homepage sets 4 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.