aaproduct.com website review

8 images could be 755 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

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

About 290 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 752 KiB and 324 ms of main-thread time.

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

19 KiB could be saved by minifying CSS.

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.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

14 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 2.6 MB in 56 requests on a phone: images 1.7 MB (20), scripts 721 KiB (17) and fonts 167 KiB (3). Under 2 MB keeps phones on slow connections fast.

14 images (1.6 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.

1 image is downloaded at several times the size a phone draws it, for example slide6.jpg at 1,425 px wide, shown at 390 px. Resized copies would save about 49 KiB.

3 images further down the page (293 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 0.75 g of CO₂e: 89.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

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

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

Your title is 156 characters, so Google will cut it off around 60: “Home - Manufacturer of construction and pumps such as air-operated diaphragm pump, concre…”.

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

There are 5 <h1> headlines (“AA Products”, “Products” and “Service”). One clear main headline is easier for people and search engines.

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

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

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

No XML sitemap at https://aaproduct.com/sitemap.xml, so Google discovers your pages only by following links.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 45 pages on aaproduct.com and 4 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.

/brands, /brands/mpump, /brands/versa-matic, /brands/dickow, /brands/serfilco and /brands/blue-white and 8 others use the same meta description. A description written for each page earns more clicks.

/brands/material-handling-equipment, /brands/smart, /brands/others and /brands/general-construction-machines 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.

/brands/dickow and /brands/blue-white took over 3 s to send their HTML from our server.

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

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

http://aaproduct.com does not redirect to https, so some visitors land on the insecure version.

1 link to other sites is dead, for example https://www.linkedin.com/in/aa-product-malaysia-3a6265170 (999).

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.

1 link go through two or more redirects, for example http://www.aeioustudio.com/.

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.

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

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

Social proof on the homepage: 1 trust badge. 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.

The homepage has only about 143 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.

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

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 ip4:103.10.78.50 include:spf.sfdns.net +a +mx +ip4:220.158.201.163 +ip4:202.75.56.133 ?all”.

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 and Google Tag Manager (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.

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