Website review, no card needed

francoleone.com logo

francoleone.com website review

Visit site (opens in a new tab)Reviewed 22 October 202638 issues · 84 checks

This review found 38 issues worth fixing on francoleone.com, 13 of them high impact, across 84 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
1.5 s966 msMay 9Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
82 ms67 msMay 16Oct 1777 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202672 ms
May 23, 202679 ms
May 30, 202680 ms
Jul 18, 202677 ms
Aug 8, 202673 ms
Aug 15, 202671 ms
Aug 22, 202674 ms
Sep 12, 202672 ms
Sep 19, 202669 ms
Sep 26, 202670 ms
Oct 3, 202674 ms
Oct 10, 202676 ms
Oct 17, 202677 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 francoleone.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. francoleone.com at 0.9 s0.9 s
  2. francoleone.com at 1.8 s1.8 s
  3. francoleone.com at 2.6 s2.6 s
  4. francoleone.com at 3.5 s3.5 s
  5. francoleone.com at 4.4 s4.4 s
  6. francoleone.com at 5.3 s5.3 s
  7. francoleone.com at 6.1 s6.1 s
  8. francoleone.com at 7.0 s7.0 s

Speed

12 to fix58
  • Reduce unused JavaScript

    1.4 s · 305 KiB

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    973 KiB

    13 images could be 973 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    600 ms · 139 KiB

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

  • Reduce unused CSS

    510 ms · 106 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (razorpay.com, vitals.app and Shopify and others), adding 1.6 MB and 374 ms of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Legacy JavaScript

    300 ms · 29 KiB

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

  • Main-thread work: 2.9 s

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

  • razorpay.com adds 172 ms

    172 ms

    razorpay.com costs a phone 172 ms of main-thread work and 879 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.

  • 1,595 HTML elements

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

  • Shopify adds 50 ms

    50 ms

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

  • 4 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 99 but mobile only 58. 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: 9 ms

    9 ms

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

Core Web Vitals

6 to fix100
  • 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: 13.9 s

    13.9 s

    Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Crafted For Modern Movement.”.

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Time to Interactive: 15.7 s

    15.7 s

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

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

6 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 76 ms

    76 ms

    Real visitors wait 76 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.

  • Total Blocking Time: 84 ms

    84 ms

    Scripts block the page for only 84 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

2 to fix50
  • Page weight: 5.3 MB in 481 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 481 requests on a phone: images 2.4 MB (71), other files 1.3 MB (195) and scripts 1.2 MB (178). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    509 KiB

    4 images are downloaded at several times the size a phone draws them, for example creaive1.png at 1,254 px wide, shown at 129 px. Resized copies would save about 509 KiB.

  • 1 image in older formats

    1 image (181 KiB) is 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.

  • About 1.5 g of CO₂ per visit

    1.50 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

6 to fixGoogle 8791
  • 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.

  • 4 tap targets too small

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

  • 5 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), 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. (12 elements).

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 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

2 to fixGoogle 9288
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Premium Leather Shoes for Men | Loafers, Monks, Boots – Franco Leone”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Franco Leone” and “Crafted For Modern Movement.”). One clear main headline is easier for people and search engines.

  • 179 internal links, 1 external

    The homepage links to 179 pages on francoleone.com and 1 external page.

6 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Shop premium leather shoes for men – loafers, lace-ups, monk straps, boots and slippers. Crafted for comfort and everyd…”.

  • Canonical URL set

    The canonical URL is https://francoleone.com/.

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (912 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix86
  • 3 pages share a title

    https://francoleone.com/products/franco-leone-men-lace-up-flb26l502black, https://francoleone.com/products/franco-leone-men-lace-up-fll264212black and https://francoleone.com/products/franco-leone-men-lace-up-flt269801black all use the title “Milano Lace-Up – Black – Franco Leone”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://francoleone.com/products/franco-leone-men-lace-up-flb26l502brown and https://francoleone.com/products/franco-leone-men-lace-up-flb26l502black use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://francoleone.com/collections/lace-up, https://francoleone.com/collections/slip-on, https://francoleone.com/collections/slippers, https://francoleone.com/collections/monk, https://francoleone.com/collections/loafers and https://francoleone.com/collections/boots and 1 other 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 72 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    19 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 530 words of copy

    The homepage carries about 530 words of visible text.

2 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Start with image 1”, “Start with image 2” and “Start with image 3”.

  • 2 short forms

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

Privacy and tracking

  • 8 cookies set on arrival

    8

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

  • 17 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on francoleone.com, including 18 speed issues, 2 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