Website review, no card needed

pixelworks.com logo

pixelworks.com website review

Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 82 checks

This review found 44 issues worth fixing on pixelworks.com, 16 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of pixelworks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pixelworks.com at 0.8 s0.8 s
  2. pixelworks.com at 1.6 s1.6 s
  3. pixelworks.com at 2.5 s2.5 s
  4. pixelworks.com at 3.3 s3.3 s
  5. pixelworks.com at 4.1 s4.1 s
  6. pixelworks.com at 4.9 s4.9 s
  7. pixelworks.com at 5.7 s5.7 s
  8. pixelworks.com at 6.6 s6.6 s

Speed

10 to fix44
  • Reduce unused JavaScript

    10.8 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.8 s faster on a phone.

  • Use efficient cache lifetimes

    6.5 s · 1.4 MB

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

  • Improve image delivery

    3.6 s · 666 KiB

    2 images could be 666 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.

  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 44

    44/100

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

  • Main-thread work: 5.3 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Vimeo and Other Google APIs/SDKs and others), adding 2.3 MB and 1.1 s of main-thread time.

  • Google CDN adds 686 ms

    686 ms

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

  • Reduce unused CSS

    580 ms · 56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.

  • Vimeo adds 287 ms

    287 ms

    Vimeo costs a phone 287 ms of main-thread work and 1.1 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.

  • Legacy JavaScript

    150 ms · 39 KiB

    Polyfills for old browsers add 39 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 20 long tasks on the main thread

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

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 71 ms

    71 ms

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

Core Web Vitals

5 to fix44
  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 25.4 s

    25.4 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Total Blocking Time: 914 ms

    914 ms

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

3 to fix53
  • Page weight: 4.6 MB in 137 requests

    4.6 MB

    Your homepage downloads 4.6 MB in 137 requests on a phone: scripts 2.2 MB (47), images 1.5 MB (21) and other files 356 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (651 KiB) 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.

  • 6 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.30 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8992
  • 3 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 21 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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 23 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 8574
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (27 characters)

    Your title is only 27 characters: “TrueCut Motion – Pixelworks”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 45 internal links, 14 external

    The homepage links to 45 pages on pixelworks.com and 14 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Greater Control Over Motion. Cinematic Clarity, Preserved.”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • 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.pixelworks.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-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, which the crawlers above handle.

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 (831 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix53
  • 1 linked page is broken

    Your homepage links to https://www.pixelworks.com/en, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.pixelworks.com/en/privacy-policy and https://www.pixelworks.com/privacy-policy all use the title “Privacy Policy – TrueCut Motion”. 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.pixelworks.com/media, https://www.pixelworks.com/about-us-old, https://www.pixelworks.com/en/privacy-policy, https://www.pixelworks.com/about-us, https://www.pixelworks.com/privacy-policy and https://www.pixelworks.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.pixelworks.com/en/privacy-policy, whose canonical is https://www.pixelworks.com/privacy-policy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 6 pages without an H1

    https://www.pixelworks.com/media, https://www.pixelworks.com/about-us-old, https://www.pixelworks.com/en/privacy-policy, https://www.pixelworks.com/about-us, https://www.pixelworks.com/privacy-policy and https://www.pixelworks.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5081
  • 11 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.truecutmotion.com/wp-content/uploads/2024/02/F37-F37Bolton-Bold.ttf' from origin 'https:…”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 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

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 18 testimonial or review blocks. 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 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 605 words of copy

    The homepage carries about 605 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Learn More”, “GET IN TOUCH WITH TRUECUT MOTION” and “DOWNLOAD TECHNICAL RESOURCES”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 3 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 13 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 pixelworks.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
WordPress
Framework
jQuery
Hosting
Cloudflare

Company

Employees
20
Founded
1997
Headquarters
San Jose

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on pixelworks.com, including 15 speed issues, 5 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