Website review, no card needed

aaopticalco.com logo

aaopticalco.com website review

Visit site (opens in a new tab)Reviewed 19 October 202633 issues · 65 checks

This review found 33 issues worth fixing on aaopticalco.com, 10 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. 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 s3.1 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.8 s
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.9 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.4 s
Jul 11, 20263.2 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
136 ms95 msJun 13Oct 17112 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026131 ms
Jun 27, 2026108 ms
Jul 4, 2026100 ms
Jul 18, 2026114 ms
Aug 22, 2026104 ms
Aug 29, 2026112 ms
Sep 5, 2026116 ms
Sep 12, 2026111 ms
Sep 19, 2026111 ms
Sep 26, 2026113 ms
Oct 3, 2026111 ms
Oct 10, 2026113 ms
Oct 17, 2026112 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 aaopticalco.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix91
  • Font display

    700 ms

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

  • Render-blocking requests

    400 ms

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

  • Improve image delivery

    150 ms · 81 KiB

    9 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    150 ms · 14 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (14 KiB).

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

3 checks passed
  • Mobile performance score: 91

    91/100

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

  • Main-thread work: 0.1 s

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

  • Server response: 84 ms

    84 ms

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

Core Web Vitals

6 to fix0
  • 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 CLS: 1.11

    1.11

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A&A Optical Logo”.

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

7 checks passed
  • Real-user TTFB: 583 ms

    583 ms

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

  • Largest content (LCP) got 10% faster for real visitors

    -10%

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

  • Time to Interactive: 3.4 s

    3.4 s

    The page is fully interactive after 3.4 s.

  • Cumulative Layout Shift: 0.058

    0.058

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

  • Speed Index: 2.4 s

    2.4 s

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • 2 images below the first screen load straight away

    2 images further down the page (55 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.2 g of CO₂ per visit

    0.20 g

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

3 checks passed
  • Page weight: 735 KiB in 20 requests

    735 KiB

    Your homepage downloads 735 KiB in 20 requests on a phone: other files 250 KiB (2), fonts 240 KiB (2) and images 170 KiB (12). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7787
  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • Links must have discernible text (3 elements)

    Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 1 text element with low contrast

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

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

8 to fixGoogle 8358
  • No meta description

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

  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “A&A Optical Storefront”. 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 canonical URL

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

  • No social preview image

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

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • 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://store.aaopticalco.com/s/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.

  • No llms.txt

    There is no https://www.aaopticalco.com/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.

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

Best practices

2 to fixGoogle 8883
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • No call to action on the first screen

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 140 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on aaopticalco.com, including 8 speed issues, 8 SEO issues and 6 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