Website review, no card needed
anakin.io website review
Visit site (opens in a new tab)Reviewed 22 October 202626 issues · 78 checks
This review found 26 issues worth fixing on anakin.io, 8 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
87BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 209 ms |
| May 9, 2026 | 177 ms |
| May 16, 2026 | 158 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 149 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 240 ms |
| Jul 11, 2026 | 215 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 148 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 167 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 189 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 207 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
1.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 75
75/100Your mobile performance score is 75 (desktop: 54). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (reddit, Google Tag Manager and IPONWEB and others), adding 793 KiB and 710 ms of main-thread time.
Improve image delivery
510 KiB9 images could be 510 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
378 KiBAbout 378 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 295 ms
295 msGoogle Tag Manager costs a phone 295 ms of main-thread work and 488 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.
reddit adds 295 ms
295 msreddit costs a phone 295 ms of main-thread work and 28 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.
2,516 HTML elements
The page has 2,516 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 35 KiBAbout 35 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
129 KiB8 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 119 ms. During a long task the page ignores taps.
Legacy JavaScript
53 KiBPolyfills for old browsers add 53 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 247 ms
247 msYour server sent the HTML in 247 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Time to Interactive: 16.7 s
16.7 sThe page becomes fully interactive after 16.7 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 903 ms
903 msReal visitors wait 903 ms for your server to start answering (75th percentile). Good is under 800 ms.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 251 ms
251 msScripts block taps and scrolling for 251 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 209 ms to 207 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 183 requests
2.9 MBYour homepage downloads 2.9 MB in 183 requests on a phone: scripts 1.3 MB (49), other files 640 KiB (90) and images 601 KiB (35). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
56 KiB1 image is downloaded at several times the size a phone draws it, for example soc2-badge.png at 1,463 px wide, shown at 16 px. Resized copies would save about 56 KiB.
1 image in older formats
1 image (56 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.
1 image below the first screen load straight away
1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 97.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
85 text elements with low contrast
85 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
43 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: 43 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
149 internal links, 8 external
The homepage links to 149 pages on anakin.io and 8 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Turn any website into clean, agent-ready data. Scrape, crawl, search, and run pre-built Wire actions across 940+ sites.…”.
One H1 headline
Your main headline reads: “One API.The whole web,agent-ready.”.
Title: 35 characters
Your title is a healthy 35 characters: “Anakin.io — One API. The whole web.”.
Canonical URL set
The canonical URL is https://anakin.io/.
Structured data in place
Structured data found: Organization, SoftwareApplication 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://anakin.io/sitemap.xml.
AI search readiness
Parts of the site are closed to 6 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,978 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://anakin.io/llms.txt (6 KiB, 22 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 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
16 small tap targets
16 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 1,646 words of copy
The homepage carries about 1,646 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get started”.
10 calls to action
The homepage has 10 calls to action, for example “Pricing”, “Get started” and “Start free”.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 17 customer or partner logos, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Reddit Pixel and X (Twitter) Ads (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
20 other companies contacted
Loading the homepage contacts 20 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 anakin.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on anakin.io, including 18 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.