getaquafairy.com website review

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

8 third-party services load with your homepage (Google Tag Manager, replocdn.com and Clarity and others), adding 1.8 MB and 920 ms of main-thread time.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

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

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

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

replocdn.com costs a phone 258 ms of main-thread work and 634 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.

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

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

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

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

13 KiB could be saved by minifying CSS.

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

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 15.6 s. Good is under 3.8 s.

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

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

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

The first text or image appears after 2.1 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 137 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.3 MB in 231 requests on a phone: scripts 1.3 MB (65), other files 874 KiB (122) and images 727 KiB (21). Under 2 MB keeps phones on slow connections fast.

c9c4b743-bdbe-4c07-a85e-94cc9156b84f 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).

4 images are downloaded at several times the size a phone draws them, for example 2_13a52abd-25e2-4616-b3ad-6dec04212160.webp at 700 px wide, shown at 159 px. Resized copies would save about 181 KiB.

6 images (423 KiB) 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.

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

Scrollable region must have keyboard access: 20 elements on the page fail this check, rated serious by axe-core.

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

ARIA commands must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 2 <h1> headlines (“Curiosity Planet” and “If it's trending, it's here.”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 23 pages on getaquafairy.com and 1 external page.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

https://mycuriosityplanet.com/pages/trending-now, https://mycuriosityplanet.com/customer_authentication/redirect, https://mycuriosityplanet.com/policies/terms-of-service, https://mycuriosityplanet.com/policies/refund-policy, https://mycuriosityplanet.com/policies/shipping-policy and https://mycuriosityplanet.com/policies/contact-information and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://mycuriosityplanet.com/customer_authentication/redirect and https://mycuriosityplanet.com/apps/parcelpanel have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage carries about 284 words of visible text.

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