Website review, no card needed
aedes.com website review
Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 103 checks
This review found 31 issues worth fixing on aedes.com, 7 of them high impact, across 103 checks. The most urgent: main-thread work: 6.0 s. 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
84B- #15,346 of 86,644 reviewed websitesbeats 77%
- #9,205 of 44,499 online storesbeats 73%
- #8,888 of 39,805 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 100 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 102 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 91 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 96 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 97 ms |
| Aug 22, 2026 | 97 ms |
| Aug 29, 2026 | 92 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 113 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 110 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
1.0 s
2.0 s
3.0 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
aedes.com does not allow embedding, so this is Google's rendering of the page.
Speed
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 420 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
650 ms · 415 KiB12 images could be 415 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
1,767 HTML elements
The page has 1,767 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 94 ms
94 msShopify costs a phone 94 ms of main-thread work and 609 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.
Reduce unused JavaScript
150 ms · 242 KiBAbout 242 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Privy and omnisnippet1.com and others), adding 888 KiB and 189 ms of main-thread time.
Reduce unused CSS
150 ms · 20 KiBAbout 20 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
102 KiB8 files are served with short cache lifetimes, so returning visitors download them again (102 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 15.1 s
15.1 sThe page becomes fully interactive after 15.1 s. Good is under 3.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 100 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 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.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 529 ms
529 msReal visitors wait 529 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 67% faster for real visitors
-67%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Total Blocking Time: 8 ms
8 msScripts block the page for only 8 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.5 MB in 326 requests
4.5 MBYour homepage downloads 4.5 MB in 326 requests on a phone: images 2.2 MB (27), other files 1.2 MB (211) and scripts 800 KiB (76). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
carmen_banner_ct_mobile.jpg 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).
14 images below the first screen load straight away
14 images further down the page (474 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.26 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 151.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 70 images in the HTML carry an alt attribute.
49 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: 49 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (25 characters)
Your title is only 25 characters: “Aedes Perfumery est. 1995”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (291 characters)
Your meta description is 291 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
277 internal links, 5 external
The homepage links to 277 pages on aedes.com and 5 external pages.
6 checks passed
One H1 headline
Your main headline reads: “AEDES.COM”.
Canonical URL set
The canonical URL is https://www.aedes.com/.
Structured data in place
Structured data found: BreadcrumbList, 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.aedes.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,105 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
/collections/adlan-fragrances, /collections/amen, /collections/amouage, /collections/atelier-des-ores, /collections/carriere-freres and /collections/chambre52-1 have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.
6 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.
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
12 small tap targets
12 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
1 link through redirect chains
1 link go through two or more redirects, for example https://instagram.com/aedes_perfumery.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
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 (aedes.com).
Valid certificate (49 days left)
The certificate from Let's Encrypt · YE1 verifies for aedes.com and is valid for another 49 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.
http:// redirects to https
http://aedes.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 45 links work
All 45 links checked from your homepage (40 internal, 5 external) answered without errors.
Domain and trust
DNSSEC is off
aedes.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.
3 checks passed
Domain is 28 years old
28 yearsaedes.com was registered in Apr 1998 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only pki.goog, ssl.com, digicert.com and globalsign.com to issue certificates for aedes.com, so a mis-issued certificate from anyone else is refused.
Registered until Apr 2034
aedes.com is registered until Apr 2034.
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 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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 400 words of copy
The homepage carries about 400 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Shop by Brands” and “Subscribe”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Opening hours shown
Your opening hours are on the homepage.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be aedes.com is still delivered. Add a report address, check the reports, then move to quarantine.
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 60/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.
1 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:emailsrvr.com include:mailgun.org ~all”.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Apps on your store
Your storefront loads 9 apps. Each one is code from another company running for your shoppers.
None of the apps your storefront loads is on the list of apps with a known security problem.
Apps your storefront loads
Blockify Fraud Filter · Pagefly Ai Page Builder · Wrapped · Tabs Studio · Region Restrictions · Now In Stock · Omnisend · privy.com · justuno.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on aedes.com, including 10 speed issues, 3 SEO issues and 6 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.