adkf.com website review

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

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

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

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

Desktop scores 66 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

1 third-party service load with your homepage (website-files.com), adding 1 KiB and 0 ms of main-thread time.

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “An Accounting Firm That's With You All The Way”. Most of its time is resource load delay (8.9 s).

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

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

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.

By the Sustainable Web Design model, a visit to your homepage emits about 0.45 g of CO₂e: 53.8 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. (1 element).

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

1 text element doesn'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.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Skip links are not focusable. (1 element).

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

Structured data found (Article, ImageObject, Organization and Person) but with 2 problems, for example “ImageObject: url is not an absolute URL ("/wp-content/uploads/2025/09/consulting.webp")”.

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

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

The homepage links to 32 pages on adkf.com and 10 external pages.

Your Organization JSON-LD is missing url, sameAs (social profiles), description 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.

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 homepage links to /who-we-are and /career-opportunities, which answer with an error. Visitors hit a dead end and search engines drop them.

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

2 errors were logged to the browser console during Google's test (“ReferenceError: jQuery is not defined at https://adkf.com/wp-content/plugins/gravityforms/js/jquery…”).

7 links from your homepage to your own site are broken, for example https://adkf.com/category/manufacturing/ (508).

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.

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

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 56 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 698 words of visible text.

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.