Website review, no card needed
basquercyrugby.fr website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 79 checks
This review found 43 issues worth fixing on basquercyrugby.fr, 16 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
64DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.7 s
1.5 s
2.2 s
2.9 s
3.7 s
4.4 s
5.1 s
5.9 s
Speed
Use efficient cache lifetimes
46.0 s · 9.6 MB38 files are served with short cache lifetimes, so returning visitors download them again (9.6 MB).
Improve image delivery
45.3 s · 9.0 MB5 images could be 9.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 45.3 s faster on a phone.
Reduce unused JavaScript
5.1 s · 853 KiBAbout 853 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Mobile performance score: 51
51/100Your mobile performance score is 51. 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 (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 1.8 MB and 810 ms of main-thread time.
Render-blocking requests
850 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused CSS
450 ms · 174 KiBAbout 174 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
YouTube adds 509 ms
509 msYouTube costs a phone 509 ms of main-thread work and 1,002 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Google CDN adds 229 ms
229 msGoogle CDN costs a phone 229 ms of main-thread work and 452 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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: 109 ms
109 msYour server sent the HTML in 109 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 73.2 s
73.2 sYour largest element takes 73.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 73.5 s
73.5 sThe page becomes fully interactive after 73.5 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 563 ms
563 msScripts block taps and scrolling for 563 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 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 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 13.8 MB in 103 requests
13.8 MBYour homepage downloads 13.8 MB in 103 requests on a phone: images 11.0 MB (24), scripts 2.0 MB (47) and stylesheets 415 KiB (11). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Capture-d’écran-2020-08-27-à-15.35.57.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.4 MB3 images are downloaded at several times the size a phone draws them, for example Capture-d’écran-2020-08-27-à-15.35.57.png at 1,820 px wide, shown at 312 px. Resized copies would save about 1.4 MB.
3 images in older formats
3 images (1.9 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.
3 images below the first screen load straight away
3 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.90 g of CO₂e: 468.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (26 characters)
Your title is only 26 characters: “Accueil - Bas Quercy Rugby”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (43 characters)
Your meta description is only 43 characters: “Page d'accueil du site de Bas Quercy Rugby.”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
46 internal links, 0 external
The homepage links to 46 pages on basquercyrugby.fr and 0 external pages.
4 checks passed
Canonical URL set
The canonical URL is http://basquercyrugby.fr/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://basquercyrugby.fr/sitemap_index.xml.
AI search readiness
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://basquercyrugby.fr/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 (479 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://basquercyrugby.fr/fetes-des-associations and https://basquercyrugby.fr/la-nouvelle-saison-va-commencer are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages without a meta description
https://basquercyrugby.fr/administratif, https://basquercyrugby.fr/equipes, https://basquercyrugby.fr/u-6, https://basquercyrugby.fr/u-8, https://basquercyrugby.fr/u-10 and https://basquercyrugby.fr/u-12 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://basquercyrugby.fr/author/communication and https://basquercyrugby.fr/category/non-classe have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://basquercyrugby.fr/administratif, https://basquercyrugby.fr/equipes, https://basquercyrugby.fr/u-6, https://basquercyrugby.fr/u-8, https://basquercyrugby.fr/u-10 and https://basquercyrugby.fr/u-12 and 3 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
4 pages slow to respond
https://basquercyrugby.fr/la-boutique, https://basquercyrugby.fr/blog, https://basquercyrugby.fr/author/communication and https://basquercyrugby.fr/category/non-classe took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
28 small tap targets
28 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 third-party cookies
6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were 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 (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 459 words of copy
The homepage carries about 459 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Meta Pixel (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 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.
16 other companies contacted
Loading the homepage contacts 16 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 basquercyrugby.fr, 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
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on basquercyrugby.fr, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.