Website review, no card needed

adtrace.ai logo

adtrace.ai website review

Visit site (opens in a new tab)Reviewed 17 November 202618 issues · 64 checks

This review found 18 issues worth fixing on adtrace.ai, 4 of them high impact, across 64 checks. The most urgent: reduce unused JavaScript. 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

Full-page screenshot of adtrace.ai (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adtrace.ai at 0.5 s0.5 s
  2. adtrace.ai at 0.9 s0.9 s
  3. adtrace.ai at 1.4 s1.4 s
  4. adtrace.ai at 1.9 s1.9 s
  5. adtrace.ai at 2.3 s2.3 s
  6. adtrace.ai at 2.8 s2.8 s
  7. adtrace.ai at 3.2 s3.2 s
  8. adtrace.ai at 3.7 s3.7 s

Speed

7 to fix71
  • Reduce unused JavaScript

    1.4 s · 312 KiB

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

  • Mobile performance score: 71

    71/100

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

  • Render-blocking requests

    850 ms

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

  • Improve image delivery

    450 ms · 108 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Google CDN and website-files.com and others), adding 1.3 MB and 379 ms of main-thread time.

  • website-files.com adds 80 ms

    80 ms

    website-files.com costs a phone 80 ms of main-thread work and 760 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.

  • Google CDN adds 83 ms

    83 ms

    Google CDN costs a phone 83 ms of main-thread work and 352 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.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 28 ms

    28 ms

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

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Best Pixel Tracking On Earth Setup better Pixel trackin…”.

  • Time to Interactive: 8.2 s

    8.2 s

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

  • 54 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Speed Index: 3.4 s

    3.4 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 168 ms

    168 ms

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    66f6de42fcdcc55ac5ab25bd__Button base-p-500.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (36 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.

  • About 0.4 g of CO₂ per visit

    0.38 g

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

2 checks passed
  • Page weight: 1.3 MB in 47 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 47 requests on a phone: scripts 640 KiB (8), images 347 KiB (28) and fonts 332 KiB (4). That is a lean page.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10097
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

2 checks passed
  • Every image has alt text

    All 68 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 32 internal links, 4 external

    The homepage links to 32 pages on adtrace.ai and 4 external pages.

7 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Our pixel attribution system helps your ads perform better with accurate targeting, increasing revenue. Optimize store …”.

  • One H1 headline

    Your main headline reads: “The Best Pixel Tracking On Earth”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “AdTrace: eCommerce Analytics & Ad Attribution Platform”.

  • Canonical URL set

    The canonical URL is https://www.adtrace.ai/.

  • 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.adtrace.ai/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.adtrace.ai/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.

2 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 (427 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 2 pages with very little text

    https://www.adtrace.ai/get-started and https://www.adtrace.ai/contact 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 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

Google 100100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No direct contact details

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

  • 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 396 words of copy

    The homepage carries about 396 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try AdTrace Free on Shopify”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Pricing”, “Get Started” and “Try AdTrace Free on Shopify”.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, 58 customer or partner logos and “over 10,000 brands”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 9 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at adtrace.ai, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Webflow
Analytics
Google Analytics
Hosting
Webflow

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on adtrace.ai, including 12 speed issues, 1 SEO issue and 1 conversion gap. 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