Website review, no card needed

skydance.com logo

skydance.com website review

Visit site (opens in a new tab)Reviewed 17 November 202649 issues · 89 checks

This review found 49 issues worth fixing on skydance.com, 19 of them high impact, across 89 checks. The most urgent: youTube adds 8.3 s. 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.1 s1.6 sOct 10Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20262.0 s
Oct 31, 20262.1 s
Nov 7, 20262.5 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
173 ms153 msOct 10Nov 14163 ms
Show as table
DateReal-visitor tap response (INP)
Oct 10, 2026155 ms
Oct 17, 2026160 ms
Oct 24, 2026163 ms
Oct 31, 2026163 ms
Nov 7, 2026171 ms
Nov 14, 2026163 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 skydance.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. skydance.com at 0.8 s0.8 s
  2. skydance.com at 1.6 s1.6 s
  3. skydance.com at 2.4 s2.4 s
  4. skydance.com at 3.2 s3.2 s
  5. skydance.com at 4.0 s4.0 s
  6. skydance.com at 4.8 s4.8 s
  7. skydance.com at 5.6 s5.6 s
  8. skydance.com at 6.4 s6.4 s

Speed

11 to fix27
  • YouTube adds 8.3 s

    8.3 s

    YouTube costs a phone 8.3 s of main-thread work and 27.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 19.0 s

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

  • Mobile performance score: 27

    27/100

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

  • 3,940 HTML elements

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

  • Use efficient cache lifetimes

    25.3 MB

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

  • Improve image delivery

    16.3 MB

    13 images could be 16.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    15.0 MB

    About 15.0 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google CDN and others), adding 28.5 MB and 8.8 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Other Google APIs/SDKs adds 229 ms

    229 ms

    Other Google APIs/SDKs costs a phone 229 ms of main-thread work and 700 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.

  • Google CDN adds 108 ms

    108 ms

    Google CDN costs a phone 108 ms of main-thread work and 352 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.

  • Reduce unused CSS

    165 KiB

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

  • Minify JavaScript

    39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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: 14 ms

    14 ms

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

Core Web Vitals

12 to fix33
  • 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.4 s

    3.4 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Speed Index: 39.1 s

    39.1 s

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

  • Time to Interactive: 225.8 s

    225.8 s

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

  • First Contentful Paint: 6.9 s

    6.9 s

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

  • Total Blocking Time: 3.2 s

    3.2 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are building a thriving entertainment ecosystem where st…”.

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 320 ms

    320 ms

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

  • Largest content (LCP) got 47% slower for real visitors

    +47%

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

  • 4 images without width and height

    4 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-11-14, real Chrome visitors' tap response (inp) went from 155 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.042

    0.042

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

Images and page weight

5 to fix18
  • Page weight: 57.0 MB in 823 requests

    57.0 MB

    Your homepage downloads 57.0 MB in 823 requests on a phone: scripts 25.0 MB (192), images 18.1 MB (110) and media 6.9 MB (4). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 16.4 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    5.1 MB

    1 image is downloaded at several times the size a phone draws it, for example 49cc63f31cf312e8c0a0b10a9e95858df42d75bf.jpg at 4,096 px wide, shown at 358 px. Resized copies would save about 5.1 MB.

  • 14 images in older formats

    14 images (16.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.

  • 2 images below the first screen load straight away

    2 images further down the page (5.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 16.2 g of CO₂ per visit

    16.17 g

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

Accessibility

5 to fixGoogle 9394
  • 5 buttons without a name

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

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Page should contain a level-one heading (1 element)

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

  • Headings skip levels

    Headings skip levels (h2 → h5 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. (3 elements).

2 checks passed
  • Every image has alt text

    All 119 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8576
  • No H1 headline

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

  • Title is short (8 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.skydance.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 37 internal links, 40 external

    The homepage links to 37 pages on skydance.com and 40 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Skydance is home to one of the industry's most powerful content engines, with a vast portfolio of iconic brands, franch…”.

  • Canonical URL set

    The canonical URL is https://www.skydance.com/.

  • Structured data in place

    Structured data found: Organization, 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.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

3 to fix88
  • 2 pages without a meta description

    https://www.skydance.com/news/ebenezer-opens-to-no-1-worldwide-with-42-million and https://www.skydance.com/news/the-bay-is-back-beloved-palisades-theater-reopens-its-doors have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages share a meta description

    https://www.skydance.com/about, https://www.skydance.com/about/brands, https://www.skydance.com/about/leadership, https://www.skydance.com/about/advertising, https://www.skydance.com/about/values-and-guiding-principles and https://www.skydance.com/about/compliance-resources and 7 others use the same meta description. A description written for each page earns more clicks.

  • 13 pages without an H1

    https://www.skydance.com/about, https://www.skydance.com/about/brands, https://www.skydance.com/about/leadership, https://www.skydance.com/about/advertising, https://www.skydance.com/about/values-and-guiding-principles and https://www.skydance.com/about/compliance-resources and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.skydance.com/about/brands has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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

3 to fixGoogle 7385
  • 5 small tap targets

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

  • 5 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was 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 (“Cookie”).

1 checks passed
  • 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: 2 trust badges. 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 257 words of copy

    The homepage carries about 257 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before 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 (Ketch) is installed; check it blocks these until visitors agree where the law requires it.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 of them by other companies (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: Ketch

    A consent management tool (Ketch) 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 skydance.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
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
7 open roles
Teams
IT (2), Animation (1), Interactive Engineering (1), Interactive Management (1)
Job board
lever

Company

Founded
2025
Headquarters
One Astor Plaza

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 skydance.com, including 23 speed issues, 5 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

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