⚡ 60fps · GPU Compositing

Animation Performance Checker

Lighthouse says “avoid non-composited animations” but never tells you which ones or how to fix them. This tool parses every @keyframes on your page, flags the CPU-heavy ones and gives an exact transform/opacity conversion for each.

Animation Perf CheckerYour tool. Connected workflows.
Free tool guide

Get more from the Animation Performance Checker

By the SocialKit.tools team · Reviewed 4 November 2026 · 100% free, no sign-up

3 quick steps

How it works

  1. 1
    PASTE

    Enter a page URL

    Paste the page whose animations feel slow or janky.

  2. 2
    PARSE

    Read every @keyframes

    The checker parses CSS animations and flags properties that are not GPU-composited.

  3. 3
    FIX

    Swap to transform / opacity

    Copy the suggested transform or opacity version of each heavy animation.

What you get

Key features

  • Reads every @keyframes

    Finds all CSS animations on the page, including ones in linked stylesheets.

  • Composited vs. paint-heavy

    Flags animations on width, height, top, left, margin or box-shadow that force layout and paint.

  • Duplicate names

    Warns when two @keyframes share a name and silently override each other.

  • Copy-paste fixes

    Suggests a transform/opacity version you can drop into your CSS.

The complete guide

Animation Performance Checker: everything you need to know

It fetches your page’s HTML and CSS in your browser — inline styles plus up to 6 external stylesheets, including cross-origin CDNs — parses every @keyframes block, and classifies each animated property: transform and opacity are GPU-composited (cheap), paint properties like color and filter repaint every frame (moderate), and layout properties like left, width or background-position reflow the page every frame (expensive). It also catches duplicate @keyframes names — a sneaky bug where the last definition silently wins. It reads prefixed @-webkit-keyframes and first-level @import files too, and if a stylesheet resists fetching you can paste the .css file URL directly as the input.

  1. Enter a URL — ideally the page Lighthouse flagged.
  2. Check the GPU-friendly score — the share of animations that are composited.
  3. Open each flagged keyframe — it lists the offending properties and which rules use it.
  4. Apply the suggested conversion — same visual effect, transform/opacity only.
  5. Gate ambient loops on mobile and add a prefers-reduced-motion block.

Only transform and opacity are fully GPU-composited — they skip layout and paint entirely and stay smooth at 60fps even on cheap phones. Everything else costs main-thread time every single frame: paint properties repaint the element, and layout properties reflow the whole page. The table below shows the standard conversions.

Instead of animating…Use this composited equivalent
left / top / right / bottomtransform: translateX() / translateY()
width / heighttransform: scaleX() / scaleY()
background-position (gradient flow)Make the element ~300% wide with a seamless gradient, animate translateX(-66.667%)
box-shadow pulsetransform: scale() pulse, or shadow on a ::after with opacity
border-color / SVG fillStatic colour on the class + opacity in the keyframes
Pro tips

Tips for better results

  • Animate only transform and opacity wherever possible.
  • Respect prefers-reduced-motion for users who disable animation.
  • Avoid animating large blurred shadows — fake them with a pseudo-element and opacity.
  • Re-run the check after every theme or plugin update.
Who it’s for

Front-end developers, WordPress site owners and designers who see janky scrolling or a poor INP score.

Privacy

How this tool handles your data

  • Public page fetch. To read a public web page, your browser requests it directly or through a public relay (a CORS proxy) because browsers cannot read other sites on their own. Only the URL you enter is sent; the analysis itself happens in your browser.
  • Google PageSpeed Insights. Speed, Lighthouse and Core Web Vitals checks send the URL you enter to Google’s PageSpeed Insights API. Google’s own privacy policy applies to that request.
  • No account, no tracking of your input. The tool is free with no login. Anonymous usage statistics (Google Analytics) and ads may use cookies only as described in our Privacy & Cookie Policy.
Answers

Frequently asked questions

An animation that changes properties the GPU can’t handle alone — anything except transform and opacity. The browser must recalculate layout or repaint on the CPU for every frame, which causes jank, battery drain and a failed Lighthouse audit.
It counts every element running a non-composited animation — one bad @keyframes used by many elements multiplies fast. Fix the keyframes definition once and every element using it becomes composited.
If two @keyframes blocks share a name, CSS silently uses only the LAST one for the entire document — the earlier animation never runs. It usually happens when styles are appended over many versions. This tool lists every duplicated name.
No — each suggestion reproduces the same visual effect with composited properties: a shine that animated left becomes a translateX sweep, a flowing gradient becomes a wide strip translating, a border pulse becomes an opacity fade. Same look, no main-thread cost.
Keep entrance and interaction animations, but pause ambient infinite loops (auroras, floating blobs, twinkles) under @media(max-width:768px) — phones gain battery and smoothness with no real visual loss. Always ship a prefers-reduced-motion block too.
No — it audits CSS @keyframes from the page’s HTML and up to 6 external stylesheets, including cross-origin CDNs. JS-driven animations (GSAP, Web Animations API) and cross-origin CSS aren’t covered; Chrome DevTools’ Performance panel handles those.

Compare motion before and after a change

Start with a repeatable action, such as opening a menu or triggering a hero animation. Use the same device, viewport and action for each run. A visit on a fast desktop can miss a problem that is visible on a budget phone.

  1. Run the checker against the exact page URL and note what data the report could collect.
  2. Record the interaction in your browser’s Performance panel. Look for long tasks or repeated layout work while motion is active.
  3. Change one property or effect, then repeat the recording. Try animating transform or opacity when they fit the design.

Enable reduced motion in your system settings and confirm the control remains usable. If the page jumps as a banner or image appears, use Layout Shift Finder to investigate that separately.