Website review, no card needed

analuisa.com logo

analuisa.com website review

Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 87 checks

This review found 40 issues worth fixing on analuisa.com, 18 of them high impact, across 87 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
2.8 s2.2 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
241 ms188 msMay 2Oct 17228 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026196 ms
May 9, 2026195 ms
May 16, 2026194 ms
May 23, 2026196 ms
May 30, 2026196 ms
Jun 6, 2026196 ms
Jun 13, 2026200 ms
Jun 20, 2026202 ms
Jun 27, 2026203 ms
Jul 4, 2026202 ms
Jul 11, 2026202 ms
Jul 18, 2026201 ms
Jul 25, 2026204 ms
Aug 1, 2026212 ms
Aug 8, 2026220 ms
Aug 15, 2026230 ms
Aug 22, 2026235 ms
Aug 29, 2026232 ms
Sep 5, 2026232 ms
Sep 12, 2026228 ms
Sep 19, 2026228 ms
Sep 26, 2026229 ms
Oct 3, 2026229 ms
Oct 10, 2026229 ms
Oct 17, 2026228 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 analuisa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. analuisa.com at 0.9 s0.9 s
  2. analuisa.com at 1.9 s1.9 s
  3. analuisa.com at 2.8 s2.8 s
  4. analuisa.com at 3.8 s3.8 s
  5. analuisa.com at 4.7 s4.7 s
  6. analuisa.com at 5.7 s5.7 s
  7. analuisa.com at 6.6 s6.6 s
  8. analuisa.com at 7.5 s7.5 s

Speed

7 to fix44
  • Reduce unused JavaScript

    3.1 s · 710 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 207 KiB

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 4.9 s

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

  • Improve image delivery

    600 ms · 231 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and TikTok and others), adding 1.1 MB and 606 ms of main-thread time.

  • Google Tag Manager adds 210 ms

    210 ms

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 27 KiB

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

  • Reduce unused CSS

    34 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 85 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 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.

  • Largest Contentful Paint: 17.2 s

    17.2 s

    Your largest element takes 17.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Personalized Collection”.

  • Time to Interactive: 19.0 s

    19.0 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Total Blocking Time: 625 ms

    625 ms

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

  • Real-user INP: 262 ms

    262 ms

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

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

    +17%

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

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

    +18%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 499 ms

    499 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.4 MB in 143 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 143 requests on a phone: scripts 1.8 MB (35), other files 1.1 MB (77) and images 357 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    HP_M__2_.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).

  • About 1.0 g of CO₂ per visit

    0.96 g

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

2 checks passed
  • 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

9 to fixGoogle 7988
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • 11 text elements with low contrast

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

  • 6 tap targets too small

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

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

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

  • 2 form fields without a label

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

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

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10081
  • No H1 headline

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

  • Meta description is long (257 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.analuisa.com/sitemap/sitemap-0.xml, so Google discovers your pages only by following links.

  • 66 internal links, 5 external

    The homepage links to 66 pages on analuisa.com and 5 external pages.

5 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Ana Luisa | Your Jewelry Uniform”.

  • Canonical URL set

    The canonical URL is https://www.analuisa.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.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    51%

    The HTML your server sends has 256 of the 504 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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.

  • Organization data: 6 of 6 facts

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

Other pages

6 to fix62
  • 1 page without a title

    https://www.analuisa.com/pages/retail has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.analuisa.com/pages/our-journey and https://www.analuisa.com/our-story all use the title “Our Story | Ana Luisa | Your Jewelry Uniform”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.analuisa.com/pages/retail has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.analuisa.com/pages/our-journey and https://www.analuisa.com/our-story use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.analuisa.com/pages/our-journey, whose canonical is /*. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.analuisa.com/pages/our-journey, https://www.analuisa.com/welcome-to-ana-luisa-luxe, https://www.analuisa.com/pages/retail and https://www.analuisa.com/our-story have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9671
  • 5 broken images

    5 images failed to load on a phone, for example https://brxcdn.com/eng-app-storage/c62d1b48-4f71-11eb-a767-16dcb0591634/media/original/4bb1dc9a-cf5c-11ef-a115-2e0ecbcc1c4f.

  • 16 small tap targets

    16 of 71 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 “Minified React error #425; visit https://reactjs.org/docs/error-decoder.html?invariant=425 for the full message or use …”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • Thin social proof

    Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • 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 504 words of copy

    The homepage carries about 504 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Log in/ Sign up” and “Shop By”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Log in/ Sign up”, “Shop By” and “Track My Order”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 mores (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

  • 42 cookies set on arrival

    42

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

  • 49 other companies contacted

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

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) loads with the page.

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

Upkeep, stack and company

Stack

Framework
Gatsby
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on analuisa.com, including 14 speed issues, 3 SEO issues and 2 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