aamsaai.com website review

39 files are served with short cache lifetimes, so returning visitors download them again (4.1 MB).

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

About 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

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

Cloudflare CDN costs a phone 54 ms of main-thread work and 444 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.

26 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Cloudflare CDN, Google CDN and Google Fonts), adding 681 KiB and 97 ms of main-thread time.

1 long task block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 25.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “-20260506034259-1883-1006.jpg”.

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

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

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

The layout shifts by 0.306 while loading, so content jumps under the reader's thumb. Good is under 0.1.

12 images have no width and height attributes, so the layout jumps as each one loads.

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.8 MB in 50 requests on a phone: images 4.0 MB (22), scripts 442 KiB (12) and stylesheets 279 KiB (13). Under 2 MB keeps phones on slow connections fast.

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

10 images are downloaded at several times the size a phone draws them, for example -20260506034259-1883-1006.jpg at 3,333 px wide, shown at 390 px. Resized copies would save about 2.2 MB.

13 images (4.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.

3 images further down the page (246 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

12 tap targets are too small or too close together to hit reliably with a finger.

<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 7 characters: “AAMSAAI”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 84 pages on aamsaai.com and 3 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.

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.

/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html, /categories/%E5%BF%AB%E5%85%85%E7%B3%BB%E5%88%97, /categories/%E5%95%B1%E6%99%92%E6%8E%A8%E8%96%A6%E7%94%A2%E5%93%81, /pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, /pages/%E6%9C%80%E6%96%B0%E8%B3%87%E8%A8%8A.html and /pages/%E4%BB%98%E6%AC%BE%E6%96%B9%E5%BC%8F.html and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html, /categories/%E5%BF%AB%E5%85%85%E7%B3%BB%E5%88%97, /categories/%E5%95%B1%E6%99%92%E6%8E%A8%E8%96%A6%E7%94%A2%E5%93%81, /pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, /pages/%E6%9C%80%E6%96%B0%E8%B3%87%E8%A8%8A.html and /pages/%E4%BB%98%E6%AC%BE%E6%96%B9%E5%BC%8F.html and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/%E8%81%AF%E7%B5%A1%E6%88%91%E5%80%91.html, /categories/%E5%BF%AB%E5%85%85%E7%B3%BB%E5%88%97, /categories/%E5%95%B1%E6%99%92%E6%8E%A8%E8%96%A6%E7%94%A2%E5%93%81, /pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, /pages/%E6%9C%80%E6%96%B0%E8%B3%87%E8%A8%8A.html and /pages/%E4%BB%98%E6%AC%BE%E6%96%B9%E5%BC%8F.html 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.

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

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'msie')”.

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

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

1 resource load over plain http on your https page (for example http://aamsaai.com); browsers block or warn about them.

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.

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

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

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

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

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

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

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

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

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

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

aamsaai.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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.

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