Website review, no card needed
marineland.fr website review
Visit site (opens in a new tab)Reviewed 24 October 202647 issues · 89 checks
This review found 47 issues worth fixing on marineland.fr, 17 of them high impact, across 89 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 138 ms |
| May 9, 2026 | 141 ms |
| May 16, 2026 | 141 ms |
| May 23, 2026 | 152 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 157 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 152 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 144 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 142 ms |
| Sep 12, 2026 | 141 ms |
| Sep 19, 2026 | 140 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 148 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Use efficient cache lifetimes
1.9 s · 1.9 MB26 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Reduce unused JavaScript
2.3 s · 884 KiBAbout 884 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
2.6 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
1.1 MB7 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Optanon and Google CDN and others), adding 1.4 MB and 858 ms of main-thread time.
Google Tag Manager adds 578 ms
578 msGoogle Tag Manager costs a phone 578 ms of main-thread work and 673 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
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
Reduce unused CSS
300 ms · 56 KiBAbout 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 107 ms
107 msGoogle CDN costs a phone 107 ms of main-thread work and 349 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.
Minify JavaScript
150 ms · 106 KiB106 KiB could be saved by minifying JavaScript.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Document request latency
37 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 910 ms of it running JavaScript. That is comfortably low.
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Marineland d'Antibes - le plus grand zoo marin d'Europe”.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Speed Index: 12.7 s
12.7 sVisually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.255
0.255The layout shifts by 0.255 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 419 ms
419 msScripts block taps and scrolling for 419 ms in total while the page loads. Good is under 200 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 138 ms to 148 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 668 ms
668 msReal visitors wait 668 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.1 MB in 90 requests
4.1 MBYour homepage downloads 4.1 MB in 90 requests on a phone: scripts 1.9 MB (34), images 1.6 MB (15) and fonts 334 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
EAAM.png weighs 503 KiB. On a phone connection a single image that size takes seconds.
3 images far larger than shown
915 KiB3 images are downloaded at several times the size a phone draws them, for example EAAM.png at 2,400 px wide, shown at 73 px. Resized copies would save about 915 KiB.
8 images in older formats
8 images (1.5 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.
4 images below the first screen load straight away
4 images further down the page (976 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 139.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Users should be able to zoom and scale the text up to 500% (1 element)
Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and 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. (1 element).
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (68 characters)
Your meta description is only 68 characters: “Plongez dans le zoo marin Marineland pour une aventure sous-marine !”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (AmusementPark) but with 1 problem, for example “AmusementPark: image is not an absolute URL ("https://www.marineland.fr/content/dam/mar/fr/images/logos/Marineland_logo_110x…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
18 internal links, 2 external
The homepage links to 18 pages on marineland.fr and 2 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Marineland”.
Title: 54 characters
Your title is a healthy 54 characters: “Marineland d'Antibes, le plus grand zoo marin d'Europe”.
Canonical URL set
The canonical URL is https://www.marineland.fr/.
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.marineland.fr/sitemap.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://www.marineland.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 (470 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages point its canonical at the homepage
https://www.marineland.fr/rechercher, https://www.marineland.fr/home, https://www.marineland.fr/content/mar/fr.html and https://www.marineland.fr/informations-de-base-sur-la-protection-des-donnees-de-recuperation-de-panier-marineland declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
6 linked pages hidden from search
https://www.marineland.fr/presse/communique-de-presse, https://www.marineland.fr/politique-de-confidentialite, https://www.marineland.fr/mentions-legales, https://www.marineland.fr/reglement-interieur, https://www.marineland.fr/conditions-generales-de-vente and https://www.marineland.fr/politique-de-cookies are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages share a title
/, https://www.marineland.fr/rechercher, https://www.marineland.fr/home, https://www.marineland.fr/content/mar/fr.html, https://www.marineland.fr/home-backup and https://www.marineland.fr/informations-de-base-sur-la-protection-des-donnees-de-recuperation-de-panier-marineland all use the title “Marineland d'Antibes, le plus grand zoo marin d'Europe”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.marineland.fr/presse/communique-de-presse, https://www.marineland.fr/politique-de-confidentialite, https://www.marineland.fr/mentions-legales, https://www.marineland.fr/reglement-interieur, https://www.marineland.fr/conditions-generales-de-vente and https://www.marineland.fr/politique-de-cookies have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://www.marineland.fr/rechercher, https://www.marineland.fr/home, https://www.marineland.fr/content/mar/fr.html, https://www.marineland.fr/home-backup and https://www.marineland.fr/informations-de-base-sur-la-protection-des-donnees-de-recuperation-de-panier-marineland use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
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
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.
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.
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 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 444 words of copy
The homepage carries about 444 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Apply”.
3 short forms
3 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 marineland.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Founded
- 1970
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on marineland.fr, including 22 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.