allot.com website review

4 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.4 s faster on a phone.

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

7 third-party services load with your homepage (Google Tag Manager, Hubspot and userway.org and others), adding 1.1 MB and 599 ms of main-thread time.

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

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

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

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

Hubspot costs a phone 157 ms of main-thread work and 343 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.

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

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

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

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.

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

Your largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Family using connected devices at home, protected by their …”.

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

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

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

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

12 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-17, real Chrome visitors' tap response (inp) went from 130 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example slide-unprotected.png at 1,460 px wide, shown at 390 px. Resized copies would save about 831 KiB.

Your homepage downloads 3.9 MB in 109 requests on a phone: images 2.6 MB (30), scripts 1.1 MB (49) and fonts 69 KiB (7). Under 2 MB keeps phones on slow connections fast.

slide-visibility.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images (320 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.

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

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 128 pages on allot.com and 9 external pages.

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.

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

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

http://allot.com does not redirect to https, so some visitors land on the insecure version.

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

1 link go through two or more redirects, for example https://customers.allot.com/.

X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

allot.com 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.

allot.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.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 460 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 and HubSpot (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 3 cookies (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.