ahrefs.com website review

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

3 images could be 203 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 66 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

About 105 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.

The page has 2,976 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

8 third-party services load with your homepage (Facebook, Google Tag Manager and cdn-cookieyes.com and others), adding 649 KiB and 377 ms of main-thread time.

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

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

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

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.

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.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Make your business discoverable—in search, AI, and beyond”.

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

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

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

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

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

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

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

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

Your homepage downloads 2.5 MB in 207 requests on a phone: scripts 1.1 MB (90), images 846 KiB (84) and fonts 290 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (45 KiB) is 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.

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

24 buttons have no accessible name, so screen readers announce just “button”.

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

11 images have no alt text, which hurts accessibility and image search.

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

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

The homepage links to 198 pages on ahrefs.com and 43 external pages.

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.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

3 links go through two or more redirects, for example https://signin.letaido.com/sign-up?utm_source=ahrefs_website&utm_content=homepage-letaido-capabilities-banner.

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.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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

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

The homepage carries about 1,610 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.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, LinkedIn Insight, Meta Pixel and Reddit Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 9 cookies (measured from a US location before any click).

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