Website review, no card needed

cyberlink.com logo

cyberlink.com website review

Visit site (opens in a new tab)Reviewed 26 October 202636 issues · 88 checks

This review found 36 issues worth fixing on cyberlink.com, 11 of them high impact, across 88 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.9 s1.8 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.5 s
Jun 13, 20262.7 s
Jun 20, 20263.0 s
Jun 27, 20263.9 s
Jul 4, 20264.4 s
Jul 11, 20264.4 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.6 s
Aug 8, 20264.6 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.5 s
Oct 3, 20264.5 s
Oct 10, 20264.4 s
Oct 17, 20264.1 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
163 ms145 msMay 9Oct 24159 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026147 ms
May 16, 2026150 ms
May 23, 2026151 ms
May 30, 2026152 ms
Jun 6, 2026155 ms
Jun 13, 2026150 ms
Jun 20, 2026150 ms
Jun 27, 2026153 ms
Jul 4, 2026159 ms
Jul 11, 2026159 ms
Jul 18, 2026157 ms
Jul 25, 2026154 ms
Aug 1, 2026151 ms
Aug 8, 2026153 ms
Aug 15, 2026156 ms
Aug 22, 2026158 ms
Aug 29, 2026155 ms
Sep 5, 2026155 ms
Sep 12, 2026156 ms
Sep 19, 2026158 ms
Sep 26, 2026161 ms
Oct 3, 2026158 ms
Oct 10, 2026158 ms
Oct 17, 2026156 ms
Oct 24, 2026159 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 cyberlink.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cyberlink.com at 0.4 s0.4 s
  2. cyberlink.com at 0.8 s0.8 s
  3. cyberlink.com at 1.1 s1.1 s
  4. cyberlink.com at 1.5 s1.5 s
  5. cyberlink.com at 1.9 s1.9 s
  6. cyberlink.com at 2.3 s2.3 s
  7. cyberlink.com at 2.6 s2.6 s
  8. cyberlink.com at 3.0 s3.0 s

Speed

5 to fix72
  • Use efficient cache lifetimes

    950 ms · 1.3 MB

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

  • Improve image delivery

    500 ms · 1.4 MB

    6 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    460 ms · 305 KiB

    About 305 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • 3 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Other Google APIs/SDKs, JSDelivr CDN and Google Fonts and others), adding 275 KiB and 37 ms of main-thread time.

  • Reduce unused CSS

    11 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 306 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

10 to fix67
  • 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.6 s

    3.6 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 5.1 s

    5.1 s

    Your largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Spooky Makeovers, Free to Try”.

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Time to Interactive: 8.6 s

    8.6 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

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

    +80%

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 5 images without width and height

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

4 checks passed
  • Real-user INP: 149 ms

    149 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 22 ms

    22 ms

    Scripts block the page for only 22 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix40
  • 1 image over 500 KB

    Spotlight_PhD_enu.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.1 MB

    1 image is downloaded at several times the size a phone draws it, for example Spotlight_PhD_enu.png at 2,752 px wide, shown at 350 px. Resized copies would save about 1.1 MB.

  • Page weight: 2.6 MB in 65 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 65 requests on a phone: images 1.7 MB (17), scripts 565 KiB (18) and fonts 296 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

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

  • About 0.8 g of CO₂ per visit

    0.75 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8693
  • Images must have alternative text (5 elements)

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

    All page content should be contained by landmarks: 19 elements on the page fail 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.

  • No main landmark

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 8596
  • 22 links crawlers can't follow

    22 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 30 internal links, 18 external

    The homepage links to 30 pages on cyberlink.com and 18 external pages.

8 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Edit videos and photos, generate marketing content, and play back your media. Explore our AI software, online tools and…”.

  • One H1 headline

    Your main headline reads: “Award-Winning Video and Photo Editing Software”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “CyberLink: AI Video, Photo & Marketing Content Creation”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: OnlineStore, 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.cyberlink.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 2 AI crawlers

    Your robots.txt lets ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

    There is no https://www.cyberlink.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
  • Organization data: 6 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (344 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix76
  • 2 pages share a title

    https://www.cyberlink.com/products/photodirector-photo-editing-software-365/overview_en_US.html and https://www.cyberlink.com/products/photodirector-photo-editing-software-365/overview all use the title “PhotoDirector - A Complete Photo Editor with Generative AI”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.cyberlink.com/partner/qnqp, https://www.cyberlink.com/cyberlink-affiliate-program and https://www.cyberlink.com/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.cyberlink.com/products/photodirector-photo-editing-software-365/overview_en_US.html and https://www.cyberlink.com/products/photodirector-photo-editing-software-365/overview use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.cyberlink.com/prog/trial/user-add.do, whose canonical is https://www.cyberlink.com/downloads/trials/index_en_US.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.cyberlink.com/stat/company/enu/index.jsp, https://www.cyberlink.com/cyberlink-affiliate-program and https://www.cyberlink.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5438222&tm=gtm002&Ver=2&mid=5e817356-b054-466c-8fa7-37108a57d0fd&bo=7&sid=bc64cec0d11c11f1bf8421ef305f9659&vid=bc650df0d11c11f1a8091523adbd11b1&vids=0&msclkid=N&pi=918.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.cyberlink.com' has been bl…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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 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 322 words of copy

    The homepage carries about 322 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Free Download” and “Learn more”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Free Download”, “Learn more” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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.

  • 24 cookies set on arrival

    24

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 cyberlink.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on cyberlink.com, including 15 speed issues, 2 SEO issues and 3 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