Website review, no card needed

boutiquejacques.com logo

boutiquejacques.com website review

Visit site (opens in a new tab)Reviewed 21 November 202641 issues · 89 checks

This review found 41 issues worth fixing on boutiquejacques.com, 11 of them high impact, across 89 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.5 s1.1 sMay 30Nov 142.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.2 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.4 s
Aug 8, 20261.8 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Nov 14, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
158 ms87 msMay 30Nov 14146 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 2026100 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 2026100 ms
Jul 18, 2026104 ms
Jul 25, 2026105 ms
Aug 1, 2026112 ms
Aug 8, 2026124 ms
Aug 15, 2026131 ms
Aug 22, 2026145 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026135 ms
Sep 19, 2026135 ms
Sep 26, 2026137 ms
Oct 3, 2026142 ms
Oct 10, 2026146 ms
Oct 17, 2026145 ms
Oct 24, 2026150 ms
Oct 31, 2026146 ms
Nov 7, 2026145 ms
Nov 14, 2026146 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 boutiquejacques.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boutiquejacques.com at 0.4 s0.4 s
  2. boutiquejacques.com at 0.8 s0.8 s
  3. boutiquejacques.com at 1.2 s1.2 s
  4. boutiquejacques.com at 1.5 s1.5 s
  5. boutiquejacques.com at 1.9 s1.9 s
  6. boutiquejacques.com at 2.3 s2.3 s
  7. boutiquejacques.com at 2.7 s2.7 s
  8. boutiquejacques.com at 3.1 s3.1 s

Speed

9 to fix61
  • Reduce unused JavaScript

    1.8 s · 287 KiB

    About 287 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.

  • 3,929 HTML elements

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

  • Mobile performance score: 61

    61/100

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

  • Improve image delivery

    600 ms · 382 KiB

    14 images could be 382 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.

  • Use efficient cache lifetimes

    600 ms · 92 KiB

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

  • Reduce unused CSS

    570 ms · 109 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, boostcommerce.io and omnisnippet1.com and others), adding 1.2 MB and 235 ms of main-thread time.

  • Main-thread work: 2.9 s

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

  • Shopify adds 89 ms

    89 ms

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

  • Render-blocking requests

    150 ms

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

  • 4 long tasks on the main thread

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

  • Font display

    50 ms

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

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

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 13.5 s

    13.5 s

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

  • Time to Interactive: 13.7 s

    13.7 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

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

    +52%

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

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

    +58%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 2.2 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: 2.1 s

    2.1 s

    Real visitors wait 2.1 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 FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 437 ms

    437 ms

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

  • Total Blocking Time: 117 ms

    117 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 319 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 319 requests on a phone: images 1.1 MB (114), other files 978 KiB (120) and scripts 912 KiB (61). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

8 to fixGoogle 7789
  • Hidden but focusable

    33 elements hidden from screen readers can still receive keyboard focus.

  • 33 text elements with low contrast

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

  • 2 tap targets too small

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

  • 1 image without alt text

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

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

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

  • Zoom is disabled

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

  • 4 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 9279
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Boutique Jacques™ | Men's Designer Clothing | Suits, Jackets & more”.

  • Meta description is long (277 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

  • One H1 headline

    Your <h1> is empty.

  • 376 internal links, 5 external

    The homepage links to 376 pages on boutiquejacques.com and 5 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.boutiquejacques.com/.

  • 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://www.boutiquejacques.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

6 to fix52
  • 2 linked pages are broken

    Your homepage links to https://www.boutiquejacques.com/collections/black-friday and https://www.boutiquejacques.com/fr/collections/black-friday, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://www.boutiquejacques.com/pages/pre-black-friday and https://www.boutiquejacques.com/fr/pages/pre-black-friday all use the title “Pre-Black Friday”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.boutiquejacques.com/collections/new-arrivals-boutique-jacques, https://www.boutiquejacques.com/pages/made-to-measure, https://www.boutiquejacques.com/collections/all, https://www.boutiquejacques.com/collections/bags-wallets and https://www.boutiquejacques.com/collections/belts have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.boutiquejacques.com/pages/pre-black-friday and https://www.boutiquejacques.com/fr/pages/pre-black-friday use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.boutiquejacques.com/fr/pages/gifts, whose canonical is https://www.boutiquejacques.com/fr/pages/cadeaux. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://www.boutiquejacques.com/pages/pre-black-friday, https://www.boutiquejacques.com/fr/pages/pre-black-friday, https://www.boutiquejacques.com/pages/gifts, https://www.boutiquejacques.com/fr/pages/gifts, https://www.boutiquejacques.com/collections/new-arrivals-boutique-jacques and https://www.boutiquejacques.com/pages/made-to-measure and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://www.boutiquejacques.com/pages/pre-black-friday, https://www.boutiquejacques.com/fr/pages/pre-black-friday, https://www.boutiquejacques.com/collections/new-arrivals-boutique-jacques, https://www.boutiquejacques.com/pages/made-to-measure, https://www.boutiquejacques.com/pages/services and https://www.boutiquejacques.com/blogs/jacques-style and 5 others 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 162 found) and read each the way a search engine does.

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 14 small tap targets

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

  • Deprecated browser APIs

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'transaction')”.

  • 1 low-resolution image

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

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

  • About 1,097 words of copy

    The homepage carries about 1,097 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop the event” and “Book Now”.

  • 23 calls to action

    The homepage has 23 calls to action, for example “Shop the event”, “Shop gifts” and “Book Now”.

  • 10 short forms

    10 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

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

  • Phone number on the homepage

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 2 of them by other companies (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.

  • 28 other companies contacted

    Loading the homepage contacts 28 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 boutiquejacques.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Boost Ai Search Filter · Reputon Google Reviews Widget · Koin · herokuapp.com · gtranslate.io · omnisnippet1.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
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on boutiquejacques.com, including 15 speed issues, 4 SEO issues and 3 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