Website review, no card needed

lesfleurs.com logo

lesfleurs.com website review

Visit site (opens in a new tab)Reviewed 18 October 202642 issues · 95 checks

This review found 42 issues worth fixing on lesfleurs.com, 18 of them high impact, across 95 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.9 s2.0 sApr 25Oct 102.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.4 s
May 2, 20262.6 s
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.5 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
107 ms83 msApr 25Oct 1093 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202696 ms
May 2, 202694 ms
May 9, 202694 ms
May 16, 202697 ms
May 23, 202697 ms
May 30, 202694 ms
Jun 6, 202688 ms
Jun 13, 202688 ms
Jun 20, 202686 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202691 ms
Jul 18, 202696 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202687 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026100 ms
Sep 5, 202697 ms
Sep 12, 202688 ms
Sep 19, 202687 ms
Sep 26, 202690 ms
Oct 3, 202693 ms
Oct 10, 202693 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 lesfleurs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lesfleurs.com at 1.1 s1.1 s
  2. lesfleurs.com at 2.3 s2.3 s
  3. lesfleurs.com at 3.4 s3.4 s
  4. lesfleurs.com at 4.6 s4.6 s
  5. lesfleurs.com at 5.7 s5.7 s
  6. lesfleurs.com at 6.8 s6.8 s
  7. lesfleurs.com at 8.0 s8.0 s
  8. lesfleurs.com at 9.1 s9.1 s

Speed

14 to fix4
  • Reduce unused JavaScript

    6.5 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

  • Render-blocking requests

    6.9 s

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

  • Improve image delivery

    1.8 s · 1.2 MB

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

  • Squarespace adds 1.2 s

    1.2 s

    Squarespace costs a phone 1.2 s of main-thread work and 2.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 4

    4/100

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

  • Main-thread work: 8.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Squarespace, YouTube and Google CDN and others), adding 4.8 MB and 3.1 s of main-thread time.

  • Reduce unused CSS

    570 ms · 260 KiB

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

  • YouTube adds 694 ms

    694 ms

    YouTube costs a phone 694 ms of main-thread work and 961 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.

  • Google CDN adds 637 ms

    637 ms

    Google CDN costs a phone 637 ms of main-thread work and 733 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.

  • 20 long tasks on the main thread

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

  • Duplicated JavaScript

    300 ms · 49 KiB

    49 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 289 ms

    289 ms

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

  • 2,169 HTML elements

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

  • Legacy JavaScript

    150 ms · 52 KiB

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

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    11 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 30 but mobile only 4. 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.

  • 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: 38 ms

    38 ms

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

Core Web Vitals

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

  • First Contentful Paint: 13.5 s

    13.5 s

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

  • Largest Contentful Paint: 36.8 s

    36.8 s

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

  • Speed Index: 21.6 s

    21.6 s

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

  • Time to Interactive: 44.6 s

    44.6 s

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

  • Cumulative Layout Shift: 0.972

    0.972

    The layout shifts by 0.972 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.8 s

    1.8 s

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

  • Real-user TTFB: 748 ms

    748 ms

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

Images and page weight

3 to fix50
  • Page weight: 9.4 MB in 200 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 200 requests on a phone: images 4.9 MB (61), scripts 3.3 MB (82) and other files 507 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 5 images far larger than shown

    333 KiB

    5 images are downloaded at several times the size a phone draws them, for example about-menu-image-shop-exterior.jpg at 800 px wide, shown at 200 px. Resized copies would save about 333 KiB.

  • 3 images below the first screen load straight away

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

  • About 2.7 g of CO₂ per visit

    2.68 g

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

Accessibility

8 to fixGoogle 7889
  • 2 buttons without a name

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

  • 5 text elements with low contrast

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

  • 18 images without alt text

    18 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 81 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 (1 element)

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

  • 15 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3), 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
  • 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. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 8594
  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5992e51a6a49634687e…”.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 293 internal links, 11 external

    The homepage links to 293 pages on lesfleurs.com and 11 external pages.

7 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Les Fleurs Andover florist, same day flower delivery near Andover MA. French-inspired vintage home decor and garden sto…”.

  • One H1 headline

    Your main headline reads: “Floral · Home · Garden”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Andover Florist | Flower Delivery by Les Fleurs”.

  • Canonical URL set

    The canonical URL is https://lesfleurs.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://lesfleurs.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

3 to fix86
  • 3 pages share a title

    https://lesfleurs.com/andover-florist-flower-delivery-les-fleurs, https://lesfleurs.com/fresh-floral and https://lesfleurs.com/floral all use the title “Les Fleurs Andover Florist | Same Day Flower Delivery Andover MA”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://lesfleurs.com/andover-florist-flower-delivery-les-fleurs, https://lesfleurs.com/fresh-floral and https://lesfleurs.com/floral use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://lesfleurs.com/andover-florist-flower-delivery-les-fleurs, whose canonical is https://lesfleurs.com/fresh-floral. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    128 of 132 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 521 words of visible text.

9 checks passed
  • Clear next step on the first screen

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

  • 43 calls to action

    The homepage has 43 calls to action, for example “Shop”, “Book” and “shop”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 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.

  • 22 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Squarespace
Framework
jQuery
Analytics
Google Analytics

Company

Founded
1989
Headquarters
Andover

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on lesfleurs.com, including 22 speed issues and 2 SEO issues. 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