amiantit.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: 9.5 s

  9.5 s

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

• Real-user FCP: 9.2 s

  9.2 s

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

• Real-user TTFB: 3.5 s

  3.5 s

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

• Tap response (INP) held steady for real visitors

  -8%

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

• Largest content (LCP) held steady for real visitors

  +9%

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

• Page weight: 7.0 MB

  7.0 MB

  Your homepage downloads 7.0 MB on a phone, 5.2 MB of it images (74%). Under 2 MB keeps phones on slow connections fast.

• 2 images over 500 KB

  2 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 2 images far larger than shown

  827 KiB

  2 images are downloaded at several times the size a phone draws them, for example ISECC-1400x700.png at 1,400 px wide, shown at 355 px. Resized copies would save about 827 KiB.

  Elements (2)

• 16 images in older formats

  16 images (3.0 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)

• About 2.0 g of CO₂ per visit

  1.98 g

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

• 5 text elements with low contrast

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

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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 (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 15 form fields without a label

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

  View source

• 11 links without text

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

  Elements (3)

• Headings skip levels

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

  View source

• Title is short (19 characters)

  Your title is only 19 characters: “الرئيسية – أميانتيت”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Meta description is long (336 characters)

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

  View source

• 158 internal links, 13 external

  The homepage links to 158 pages on amiantit.com and 13 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.

• 1 page without an H1

  /%d8%a7%d9%84%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%a7%d8%b9%d9%84%d8%a7%d9%85%d9%8a has no <h1> headline, so visitors and search engines get no clear main topic.

• 13 pages with very little text

  /%d8%b4%d8%b1%d9%83%d8%a7%d8%aa%d9%86%d8%a7, /portfolio/%d8%b3%d8%a7%d8%af%d9%8a%d8%a8, /portfolio/%d8%a3%d9%81%d9%8a%d9%84, /portfolio/%d8%a3%d9%85%d9%8a%d8%a8%d9%88%d9%83%d8%b3, /portfolio/%d8%a3%d8%a8%d9%83%d9%88 and /portfolio/%d8%a3%d8%b1%d9%8a%d9%84 and 7 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 9 pages slow to respond

  /portfolio/%d8%a3%d9%81%d9%8a%d9%84, /portfolio/%d8%a3%d9%85%d9%8a%d8%a8%d9%88%d9%83%d8%b3, /portfolio/%d8%a3%d8%a8%d9%83%d9%88, /portfolio/%d8%a3%d8%b1%d9%8a%d9%84, /%d8%a7%d9%84%d8%aa%d8%ad%d9%85%d9%8a%d9%84%d8%a7%d8%aa and /%d8%a7%d9%84%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%a7%d8%b9%d9%84%d8%a7%d9%85%d9%8a and 3 others took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

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

• 2 broken links to your own pages

  2 links from your homepage to your own site are broken, for example https://amiantit.com/?osf_portfolio=appsco (404).

• No Content-Security-Policy

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

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• Short HSTS lifetime

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

• No X-Content-Type-Options

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

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

• No security.txt

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

• DNSSEC is off

  amiantit.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 calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• Thin social proof

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

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• Only about 51 words

  The homepage has only about 51 words of visible text; thin pages give Google and first-time buyers little to go on.

• 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 risk reducer

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

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be amiantit.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.

• 1 cookie set on arrival

  1

  Opening the homepage sets 1 cookie (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.

• 7 other companies contacted

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