Website review, no card needed

sara-lisa.com logo

sara-lisa.com website review

Visit site (opens in a new tab)Reviewed 21 November 202626 issues · 67 checks

This review found 26 issues worth fixing on sara-lisa.com, 11 of them high impact, across 67 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

Full-page screenshot of sara-lisa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sara-lisa.com at 0.8 s0.8 s
  2. sara-lisa.com at 1.5 s1.5 s
  3. sara-lisa.com at 2.3 s2.3 s
  4. sara-lisa.com at 3.1 s3.1 s
  5. sara-lisa.com at 3.8 s3.8 s
  6. sara-lisa.com at 4.6 s4.6 s
  7. sara-lisa.com at 5.4 s5.4 s
  8. sara-lisa.com at 6.2 s6.2 s

Speed

2 to fix83
  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 83

    83/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Pinterest and JSDelivr CDN and others), adding 263 KiB and 115 ms of main-thread time.

  • Document request latency

    138 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce unused JavaScript

    98 KiB

    About 98 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    28 KiB

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

  • Reduce unused CSS

    12 KiB

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

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

2 checks passed
  • Main-thread work: 0.3 s

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

  • Server response: 217 ms

    217 ms

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

Core Web Vitals

4 to fix94
  • Speed Index: 8.9 s

    8.9 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Time to Interactive: 5.0 s

    5.0 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Délai de fabrication : 5 JOURS OUVRÉS (hors doudou Bola)”. Most of its time is element render delay (5.3 s).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.067

    0.067

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

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.14 g

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

4 checks passed
  • Page weight: 511 KiB in 90 requests

    511 KiB

    Your homepage downloads 511 KiB in 90 requests on a phone: scripts 275 KiB (53), HTML 207 KiB (1) and stylesheets 19 KiB (20). That is a lean page.

  • 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

10 to fixGoogle 8387
  • 59 tap targets too small

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

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

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate 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.

2 checks passed
  • Every image has alt text

    All 33 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 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10082
  • No H1 headline

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

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at sara-lisa.com/robots.txt, the first file search crawlers ask for.

  • 84 internal links, 4 external

    The homepage links to 84 pages on sara-lisa.com and 4 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “SARA LISA Création De Bijoux Et Accessoires. Boutique spécialisée en Bola de grossesse. Créations uniques et personnali…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Sara Lisa | Bola De Grossesse Et Bijoux Personnalisés”.

  • Canonical URL set

    The canonical URL is https://sara-lisa.com/.

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
  • No llms.txt

    There is no https://sara-lisa.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.

3 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://sara-lisa.com/suivi-de-commande, https://sara-lisa.com/shop, https://sara-lisa.com/product-category/nos-bolas, https://sara-lisa.com/product-category/nos-bolas/nos-bolas-signature, https://sara-lisa.com/product-category/nos-bolas/nos-intemporels and https://sara-lisa.com/product-category/nos-bolas/nos-mini-bola and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

4 to fixGoogle 9663
  • 6 broken images

    6 images failed to load on a phone, for example https://sara-lisa.com/wp-content/uploads/2021/03/sara-lisa-logo-entete.jpg.

  • 29 small tap targets

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

  • Scrolls sideways on phones

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 457 words of copy

    The homepage carries about 457 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Service Client : [email protected]”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Service Client : [email protected]”.

  • 5 short forms

    5 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 sara-lisa.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
DigitalOcean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on sara-lisa.com, including 6 speed issues, 3 SEO issues and 1 conversion gap. 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