Website review, no card needed

theaquavault.com logo

theaquavault.com website review

Visit site (opens in a new tab)Reviewed 7 November 202623 issues · 82 checks

This review found 23 issues worth fixing on theaquavault.com, 4 of them high impact, across 82 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.1 s981 msMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.7 s
May 30, 20262.4 s
Jun 6, 20261.9 s
Jun 13, 20261.5 s
Jun 20, 20261.3 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.7 s
Jul 18, 20261.8 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20263.2 s
Oct 10, 20263.6 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
460 ms145 msMay 16Oct 31412 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026185 ms
May 23, 2026187 ms
May 30, 2026181 ms
Jun 6, 2026184 ms
Jun 13, 2026188 ms
Jun 20, 2026187 ms
Jun 27, 2026192 ms
Jul 4, 2026194 ms
Jul 11, 2026195 ms
Jul 18, 2026203 ms
Jul 25, 2026204 ms
Aug 1, 2026203 ms
Aug 8, 2026199 ms
Aug 15, 2026196 ms
Aug 22, 2026195 ms
Aug 29, 2026195 ms
Sep 5, 2026211 ms
Sep 12, 2026215 ms
Sep 19, 2026217 ms
Sep 26, 2026220 ms
Oct 3, 2026289 ms
Oct 10, 2026402 ms
Oct 17, 2026424 ms
Oct 24, 2026424 ms
Oct 31, 2026412 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of theaquavault.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. theaquavault.com at 0.4 s0.4 s
  2. theaquavault.com at 0.8 s0.8 s
  3. theaquavault.com at 1.1 s1.1 s
  4. theaquavault.com at 1.5 s1.5 s
  5. theaquavault.com at 1.9 s1.9 s
  6. theaquavault.com at 2.3 s2.3 s
  7. theaquavault.com at 2.6 s2.6 s
  8. theaquavault.com at 3.0 s3.0 s

Speed

2 to fix98
  • Render-blocking requests

    1.7 s

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

  • 1,598 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (negate.io, pii.ai and Shopify and others), adding 538 KiB and 198 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    144 KiB

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

  • Reduce unused CSS

    107 KiB

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

  • Improve image delivery

    30 KiB

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

  • Minify CSS

    17 KiB

    17 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 checks passed
  • Mobile performance score: 98

    98/100

    Your mobile performance score is 98. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 458 ms of it running JavaScript. That is comfortably low.

  • Server response: 17 ms

    17 ms

    Your server sent the HTML in 17 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user INP: 222 ms

    222 ms

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

  • Tap response (INP) got 125% slower for real visitors

    +125%

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Time to Interactive: 4.2 s

    4.2 s

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

  • 8 images without width and height

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

8 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 469 ms

    469 ms

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 130 ms

    130 ms

    Scripts block the page for only 130 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “🔄”.

Images and page weight

3 to fix69
  • 1 image over 500 KB

    ChargeCardr-World_s-Thinnest-Portable-Charger-AquaVault-Inc. weighs 854 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    1_1.jpg 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).

  • 1 image in older formats

    1 image (854 KiB) is 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.

  • About 0.5 g of CO₂ per visit

    0.54 g

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

2 checks passed
  • Page weight: 1.9 MB in 87 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 87 requests on a phone: images 839 KiB (31), scripts 789 KiB (38) and stylesheets 137 KiB (9). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9795
  • 12 tap targets too small

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

  • All page content should be contained by landmarks (3 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 73 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8593
  • Meta description is long (320 characters)

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

  • 3 links with vague text

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

  • 89 internal links, 11 external

    The homepage links to 89 pages on theaquavault.com and 11 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “AquaVault Inc.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Premium Travel & Mobile Phone Accessories – AquaVault Inc.”.

  • Canonical URL set

    The canonical URL is https://theaquavault.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://theaquavault.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (841 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://theaquavault.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 5 pages without an H1

    https://theaquavault.com/collections/aquavault, https://theaquavault.com/pages/hotels-and-partners, https://theaquavault.com/products/flexsafe, https://theaquavault.com/products/soundcharge-portable-speaker-and-power-bank and https://theaquavault.com/products/aquavault-waterproof-floating-case have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://theaquavault.com/products/flexsafe, https://theaquavault.com/products/credit-card-sized-portable-charger, https://theaquavault.com/products/wireless-magnetic-chargecard, https://theaquavault.com/products/soundcharge-portable-speaker-and-power-bank, https://theaquavault.com/products/magnetic-wallet-with-phone-grip and https://theaquavault.com/products/aquavault-waterproof-floating-case and 1 other 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 30 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Local business without LocalBusiness data

    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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 697 words of copy

    The homepage carries about 697 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP ALL”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “SHOP”, “Shop Now” and “Add order notes”.

  • 9 short forms

    9 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 55 testimonial or review blocks, 8 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 15 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at theaquavault.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pieeye · Gemx Cro A B Testing · Instafeed · Gempages Builder · Klaviyo Email Marketing Sms · Judge Me Reviews · Kaching Bundles · Aftership Returns · Aftersell · Upcart · Psd Viewer Real3d Flipbook · archive-digger.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Miami

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on theaquavault.com, including 9 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25