Programmable

Website review, no card needed

leadforensics.com logo

leadforensics.com website review

Visit site (opens in a new tab)Reviewed 1 November 202614 issues · 88 checks

This review found 14 issues worth fixing on leadforensics.com, 2 of them high impact, across 88 checks. The most urgent: certain ARIA roles must contain particular children (1 element). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

93A

Closest competitors among SaaS websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.5 s1.5 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.3 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.4 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.9 s
Oct 17, 20262.1 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
244 ms142 msMay 9Oct 24189 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026184 ms
May 16, 2026186 ms
May 23, 2026186 ms
May 30, 2026188 ms
Jun 6, 2026195 ms
Jun 13, 2026187 ms
Jun 20, 2026207 ms
Jun 27, 2026232 ms
Jul 4, 2026227 ms
Jul 11, 2026213 ms
Jul 18, 2026203 ms
Jul 25, 2026170 ms
Aug 1, 2026170 ms
Aug 8, 2026184 ms
Aug 15, 2026171 ms
Aug 22, 2026177 ms
Aug 29, 2026177 ms
Sep 5, 2026155 ms
Sep 12, 2026154 ms
Sep 19, 2026164 ms
Sep 26, 2026159 ms
Oct 3, 2026157 ms
Oct 10, 2026169 ms
Oct 17, 2026161 ms
Oct 24, 2026189 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

www.leadforensics.com (opens in a new tab)
Full-page screenshot of leadforensics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. leadforensics.com at 0.4 s0.4 s
  2. leadforensics.com at 0.8 s0.8 s
  3. leadforensics.com at 1.1 s1.1 s
  4. leadforensics.com at 1.5 s1.5 s
  5. leadforensics.com at 1.9 s1.9 s
  6. leadforensics.com at 2.3 s2.3 s
  7. leadforensics.com at 2.6 s2.6 s
  8. leadforensics.com at 3.0 s3.0 s

leadforensics.com does not allow embedding, so this is Google's rendering of the page.

Speed

3 to fix86

  • Mobile performance score: 86

    86/100

    Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    450 ms · 36 KiB

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

  • 1,683 HTML elements

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

  • Reduce unused CSS

    150 ms · 18 KiB

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

  • Improve image delivery

    79 KiB

    2 images could be 79 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 3 third-party services on the page

    3 third-party services load with your homepage (mida.so, Adobe TypeKit and openfpcdn.io), adding 154 KiB and 43 ms of main-thread time.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed

  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 212 ms of it running JavaScript. That is comfortably low.

  • Server response: 11 ms

    11 ms

    Your server sent the HTML in 11 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100

  • Largest Contentful Paint: 3.9 s

    3.9 s

    Your largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “B2B website visitor identification with Lead Forensics”. Most of its time is element render delay (2.1 s).

  • Speed Index: 4.1 s

    4.1 s

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

  • Time to Interactive: 3.9 s

    3.9 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

10 checks passed

  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 180 ms

    180 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 406 ms

    406 ms

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

  • Largest content (LCP) got 27% faster for real visitors

    -27%

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

100

  • About 0.1 g of CO₂ per visit

    0.14 g

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

4 checks passed

  • Page weight: 506 KiB in 68 requests

    506 KiB

    Your homepage downloads 506 KiB in 68 requests on a phone: images 135 KiB (10), HTML 112 KiB (1) and fonts 103 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9295

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 8 text elements with low contrast

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

  • 11 links without text

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

2 checks passed

  • Every image has alt text

    All 83 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290

  • Title is short (21 characters)

    Your title is only 21 characters: “Home - Lead Forensics”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 11 links with vague text

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

  • 154 internal links, 12 external

    The homepage links to 154 pages on leadforensics.com and 12 external pages.

7 checks passed

  • Meta description: 136 characters

    Your meta description is 136 characters: “Everything you need to know about Lead Forensics - the original B2B website visitor identification tool that helps you …”.

  • One H1 headline

    Your main headline reads: “Turn anonymous B2B website traffic into revenue”.

  • Canonical URL set

    The canonical URL is https://www.leadforensics.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.leadforensics.com/sitemap_index.xml.

AI search readiness

1 to fix88

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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.

3 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,234 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (8 KiB, 44 links), a plain-text guide to the site for AI tools.

Other pages

100

  • 15 internal pages checked

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

7 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

2 checks passed

  • Tap targets are thumb-sized

    7 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix94

  • http:// does not redirect

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

  • No security.txt

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

7 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (leadforensics.com).

  • Valid certificate (80 days left)

    The certificate from Google Trust Services · WE1 verifies for leadforensics.com and is valid for another 80 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 49 links work

    All 49 links checked from your homepage (40 internal, 9 external) answered without errors; 1 did not answer within 5 s.

Domain and trust

  • No CAA record

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

  • DNSSEC is off

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

2 checks passed

  • Domain is 16 years old

    16 years

    leadforensics.com was registered in Jul 2010 through easyDNS Technologies Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Jul 2027

    leadforensics.com is registered until Jul 2027.

Content and conversion

100

  • No form on the homepage

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

  • No risk reducer

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

  • About 564 words of copy

    The homepage carries about 564 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a demo” and “Request a call back”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Contact decision makers”, “Pricing” and “Contact us”.

  • Social proof on the page

    Social proof on the homepage: 3 customer or partner logos and 11 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Email authentication

85

  • Email authentication score: 85/100

    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.

3 checks passed

  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:eu._netblocks.mimecast.com ip4:137.220.73.99 ip4:52.51.138.22 ip4:52.50.251.61 ip4:31.3.233.105 ip4:31.3…”.

  • DKIM signing found

    A DKIM key is published (selector “selector2”, “s1” and “s2”), so receivers can verify mail really came from you.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 5 other companies contacted

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

1 checks passed

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Upkeep, stack and company

  • It runs WordPress 3.7.1; the current release is 7.1.4.
  • 1 plugin is behind its latest release.elementor 4.3.4 → 4.3.5

Stack

CMS
WordPress 3.7.1
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
19 open roles
Teams
Engineering (9), UK Sales (4), US Sales (4), Customer Success (2)
Job board
ashby
Careers page
www.leadforensics.com/careers (opens in a new tab)

Company

Founded
2009

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on leadforensics.com, including 6 speed issues and 2 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25