Website review, no card needed

jackiesmith.com.br logo

jackiesmith.com.br website review

Visit site (opens in a new tab)Reviewed 10 November 202646 issues · 89 checks

This review found 46 issues worth fixing on jackiesmith.com.br, 9 of them high impact, across 89 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
1.8 s1.6 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
192 ms124 msMay 23Nov 7164 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026132 ms
May 30, 2026133 ms
Jun 6, 2026141 ms
Jun 13, 2026149 ms
Jun 20, 2026151 ms
Jun 27, 2026154 ms
Jul 4, 2026153 ms
Jul 11, 2026155 ms
Jul 18, 2026164 ms
Jul 25, 2026172 ms
Aug 1, 2026180 ms
Aug 8, 2026184 ms
Aug 15, 2026179 ms
Aug 22, 2026175 ms
Aug 29, 2026171 ms
Sep 5, 2026168 ms
Sep 12, 2026165 ms
Sep 19, 2026164 ms
Sep 26, 2026164 ms
Oct 3, 2026169 ms
Oct 10, 2026170 ms
Oct 17, 2026172 ms
Oct 24, 2026175 ms
Oct 31, 2026171 ms
Nov 7, 2026164 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 jackiesmith.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jackiesmith.com.br at 0.8 s0.8 s
  2. jackiesmith.com.br at 1.6 s1.6 s
  3. jackiesmith.com.br at 2.4 s2.4 s
  4. jackiesmith.com.br at 3.2 s3.2 s
  5. jackiesmith.com.br at 4.0 s4.0 s
  6. jackiesmith.com.br at 4.8 s4.8 s
  7. jackiesmith.com.br at 5.6 s5.6 s
  8. jackiesmith.com.br at 6.4 s6.4 s

Speed

16 to fix58
  • Render-blocking requests

    2.5 s

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

  • Main-thread work: 6.2 s

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

  • 4,586 HTML elements

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

  • Improve image delivery

    800 ms · 1.3 MB

    24 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Facebook and minmaxify.com and others), adding 2.2 MB and 1.7 s of main-thread time.

  • Mobile performance score: 58

    58/100

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

  • Use efficient cache lifetimes

    300 ms · 506 KiB

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

  • Shopify adds 632 ms

    632 ms

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

  • Reduce unused JavaScript

    250 ms · 440 KiB

    About 440 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 250 ms faster on a phone.

  • Font display

    600 ms

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

  • Legacy JavaScript

    400 ms · 75 KiB

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

  • Reduce unused CSS

    300 ms · 103 KiB

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

  • Facebook adds 348 ms

    348 ms

    Facebook costs a phone 348 ms of main-thread work and 283 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 284 ms. During a long task the page ignores taps.

  • minmaxify.com adds 269 ms

    269 ms

    minmaxify.com costs a phone 269 ms of main-thread work and 9 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.

  • Klaviyo adds 195 ms

    195 ms

    Klaviyo costs a phone 195 ms of main-thread work and 307 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.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 18 ms

    18 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 18.6 s

    18.6 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

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

  • Speed Index: 6.9 s

    6.9 s

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

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

    +26%

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

  • Total Blocking Time: 382 ms

    382 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest content (LCP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 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.4 s

    2.4 s

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

  • Real-user INP: 163 ms

    163 ms

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

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

    1.7 s

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

  • Real-user TTFB: 505 ms

    505 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix69
  • Page weight: 4.7 MB in 274 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 274 requests on a phone: images 1.9 MB (27), scripts 1.6 MB (111) and other files 904 KiB (110). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

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

  • 8 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.34 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 161.4 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

6 to fixGoogle 9294
  • 15 tap targets too small

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

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

    All page content should be contained by landmarks: 4 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.

  • 10 links without text

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

  • 4 form fields without a label

    4 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 (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.

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

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

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

5 to fixGoogle 8580
  • Title is short (12 characters)

    Your title is only 12 characters: “Jackie Smith”. 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.

  • Meta description is long (205 characters)

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 71 internal links, 14 external

    The homepage links to 71 pages on jackiesmith.com.br and 14 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Jackie Smith”.

  • Canonical URL set

    The canonical URL is https://jackiesmith.com.ar/.

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

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix83
  • 9 pages share 3 titles

    https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc03n98, https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc99u98 and https://jackiesmith.com.ar/collections/home-6/products/cp02457rfa01n98 all use the title “Grace – Jackie Smith”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 links to non-canonical URLs

    Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc03n98, whose canonical is https://jackiesmith.com.ar/products/cp02457rfc03n98. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    https://jackiesmith.com.ar/collections/new-arrivals, https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc03n98, https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc99u98, https://jackiesmith.com.ar/collections/home-6/products/cp02457rfa01n98, https://jackiesmith.com.ar/collections/home-4/products/cp00194gsa87d99 and https://jackiesmith.com.ar/collections/home-4/products/002d317gaa87x and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://jackiesmith.com.ar/collections/home-6/products/cp02457rfc99u98, https://jackiesmith.com.ar/collections/home-6/products/cp02457rfa01n98, https://jackiesmith.com.ar/collections/home-4/products/cp00194gsa87d99, https://jackiesmith.com.ar/collections/home-4/products/002d317gaa87x, https://jackiesmith.com.ar/collections/home-4/products/cp00200gsa87d99 and https://jackiesmith.com.ar/collections/home-5/products/ld00130ncc99198 and 7 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 47 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • Only about 210 words

    The homepage has only about 210 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
  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP OUR INSTAGRAM”, “SHOP” and “icon-email sign up!”.

  • 7 short forms

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 28 cookies set on arrival

    28

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

  • 41 other companies contacted

    Loading the homepage contacts 41 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 jackiesmith.com.br, 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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Minmaxify Order Limits · Okendo · Buddha Mega Menu Navigation · Cozy Country Redirect · Beast Currency Converter · Delm · Klaviyo Email Marketing Sms · Nosto · Social Login · Powerful Form Builder · Langify · Countdown Timer · Foursixty Shopify App · cloudfront.net · Swym Wishlist Plus

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on jackiesmith.com.br, including 22 speed issues, 5 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