myaquasource.net website review

51 files are served with short cache lifetimes, so returning visitors download them again (6.1 MB).

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

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.5 s faster on a phone.

About 145 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Vimeo, Usercentrics CMP and Hotjar and others), adding 6.2 MB and 221 ms of main-thread time.

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

Vimeo costs a phone 94 ms of main-thread work and 2.6 MB 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.

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

Azure Web Services costs a phone 0 ms of main-thread work and 3.1 MB 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 2.5 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

14 long tasks block the main thread while loading, the longest for 155 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.

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.

For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.

Your largest element takes 41.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

The layout shifts by 0.954 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 82 ms to 87 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 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.6 MB in 120 requests on a phone: images 7.6 MB (33), scripts 2.3 MB (36) and fonts 404 KiB (7). Under 2 MB keeps phones on slow connections fast.

6 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 0005107_Web-banner-Organic-Algae-mobile-EN.jpeg at 1,440 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

10 images (5.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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 340 characters; Google truncates after about 160, so the end of your pitch is cut.

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

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 40 pages on myaquasource.net and 1 external page.

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.

There is no https://myaquasource.net/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://myaquasource.net/products/findproduct/ORGALC120, https://myaquasource.net/products/findproduct/ORGGEC120, https://myaquasource.net/products/findproduct/RPC140 and https://myaquasource.net/products/findproduct/ORGSBC060 all use the title “AquaSource”. Search engines can't tell which page to show for a search, so each competes with the others.

https://myaquasource.net/recentlyviewedproducts, https://myaquasource.net/products/findproduct/ORGALC120, https://myaquasource.net/products/findproduct/ORGGEC120, https://myaquasource.net/products/findproduct/RPC140, https://myaquasource.net/our-story and https://myaquasource.net/for-a-fresh-start and 6 others use the same meta description. A description written for each page earns more clicks.

https://myaquasource.net/products/findproduct/ORGALC120, https://myaquasource.net/products/findproduct/ORGGEC120, https://myaquasource.net/products/findproduct/RPC140, https://myaquasource.net/products/findproduct/ORGSBC060 and https://myaquasource.net/nutrition have no <h1> headline, so visitors and search engines get no clear main topic.

https://myaquasource.net/recentlyviewedproducts has 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 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 error was logged to the browser console while the page loaded, for example “Could not detect carousel for plugin "jcarouselControl"”.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 3 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.

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

Before a visitor clicks anything, the page loads Hotjar (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 16 cookies, 2 of them by other companies (measured from a US location before any click).

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