Website review, no card needed

aquis.com logo

aquis.com website review

Visit site (opens in a new tab)Reviewed 11 November 202631 issues · 76 checks

This review found 31 issues worth fixing on aquis.com, 9 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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
1.1 s770 msAug 29Nov 7884 ms
Show as table
DateReal-visitor load time (LCP)
Aug 29, 20261.0 s
Sep 5, 2026894 ms
Sep 12, 2026876 ms
Sep 19, 2026818 ms
Sep 26, 2026805 ms
Oct 3, 2026845 ms
Oct 10, 2026850 ms
Oct 17, 2026895 ms
Oct 24, 2026924 ms
Oct 31, 2026922 ms
Nov 7, 2026884 ms
Real-visitor tap response (INP)75th percentile, phones
67 ms58 msSep 5Nov 766 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 202666 ms
Sep 12, 202663 ms
Sep 19, 202662 ms
Sep 26, 202662 ms
Oct 3, 202662 ms
Oct 10, 202659 ms
Oct 17, 202661 ms
Oct 24, 202662 ms
Oct 31, 202665 ms
Nov 7, 202666 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 aquis.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aquis.com at 0.5 s0.5 s
  2. aquis.com at 1.0 s1.0 s
  3. aquis.com at 1.6 s1.6 s
  4. aquis.com at 2.1 s2.1 s
  5. aquis.com at 2.6 s2.6 s
  6. aquis.com at 3.1 s3.1 s
  7. aquis.com at 3.7 s3.7 s
  8. aquis.com at 4.2 s4.2 s

Speed

4 to fix61
  • Reduce unused JavaScript

    1.8 s · 346 KiB

    About 346 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Accessibe Accessibility Overlay, Shopify and jQuery CDN and others), adding 12.5 MB and 235 ms of main-thread time.

  • Shopify adds 26 ms

    26 ms

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

  • Mobile performance score: 61

    61/100

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

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 24 KiB

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

  • Legacy JavaScript

    15 KiB

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

  • Improve image delivery

    13 KiB

    1 image could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

  • Use efficient cache lifetimes

    1 KiB

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

2 checks passed
  • Main-thread work: 1.4 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 8.9 s

    8.9 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.111

    0.111

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.3 s

    1.3 s

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

  • Real-user INP: 78 ms

    78 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 315 ms

    315 ms

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

  • Total Blocking Time: 187 ms

    187 ms

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

Images and page weight

1 to fix70
  • Page weight: 13.7 MB in 182 requests

    13.7 MB

    Your homepage downloads 13.7 MB in 182 requests on a phone: media 12.1 MB (3), scripts 747 KiB (37) and other files 681 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (38 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 3.9 g of CO₂ per visit

    3.88 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

3 to fixGoogle 9695
  • 3 text elements with low contrast

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

  • 1 image without alt text

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

  • Alternative text of images should not be repeated as text (1 element)

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

6 to fixGoogle 8573
  • No meta description

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

  • Title is short (8 characters)

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

  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

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

  • 14 internal links, 7 external

    The homepage links to 14 pages on aquis.com and 7 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “My Store”.

  • Canonical URL set

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

  • 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://aquis.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

2 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.

  • llms.txt published

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

Other pages

3 to fix65
  • 3 linked pages are broken

    Your homepage links to https://aquis.com/products/aquis-flip-amethyst, https://aquis.com/products/aquis-wrap-glacier and https://aquis.com/products/aquis-towel-whitecap, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://aquis.com/collections and https://aquis.com/pages/our-story have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://aquis.com/collections, https://aquis.com/pages/technology and https://aquis.com/pages/our-story have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://aquis.com/collections 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.

  • 6 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

    8 of 13 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: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • Only about 128 words

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

  • 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP” and “LEARN MORE”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 aquis.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2023.

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
Novato

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on aquis.com, including 10 speed issues, 6 SEO issues and 4 conversion gaps. 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