Website review, no card needed
adtraction.com website review
Visit site (opens in a new tab)Reviewed 17 November 202620 issues · 83 checks
This review found 20 issues worth fixing on adtraction.com, 4 of them high impact, across 83 checks. The most urgent: 3 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
92AClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 743 ms |
| Jun 6, 2026 | 767 ms |
| Jun 13, 2026 | 752 ms |
| Jun 20, 2026 | 742 ms |
| Jun 27, 2026 | 728 ms |
| Jul 4, 2026 | 744 ms |
| Jul 11, 2026 | 774 ms |
| Jul 18, 2026 | 831 ms |
| Jul 25, 2026 | 874 ms |
| Aug 1, 2026 | 906 ms |
| Aug 8, 2026 | 904 ms |
| Aug 15, 2026 | 861 ms |
| Aug 22, 2026 | 815 ms |
| Aug 29, 2026 | 795 ms |
| Sep 5, 2026 | 793 ms |
| Sep 12, 2026 | 814 ms |
| Sep 19, 2026 | 823 ms |
| Sep 26, 2026 | 830 ms |
| Oct 3, 2026 | 811 ms |
| Oct 10, 2026 | 788 ms |
| Oct 17, 2026 | 777 ms |
| Oct 24, 2026 | 733 ms |
| Oct 31, 2026 | 735 ms |
| Nov 7, 2026 | 734 ms |
| Nov 14, 2026 | 739 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 91 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 94 ms |
| Jul 11, 2026 | 93 ms |
| Jul 18, 2026 | 89 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 80 ms |
| Aug 15, 2026 | 79 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 78 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 80 ms |
| Sep 26, 2026 | 82 ms |
| Oct 3, 2026 | 82 ms |
| Oct 10, 2026 | 80 ms |
| Oct 17, 2026 | 80 ms |
| Oct 24, 2026 | 79 ms |
| Oct 31, 2026 | 79 ms |
| Nov 7, 2026 | 80 ms |
| Nov 14, 2026 | 82 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
Speed
Render-blocking requests
900 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused JavaScript
150 ms · 299 KiBAbout 299 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
361 KiB12 images could be 361 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 260 ms
260 msGoogle Tag Manager costs a phone 260 ms of main-thread work and 324 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 on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 720 KiB and 475 ms of main-thread time.
Reduce unused CSS
150 ms · 81 KiBAbout 81 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.
Use efficient cache lifetimes
172 KiB6 files are served with short cache lifetimes, so returning visitors download them again (172 KiB).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 155 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93. That is in Google's “good” band (90 and up).
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 552 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
46 images without width and height
46 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Increase your sales at a predictable cost Do you want to re…”.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 87 ms to 82 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 0.7 s to 0.7 s 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: 0.6 s
0.6 sReal visitors wait 0.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 70 ms
70 msReal visitors wait 70 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 239 ms
239 msReal visitors wait 239 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 143 ms
143 msScripts block the page for only 143 ms while loading. Good is under 200 ms.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.5 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: 1.4 MB in 68 requests
1.4 MBYour homepage downloads 1.4 MB in 68 requests on a phone: scripts 779 KiB (14), images 479 KiB (42) and stylesheets 81 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 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
35 internal links, 7 external
The homepage links to 35 pages on adtraction.com and 7 external pages.
6 checks passed
Meta description: 95 characters
Your meta description is 95 characters: “We help brands find new customers and sell more, while helping partners monetise their content.”.
Title: 45 characters
Your title is a healthy 45 characters: “Grow your business with partners | Adtraction”.
Canonical URL set
The canonical URL is https://adtraction.com/.
Structured data in place
Structured data found: Corporation, WebPage and WebSite.
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://adtraction.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://adtraction.com/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.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,319 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a title
https://adtraction.com/resources/cases/how-menkind-increased-sales-by-18-while-reducing-partner-marketing-costs and https://adtraction.com/resources/cases/how-storytel-scaled-partner-marketing-from-the-nordics-to-ten-european-markets have no <title>, so Google invents the link text in results.
2 pages share a title
https://adtraction.com/resources and https://adtraction.com/blog all use the title “Helpful resources | Adtraction”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://adtraction.com/resources/cases/how-menkind-increased-sales-by-18-while-reducing-partner-marketing-costs, https://adtraction.com/blog/make-sure-your-partners-have-the-information-they-need-in-black-week, https://adtraction.com/blog/increase-commissions-to-win-more-visibility-this-black-week and https://adtraction.com/resources/cases/how-storytel-scaled-partner-marketing-from-the-nordics-to-ten-european-markets have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://adtraction.com/resources and https://adtraction.com/blog use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://adtraction.com/brands, https://adtraction.com/pricing, https://adtraction.com/about, https://adtraction.com/resources, https://adtraction.com/brand-directory and https://adtraction.com/resources/cases/how-menkind-increased-sales-by-18-while-reducing-partner-marketing-costs and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
3 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,347 words of copy
The homepage carries about 1,347 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: “Get started”.
5 calls to action
The homepage has 5 calls to action, for example “Get started”, “Pricing” and “Read more and see pricing”.
Social proof on the page
Social proof on the homepage: 104 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 adtraction.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- CloudFront
Hiring
- Hiring
- 7 open roles
- Job board
- careers page
- Careers page
- adtraction.com/careers (opens in a new tab)
Company
- Employees
- 130
- Founded
- 2007
- Headquarters
- Stockholm
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on adtraction.com, including 7 speed issues, 2 SEO issues and 2 conversion gaps. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.