alj.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 4.8 s

  4.8 s

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

• Real-user FCP: 3.2 s

  3.2 s

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

• Real-user TTFB: 1.5 s

  1.5 s

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

• Tap response (INP) got 10% slower for real visitors

  +10%

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

• Largest content (LCP) held steady for real visitors

  -8%

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

• Page weight: 27.5 MB

  27.5 MB

  Your homepage downloads 27.5 MB on a phone, 26.0 MB of it images (95%). Under 2 MB keeps phones on slow connections fast.

• 23 images over 500 KB

  23 images weigh 17.6 MB together. On a phone connection a single image that size takes seconds.

  Elements (5)

• 40 images in older formats

  40 images (19.4 MB) 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.

  Elements (5)

• 39 images below the first screen load straight away

  39 images further down the page (19.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• 1 image far larger than shown

  41 KiB

  1 image is downloaded at several times the size a phone draws it, for example qrscanner.png at 300 px wide, shown at 80 px. Resized copies would save about 41 KiB.

  Elements (1)

• About 7.8 g of CO₂ per visit

  7.78 g

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

• Certain ARIA roles must contain particular children (1 element)

  Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 43 text elements with low contrast

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

  Elements (3)

• Orphan list items

  Some list items are not inside a list.

  Elements (3)

• ARIA input fields must have an accessible name (5 elements)

  ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• Interactive controls must not be nested (3 elements)

  Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• Malformed lists

  Some lists contain elements other than list items, which screen readers announce wrongly.

  Elements (1)

• All page content should be contained by landmarks (8 elements)

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

  Elements (3)

• No main landmark

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

  Elements (1)

• Zoom is disabled

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

  Elements (1)

• 7 form fields without a label

  7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View sourceElements (2)

• Headings skip levels

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

  View sourceElements (1)

• 111 internal links, 87 external

  The homepage links to 111 pages on alj.com and 87 external pages.

• No llms.txt

  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.

• 5 pages slow to respond

  /en/about/locations, /en/about/values, /en/about/our-people, /en/transportation/transportation-overview and /en/engineering-manufacturing took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 2 broken images

  2 images failed to load on a phone, for example https://alj.com/en/.

• 49 small tap targets

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

• 1 JavaScript error while loading

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

• No Content-Security-Policy

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

• No X-Content-Type-Options

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

• 2 redirects before the homepage

  Opening https://alj.com goes through 2 redirects before the homepage loads.

• 1 link through redirect chains

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

• No Permissions-Policy

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

• Deprecated X-XSS-Protection

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

• No security.txt

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

• No CAA record

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

• DNSSEC is off

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

• No call to action on the first screen

  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 direct contact details

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

• No risk reducer

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

• About 2,559 words of copy

  The homepage carries about 2,559 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be alj.com is still delivered. Reports are on, so moving to quarantine is the next step.

• Email authentication score: 75/100

  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.

• 3 trackers load before any consent

  3

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

• 11 cookies set on arrival

  11

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

• No consent tool detected

  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.

• 10 other companies contacted

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