aleran.com website review

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

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

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

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

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

8 third-party services load with your homepage (hsappstatic.net, Hubspot and Google Tag Manager and others), adding 3.0 MB and 1.8 s of main-thread time.

hsappstatic.net costs a phone 576 ms of main-thread work and 1.7 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.

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

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

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

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

The page has 1,723 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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.

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

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

Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Aleran sits in front of the ERP you already run. Your custo…”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.2 MB in 150 requests on a phone: scripts 2.6 MB (51), fonts 1.1 MB (27) and HTML 223 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is 77 characters, so Google will cut it off around 60: “ERP-Connected Commerce, CPQ and Portals for Industrial Manufacturers | Aleran”.

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

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

The homepage links to 116 pages on aleran.com and 6 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

/cpq-for-manufacturing and /cpq all use the title “CPQ for manufacturing”. Search engines can't tell which page to show for a search, so each competes with the others.

/platform-security, /catalog-embedded-buying, /customer-portals, /b2b-integrations, /sales-pim and /sales-order-management and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/platform-security, /catalog-embedded-buying, /customer-portals, /b2b-integrations, /sales-pim and /sales-order-management and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pricing took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://pixel.visitiq.io/dot/0cf9f841-9a7a-4ad4-8784-ca3e7f0f9158?cbust=3249581344308714.5&ga_session_id=1793874448&url_path=https%3A%2F%2Fwww.aleran.com%2F.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

4 errors were logged to the browser console while the page loaded, for example “(0 , C.__dangerousOptInToUnstableAPIsOnlyForCoreModules) is not a function”.

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

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

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

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

Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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 2,457 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, Hotjar and HubSpot and 1 more (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 16 cookies (measured from a US location before any click).

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