amalan.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.0 s

  4.0 s

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

• Real-user FCP: 3.9 s

  3.9 s

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

• Real-user TTFB: 3.2 s

  3.2 s

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

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

  +19%

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

• Largest content (LCP) held steady for real visitors

  +3%

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

• 1 image far larger than shown

  72 KiB

  1 image is downloaded at several times the size a phone draws it, for example Logo-amalan-Hi-Res-01-1.png at 3,508 px wide, shown at 108 px. Resized copies would save about 72 KiB.

  Elements (1)

• 2 images in older formats

  2 images (286 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.

  Elements (2)

• About 0.6 g of CO₂ per visit

  0.55 g

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

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

  All page content should be contained by landmarks: 24 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)

• Headings skip levels

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

  View sourceElements (1)

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

  View source

• No social preview image

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

  View source

• No robots.txt

  There is no robots.txt at blog.amalan.com/robots.txt, the first file search crawlers ask for.

• 81 internal links, 31 external

  The homepage links to 81 pages on amalan.com and 31 external pages.

• Organization data is thin (3 of 6 facts)

  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.

  View source

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

• Your server turned our page checks away

  15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://blog.amalan.com/' was loaded over HTTPS, but requested an insecure font 'http://blo…”.

• 5 insecure resources on an https page

  5 resources load over plain http on your https page (for example http://blog.amalan.com/wp-content/uploads/2022/12/Logo-amalan-Hi-Res-01-1.png); browsers block or warn about them.

• No HSTS header

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

• No Content-Security-Policy

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

• No Referrer-Policy

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

• 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

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

  amalan.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 social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• Phone number is not tap-to-call

  Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

• No form on the homepage

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

• 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 594 words of copy

  The homepage carries about 594 words of visible text.

• Email authentication score: 95/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.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel and 1 more (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.

• 12 cookies set on arrival

  12

  Opening the homepage sets 12 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.

• 24 other companies contacted

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