lightricks.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Google CDN and others), adding 28.5 MB and 1.0 s of main-thread time.

website-files.com costs a phone 202 ms of main-thread work and 27.4 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.

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

Google Tag Manager costs a phone 446 ms of main-thread work and 467 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.

2 images could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

22 KiB could be saved by minifying CSS.

Desktop scores 69 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 29.3 MB in 87 requests on a phone: media 25.1 MB (6), images 1.8 MB (12) and scripts 1.7 MB (26). Under 2 MB keeps phones on slow connections fast.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

There are 4 <h1> headlines (“Where AI meets open creativity”, “Our open-source AI model. Generate high-quality v…” and “Giving you the power to enhance and edit your pho…”). One clear main headline is easier for people and search engines.

Your meta description is 268 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and Product) but with 4 problems, for example “Product: no offers (price) block”.

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

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

The homepage links to 5 pages on lightricks.com and 28 external pages.

There is no /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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 318 words of visible text.

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

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

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