elementor.com website review

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

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

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (19 KiB).

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

3 third-party services load with your homepage (JSDelivr CDN, weglot.com and Unpkg), adding 81 KiB and 63 ms of main-thread time.

1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

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

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 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Short description of the video: Your vision deserves tools …”.

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

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

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

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

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

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

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

Your homepage downloads 7.1 MB in 102 requests on a phone: media 4.7 MB (7), images 1.3 MB (24) and scripts 528 KiB (29). Under 2 MB keeps phones on slow connections fast.

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

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.

Elements with visible text labels do not have matching accessible names. (1 element).

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 56 pages on elementor.com and 23 external pages.

/products/manage is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/speed-performance has no meta description, so Google writes the search snippet from whatever text it finds.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://lklxnafr.elementor.cloud/cdn-cgi/content?id=NF8BDtPMQoKFHqet4ehinSPWSz13iN4R9HpTj4QIaPY-1793172404.9767873-1.2.1.1-TY9A7Ela7s0LABXvTJR7VoljCLHm4JmD_InmdFiwBS7xyxt0rnjOK5zE1BCw4Jgd (404).

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.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

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.

elementor.com'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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 2,285 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.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.

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