Website review, no card needed

academia.tv logo

academia.tv website review

Visit site (opens in a new tab)Reviewed 2 November 202649 issues · 79 checks

This review found 49 issues worth fixing on academia.tv, 21 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.

  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
6.7 s4.5 sMay 16Oct 314.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.9 s
May 23, 20264.9 s
May 30, 20265.0 s
Jun 6, 20265.1 s
Jun 13, 20265.2 s
Jun 20, 20265.3 s
Jun 27, 20265.4 s
Jul 4, 20265.4 s
Jul 11, 20265.5 s
Jul 18, 20265.5 s
Jul 25, 20265.8 s
Aug 1, 20266.1 s
Aug 8, 20266.3 s
Aug 15, 20266.4 s
Aug 22, 20266.4 s
Aug 29, 20266.4 s
Sep 5, 20266.2 s
Sep 12, 20265.9 s
Sep 19, 20265.8 s
Sep 26, 20265.6 s
Oct 3, 20265.6 s
Oct 10, 20265.5 s
Oct 17, 20265.3 s
Oct 24, 20265.1 s
Oct 31, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
414 ms252 msMay 16Oct 31395 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026277 ms
May 23, 2026271 ms
May 30, 2026271 ms
Jun 6, 2026278 ms
Jun 13, 2026286 ms
Jun 20, 2026290 ms
Jun 27, 2026299 ms
Jul 4, 2026303 ms
Jul 11, 2026305 ms
Jul 18, 2026306 ms
Jul 25, 2026295 ms
Aug 1, 2026290 ms
Aug 8, 2026288 ms
Aug 15, 2026286 ms
Aug 22, 2026288 ms
Aug 29, 2026287 ms
Sep 5, 2026307 ms
Sep 12, 2026324 ms
Sep 19, 2026332 ms
Sep 26, 2026340 ms
Oct 3, 2026338 ms
Oct 10, 2026341 ms
Oct 17, 2026360 ms
Oct 24, 2026377 ms
Oct 31, 2026395 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 academia.tv (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. academia.tv at 1.0 s1.0 s
  2. academia.tv at 2.0 s2.0 s
  3. academia.tv at 3.1 s3.1 s
  4. academia.tv at 4.1 s4.1 s
  5. academia.tv at 5.1 s5.1 s
  6. academia.tv at 6.1 s6.1 s
  7. academia.tv at 7.2 s7.2 s
  8. academia.tv at 8.2 s8.2 s

Speed

9 to fix29
  • Use efficient cache lifetimes

    4.2 s · 2.8 MB

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

  • Reduce unused JavaScript

    3.1 s · 800 KiB

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

  • Render-blocking requests

    2.1 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (iubenda, Stripe and Google Tag Manager and others), adding 772 KiB and 574 ms of main-thread time.

  • Main-thread work: 3.0 s

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

  • 11 long tasks on the main thread

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

  • Stripe adds 175 ms

    175 ms

    Stripe costs a phone 175 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.

  • 1,567 HTML elements

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

  • Reduce unused CSS

    58 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

14 to fix0
  • 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 LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 3.5 s

    3.5 s

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

  • Largest Contentful Paint: 13.0 s

    13.0 s

    Your largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Online cooking courses to cook at home like a chef Learn st…”.

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Total Blocking Time: 906 ms

    906 ms

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

  • Real-user INP: 395 ms

    395 ms

    Real visitors wait 395 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.19

    0.19

    For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 41% slower for real visitors

    +41%

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

  • Real-user TTFB: 894 ms

    894 ms

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

  • Cumulative Layout Shift: 0.238

    0.238

    The layout shifts by 0.238 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 15 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

Images and page weight

5 to fix43
  • Page weight: 4.3 MB in 98 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 98 requests on a phone: scripts 2.4 MB (28), images 1.8 MB (26) and fonts 43 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

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

  • An image on the first screen is lazy-loaded

    masterclass_trailer_img_cov-1790233714.716.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 6 images below the first screen load straight away

    6 images further down the page (973 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 2 images far larger than shown

    87 KiB

    2 images are downloaded at several times the size a phone draws them, for example mobile-en.3d1aabce.jpg at 1,498 px wide, shown at 358 px. Resized copies would save about 87 KiB.

  • About 1.2 g of CO₂ per visit

    1.22 g

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

Accessibility

9 to fixGoogle 8588
  • Images must have alternative text (9 elements)

    Images must have alternative text: 9 elements on the page fail this check, rated critical by axe-core.

  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 5 text elements with low contrast

    5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (4 elements)

    Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (102 elements)

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

  • Heading levels should only increase by one (9 elements)

    Heading levels should only increase by one: 9 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 9281
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (22 characters)

    Your title is only 22 characters: “Online cooking courses”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

6 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Discover now the best online cooking courses with starred chefs, both for professionals and beginners. Get your certifi…”.

  • Canonical URL set

    The canonical URL is https://www.academia.tv/en.

  • Structured data in place

    Structured data found: FAQPage, ItemList, Offer, Organization and VideoObject.

  • 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://sitemap.academia.tv/sitemap-it.xml.

AI search readiness

1 to fix75
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,131 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • No llms.txt

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

  • Organization data: 4 of 6 facts

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=343003317&tm=gtm002&Ver=2&mid=5ed3f8aa-82ff-4173-b7cf-9829d98e9441&bo=6&gtm_tag_source=1&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=Online%20cooking%20courses%.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

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

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

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Subscribe” and “Start now”.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 academia.tv, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
CloudFront

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on academia.tv, including 23 speed issues, 3 SEO issues and 6 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