afcosystems.com website review

The page goes through 4 redirects before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

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

A phone's processor spends 7.8 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

About 102 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

Scripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.

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

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

Real visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 7.1 MB in 191 requests on a phone: images 3.7 MB (19), scripts 2.8 MB (71) and fonts 176 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (3 elements).

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

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

Links do not have a discernible name (4 elements).

ARIA input fields do not have accessible names (3 elements).

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some list items are not inside a list.

1 element has a tabindex above 0, which scrambles the keyboard order.

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 13 characters: “AFCO Redirect”. 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.

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

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

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

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.

Large scripts ship without source maps.

Your homepage is served without HTTPS, so browsers mark it “Not secure” and some refuse forms on it.

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

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

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

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

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 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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

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.