Website review, no card needed
adameve.com website review
Visit site (opens in a new tab)Reviewed 11 October 202628 issues · 85 checks
This review found 28 issues worth fixing on adameve.com, 13 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.4 s |
| Apr 25, 2026 | 1.4 s |
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.4 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 196 ms |
| Apr 25, 2026 | 196 ms |
| May 2, 2026 | 196 ms |
| May 9, 2026 | 195 ms |
| May 16, 2026 | 195 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 195 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 195 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 196 ms |
| Sep 12, 2026 | 196 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 196 ms |
| Oct 3, 2026 | 197 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Reduce unused JavaScript
1.5 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Render-blocking requests
1.3 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
450 ms · 649 KiB44 files are served with short cache lifetimes, so returning visitors download them again (649 KiB).
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, ofgreencolumn.com and Google Tag Manager and others), adding 1.0 MB and 861 ms of main-thread time.
Reduce unused CSS
750 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 426 ms. During a long task the page ignores taps.
2,338 HTML elements
The page has 2,338 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
143 KiB14 images could be 143 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 61 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 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: 32.2 s
32.2 sThe page becomes fully interactive after 32.2 s. Good is under 3.8 s.
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Take 50% Off 2 Items With Code DOUBLE50”.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Real-user TTFB: 867 ms
867 msReal visitors wait 867 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 196 ms to 197 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 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: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.058
0.058The layout barely moves while loading (CLS 0.058, good is under 0.1).
Images and page weight
Page weight: 4.1 MB in 316 requests
4.1 MBYour homepage downloads 4.1 MB in 316 requests on a phone: scripts 2.9 MB (75), images 599 KiB (86) and fonts 283 KiB (12). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (364 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (300 KiB) are 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 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 139.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 80 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
496 internal links, 10 external
The homepage links to 496 pages on adameve.com and 10 external pages.
8 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Shop vibrators, dildos, butt plugs, couples toys & more at Adam & Eve. Trusted since 1971. Great prices, free gifts & d…”.
One H1 headline
Your main headline reads: “Explore Pleasure, Intimacy & Sexual Wellness”.
Title: 47 characters
Your title is a healthy 47 characters: “Adam & Eve: Sex Toys & Sexual Wellness Products”.
Canonical URL set
The canonical URL is https://www.adameve.com/.
Structured data in place
Structured data found: Organization 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.adameve.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.adameve.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 (2,403 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.adameve.com/shoppingcart.aspx and https://www.adameve.com/adult-sex-toys/kinky-bondage/sex-machines-c-2263.aspx are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
1 page without an H1
https://www.adameve.com/shoppingcart.aspx has 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 185 found) and read each the way a search engine does.
5 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 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn02.taggstar.com/customers/adamevecom/taggstar-v7.min.css' from origin 'https://…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
28 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 689 words of copy
The homepage carries about 689 words of visible text.
7 checks passed
40 calls to action
The homepage has 40 calls to action, for example “Order Status”, “Shop All” and “How to Buy Lingerie”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call 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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
33 cookies set on arrival
33Opening the homepage sets 33 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 adameve.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on adameve.com, including 16 speed issues, 1 SEO issue and 3 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.