luciq.ai website review

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

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

16 files are served with short cache lifetimes, so returning visitors download them again (413 KiB).

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 850 ms.

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

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

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

3 images could be 105 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Polyfills for old browsers add 41 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dashboard showing an app growth bar chart and a revenue lin…”.

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

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

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

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

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

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

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

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

67 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Banner 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 banner 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 on the page fails this check, rated moderate by axe-core.

Structured data found (Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.

The homepage links to 90 pages on luciq.ai and 19 external pages.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

luciq.ai has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

luciq.ai's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 919 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Heap and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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