Website review, no card needed

lavolierecirque.com logo

lavolierecirque.com website review

Visit site (opens in a new tab)Reviewed 13 November 202633 issues · 77 checks

This review found 33 issues worth fixing on lavolierecirque.com, 14 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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
3.7 s3.0 sJun 27Aug 293.1 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20263.1 s
Jul 25, 20263.5 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
166 ms108 msJul 25Aug 29115 ms
Show as table
DateReal-visitor tap response (INP)
Jul 25, 2026159 ms
Aug 1, 2026157 ms
Aug 8, 2026159 ms
Aug 29, 2026115 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 lavolierecirque.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lavolierecirque.com at 0.6 s0.6 s
  2. lavolierecirque.com at 1.3 s1.3 s
  3. lavolierecirque.com at 1.9 s1.9 s
  4. lavolierecirque.com at 2.5 s2.5 s
  5. lavolierecirque.com at 3.1 s3.1 s
  6. lavolierecirque.com at 3.8 s3.8 s
  7. lavolierecirque.com at 4.4 s4.4 s
  8. lavolierecirque.com at 5.0 s5.0 s

Speed

8 to fix59
  • Use efficient cache lifetimes

    10.7 s · 7.6 MB

    99 files are served with short cache lifetimes, so returning visitors download them again (7.6 MB).

  • Improve image delivery

    5.3 s · 4.8 MB

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

  • Render-blocking requests

    3.8 s

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

  • Reduce unused CSS

    880 ms · 187 KiB

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

  • Mobile performance score: 59

    59/100

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

  • Font display

    950 ms

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

  • Reduce unused JavaScript

    300 ms · 210 KiB

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

  • Main-thread work: 2.3 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, buttonizer.io and Cloudflare CDN and others), adding 489 KiB and 265 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Minify JavaScript

    120 ms · 3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Minify CSS

    120 ms · 2 KiB

    2 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: 108 ms

    108 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.2 s

    3.2 s

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

  • Largest Contentful Paint: 27.5 s

    27.5 s

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

  • Time to Interactive: 28.9 s

    28.9 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Total Blocking Time: 202 ms

    202 ms

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

4 checks passed
  • Real-user INP: 164 ms

    164 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 8.9 MB in 118 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 118 requests on a phone: images 7.2 MB (14), fonts 911 KiB (9) and scripts 526 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (3.7 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.

  • About 2.5 g of CO₂ per visit

    2.53 g

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

2 checks passed
  • 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

2 to fixGoogle 9598
  • All page content should be contained by landmarks (7 elements)

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

  • 1 link without text

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

  • Headings skip levels

    Headings skip levels (h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (176 characters)

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

  • 94 internal links, 12 external

    The homepage links to 94 pages on lavolierecirque.com and 12 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “La Volière est un lieu dédié au nouveau cirque et à la danse aérienne”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “La Volière : Lieu dédié au nouveau cirque et à la danse aérienne.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, WebPage and WebSite.

  • 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://lavolierecirque.com/index.php/sitemap_index.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.

  • No llms.txt

    There is no https://lavolierecirque.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 (2,029 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix88
  • 12 pages without a meta description

    https://lavolierecirque.com/index.php/lien-aux-artistes, https://lavolierecirque.com/index.php/pratique-de-loisirs, https://lavolierecirque.com/index.php/bien-etre, https://lavolierecirque.com/index.php/enterprise, https://lavolierecirque.com/index.php/projets-transverse-aux and https://lavolierecirque.com/index.php/festival-les-rencontres-de-danse-aerienne and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://lavolierecirque.com/index.php/actualites and https://lavolierecirque.com/index.php/archives use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://lavolierecirque.com/index.php/lien-aux-artistes, https://lavolierecirque.com/index.php/pratique-de-loisirs, https://lavolierecirque.com/index.php/bien-etre, https://lavolierecirque.com/index.php/enterprise, https://lavolierecirque.com/index.php/projets-transverse-aux and https://lavolierecirque.com/index.php/actualites 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 39 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.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 10093
  • 12 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,066 words of copy

    The homepage carries about 1,066 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 lavolierecirque.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
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
OVHcloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on lavolierecirque.com, including 17 speed issues, 1 SEO issue 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