Website review, no card needed

lepetitballon.pt logo

lepetitballon.pt website review

Visit site (opens in a new tab)Reviewed 11 November 202644 issues · 85 checks

This review found 44 issues worth fixing on lepetitballon.pt, 13 of them high impact, across 85 checks. The most urgent: main-thread work: 6.7 s. 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 lepetitballon.pt (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lepetitballon.pt at 2.3 s2.3 s
  2. lepetitballon.pt at 4.6 s4.6 s
  3. lepetitballon.pt at 6.9 s6.9 s
  4. lepetitballon.pt at 9.2 s9.2 s
  5. lepetitballon.pt at 11.6 s11.6 s
  6. lepetitballon.pt at 13.9 s13.9 s
  7. lepetitballon.pt at 16.2 s16.2 s
  8. lepetitballon.pt at 18.5 s18.5 s

Speed

11 to fix61
  • Main-thread work: 6.7 s

    A phone's processor spends 6.7 s on main-thread work while loading, 3.8 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 (FontAwesome CDN, Google Tag Manager and Klaviyo and others), adding 1.9 MB and 1.9 s of main-thread time.

  • Mobile performance score: 61

    61/100

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

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    511 KiB

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

  • Use efficient cache lifetimes

    501 KiB

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

  • FontAwesome CDN adds 413 ms

    413 ms

    FontAwesome CDN costs a phone 413 ms of main-thread work and 144 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 Tag Manager adds 358 ms

    358 ms

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

  • Improve image delivery

    386 KiB

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

  • Klaviyo adds 313 ms

    313 ms

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

  • Shopify adds 123 ms

    123 ms

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

  • 11 long tasks on the main thread

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

  • Reduce unused CSS

    85 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    42 KiB

    Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Minify CSS

    16 KiB

    16 KiB could be saved by minifying CSS.

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

    8 ms

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

Core Web Vitals

5 to fix64
  • Speed Index: 14.9 s

    14.9 s

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

  • Time to Interactive: 22.5 s

    22.5 s

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

  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “O presente que dura Todos os meses, dois vinhos para degust…”.

  • Total Blocking Time: 407 ms

    407 ms

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

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

  • 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
  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix60
  • Page weight: 4.9 MB in 504 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 504 requests on a phone: scripts 1.9 MB (130), other files 1.6 MB (299) and images 649 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    95 KiB

    1 image is downloaded at several times the size a phone draws it, for example 2510-hero-abo-inter-BE-4-5.jpg at 800 px wide, shown at 163 px. Resized copies would save about 95 KiB.

  • About 1.4 g of CO₂ per visit

    1.38 g

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

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

Accessibility

6 to fixGoogle 9793
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

  • 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 25 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is long (93 characters)

    Your title is 93 characters, so Google will cut it off around 60: “Assinatura de caixa de vinho e cerveja | Presentes e compra de vinho online – Le Petit Ba…”.

  • Meta description is long (319 characters)

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

  • Structured data has 1 problem

    Structured data found (LiquorStore, Organization, Person and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://www.lepetitballon.com)”.

  • 34 internal links, 4 external

    The homepage links to 34 pages on lepetitballon.pt and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Les box de vins du Petit Ballon - Abonnement et cadeau”.

  • Canonical URL set

    The canonical URL is https://www.lepetitballon.pt/.

  • 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.lepetitballon.pt/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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.lepetitballon.pt/llms.txt (11 KiB, 54 links), a plain-text guide to the site for AI tools.

Other pages

7 to fix45
  • 1 linked page is broken

    Your homepage links to https://www.lepetitballon.pt/products/abonnement-biere-sans-pression, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://www.lepetitballon.pt/pages/abonnement-vin-cadeau is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share 2 titles

    https://www.lepetitballon.pt/pages/abonnement-international, https://www.lepetitballon.pt/pages/subscricao-vinho and https://www.lepetitballon.pt/pages/abonnement-vin all use the title “Caixa de vinho : assinatura de vinho para si ou para oferecer - Le Pe…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://www.lepetitballon.pt/pages/abonnement-vin-cadeau, https://www.lepetitballon.pt/pages/presente, https://www.lepetitballon.pt/pages/cadeau and https://www.lepetitballon.pt/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.lepetitballon.pt/pages/abonnement-international, https://www.lepetitballon.pt/pages/subscricao-vinho and https://www.lepetitballon.pt/pages/abonnement-vin use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.lepetitballon.pt/pages/abonnement-international, whose canonical is https://www.lepetitballon.pt/pages/subscricao-vinho. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.lepetitballon.pt/pages/abonnement-vin-cadeau has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 internal pages checked

    We fetched 8 pages linked from your homepage and read each the way a search engine does.

1 checks passed
  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=247013267&tm=gtm002&Ver=2&mid=682922b5-2998-4e3f-81a3-14b069d41d01&bo=2&gtm_tag_source=1&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Assinatura%20de%20caixa%20d.

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

    The homepage carries about 380 words of visible text.

3 checks passed
  • 5 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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 Tag Manager, Klaviyo, Meta Pixel and Microsoft Ads 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.

  • 15 cookies set on arrival

    15

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

  • 50 other companies contacted

    Loading the homepage contacts 50 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 lepetitballon.pt, 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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Kameleoon A B Testing · Judge Me Reviews · Depict Search Merchandising · Tagfly Tag Manager · Contentsquare Analytics · Klaviyo Email Marketing Sms · Product Ads By Criteo · Axeptio · magefan.top

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
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on lepetitballon.pt, including 16 speed issues, 3 SEO issues and 5 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