studiocanal.com website review

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

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

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

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

About 79 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.

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

8 third-party services load with your homepage (canalplus.com, JSDelivr CDN and Cloudflare CDN and others), adding 2.0 MB and 54 ms of main-thread time.

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

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

Azure Web Services costs a phone 0 ms of main-thread work and 1.8 MB 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.

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

10 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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 visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INK View title”.

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

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

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

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

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

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

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

Your homepage downloads 7.8 MB in 91 requests on a phone: images 6.6 MB (68), scripts 973 KiB (7) and stylesheets 99 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 11 characters: “STUDIOCANAL”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 10 <h1> headlines (“”, “” and “INK”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 165 pages on studiocanal.com and 33 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.studiocanal.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.studiocanal.com/movies, https://www.studiocanal.com/tv-series, https://www.studiocanal.com/news, https://www.studiocanal.com/about-studiocanal, https://www.studiocanal.com/company-history and https://www.studiocanal.com/management and 9 others have no <title>, so Google invents the link text in results.

https://www.studiocanal.com/movies, https://www.studiocanal.com/tv-series, https://www.studiocanal.com/news, https://www.studiocanal.com/about-studiocanal, https://www.studiocanal.com/company-history and https://www.studiocanal.com/management and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.studiocanal.com/movies, https://www.studiocanal.com/tv-series, https://www.studiocanal.com/news, https://www.studiocanal.com/about-studiocanal, https://www.studiocanal.com/company-history and https://www.studiocanal.com/management and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 138 found) and read each the way a search engine does.

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 643 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

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